What This iMac Has Switched Off

2026-10-19, Jacks-iMac. Brandon said the other Mac creates sub chats, runs things in parallel, has better gates, and took skills off, and told me to find out. He was right on all four. Every one of those capabilities exists on this machine. Some are switched off, one is gated by policy, and three have simply never been used, which is a different and more awkward answer.

1. Where my earlier answer was wrong

I told Brandon the MacBook "found no faster setting" and that its gain was a list of ten mistakes. That came from reading one README rather than from looking at the machine. The README was about one narrow job, switching off thirteen claude.ai add-ons, and it said nothing about orchestration because orchestration was not its subject. I treated the absence of a topic in one document as the absence of the capability. Looking at the filesystem gives a different answer.
40
launchd jobs loaded now
26
skills switched off locally
13
add-ons in the skills trash
2
blocks on sub chats

2. His four claims, each checked against files

"It took off skills" confirmed, twice over

Two separate removals happened, by two different mechanisms.

LOCAL  ~/.claude/skills            179 active skill directories
       ~/.claude/skills_disabled    26 switched off, with toggle.py to flip them back
                                    24 of those auto-disabled 2026-07-17
                                    reason recorded in MANIFEST.json: "unused+unreferenced"

ACCOUNT ~/.claude/skills/.trash     13 add-ons removed by the 2026-10-17 claude.ai sync
        ~/.claude/skills/synced      9 add-ons remain

The thirteen in the trash include deep-research and mcp-builder. That first one matters for his second claim, because deep-research was the parallel-subagent skill. Its own description says it coordinates research subagents and should be used only where a tool for spawning subagents exists, and its procedure spawns research subagents in parallel then a report writer. So the clean-up I verified as finished removed a parallel-research capability, and I reported the clean-up without noticing what came off with it.

"Runs parallel things automatically" confirmed, running right now

The automatic fleet belongs to this machine, and it has been running all day.

41 com.drwu.* plists on disk, 40 loaded in launchctl

PIDs observed at measurement:   n8n 914        reveal-server 897
                      claude-gpu-watch 905    arena-throttle-proxy 885
                      clip-sync 891

jobs include:  claude-config-sync   idea-miner         conductor-rebuild
               substack-hourly      substack-daily     etsy-delivery-audit
               recents-rebuild      transcript-vault   usage-monitor-sweep
               stem-map-refresher   phone-chat-index   disk-space-guardian

plus one crontab entry at 07:00 daily for idea_scanner.py

The n8n orchestrator held PID 914 at the moment of measurement. So the automatic fleet exists on this machine and was working through every turn of this conversation.

"Has gates that are better" confirmed as a direction

The MacBook authors gates and ships them back through iCloud, and several of the gates that refused me today arrived from it.

Gate shipped back from the MacBookBundle it arrived in
completion_stop_gate.pyskill-sync-2026-09-06-completion-controller
no_idle_stop_gate.py, stop_gate.py, quit_gate.pyskill-sync-2026-06-05-no-quit-shift
notation_evidence_gate.py, verdict_gate.py, gpif_share_gate.pyskill-sync-2026-09-06-notation-evidence-gate
drum_reality_gate.py, impossible_gate.pyzappa-macbook-return-2026-08-31, kilgore-macbook-return-2026-08-13

The stop gate that refused four of my attempts to end a turn today is one of those imports. So the gate-authoring habit is a MacBook export, and this Mac is the consumer.

"Automatically creates sub chats" one route gated, three never tried

Nothing is missing here. One route is deliberately gated, and I wrongly reported that as the whole picture.

BLOCK 1  ~/CLAUDE.md, line 13
  "Keep one active Claude session. Do not launch subagents, parallel chats,
   /loop, keepalive work, or browser automation unless Brandon authorizes
   that specific run."

BLOCK 2  ~/.claude/hooks/opus_spawn_gate.py
  PreToolUse hook, matcher "Agent|Task"
  Hard-denies every sub-agent spawn until ~/.claude/.opus_ok is touched.
  One-shot marker, valid 15 minutes, consumed on use.
Correction, 2026-10-19 15:25. I first wrote that sub chats were simply blocked here. A gate caught that as declaring something unreachable without checking, and it was right. Those two blocks cover the Agent and Task tool path only. The Claude Code documentation names other routes, and not one switch disabling them is set on this machine: disableAgentView, worktree, disableWorkflows, enableWorkflows and teammateMode are all unset, the env block is empty so the concurrent-subagent cap stands at its default of 20, and permissions carries no Agent or Task rule.
Documented routeState on this Mac
Agent / Task tool subagents, up to 20 at oncegated by opus_spawn_gate.py and the CLAUDE.md clause
/batch <instruction>, splits work across 5 to 30 subagents, each in its own worktreenothing disables it, never tried here
claude agents, Agent view, background sessions watched from one screendisableAgentView unset, ~/.claude/agents absent, never used
Worktrees, separate CLI sessions in isolated checkoutsworktree unset, ~/.claude/worktrees absent, never used
Agent teams, shared task list and messagingexperimental and off by default upstream

The absence of ~/.claude/agents and ~/.claude/worktrees is the evidence that those two routes have never run here at all. So "blocked" was the wrong word for three of the five: unused is the right one, and the difference between those two words is the thing Brandon has been pointing at.

And here is the likely reason the two machines behave differently at all. The config-sync installer states that CLAUDE.md is per-machine and is never written over, because it hardcodes the source Mac's home, drives and anchors. So the MacBook runs its own CLAUDE.md, which need not carry that one-session clause. The capability gap between the two Macs is most likely a single paragraph in a file that sync refuses to copy.

3. The structural defect behind all of it

The two skills that would have answered Brandon's question are among the ones switched off, and they were switched off for being unused. A sweep that judges a skill by how often it was invoked will always remove the monitoring layer, because a status dashboard is invoked rarely by design. The sweep removed this system's self-awareness, and then there was nothing left to report that it had.
SkillStateWhat it doesStill runnable
fleet-dashboardoff 2026-07-17Shows what every part of the fleet is doing right now: the launchd jobs, the stall-scan cron, voice routing, n8n state, CLI session count. Renders one Markdown dashboard into Brandon-Vault.Yes. Its script is intact at ~/Projects/fleet-dashboard/build_dashboard.py, 4,940 bytes.
system-pulseoff 2026-07-17Ranks every skill by real usage from the session transcripts, flags skills older than the memory rules that govern them, and judges whether the connectors and newer systems are being used as much as they should. Powers a daily adoption nudge.Partly. Its build scripts are intact, but deploy.sh pushes to Vercel through the CLI, which is forbidden from this Mac.

Both carry the same recorded reason as the other twenty-two: unused+unreferenced. Neither was judged on what it was for.

4. The exact levers

Every one of these is reversible, and toggle.py moves directories rather than deleting them.

# see the fleet, without changing any policy
python3 ~/.claude/skills_disabled/toggle.py enable fleet-dashboard
python3 ~/Projects/fleet-dashboard/build_dashboard.py

# rank skills and connector adoption; do NOT run its deploy.sh on this Mac
python3 ~/.claude/skills_disabled/toggle.py enable system-pulse
python3 ~/.claude/skills/system-pulse/build_system_pulse.py

# restore the parallel-research skill from the trash
cp -R ~/.claude/skills/.trash/1792272791312-27828-YYTbyK/deep-research \
      ~/.claude/skills/deep-research

# allow one sub-agent spawn, 15 minutes, consumed on use
touch ~/.claude/.opus_ok

The one lever that is not a command is the first block: the one-session clause in ~/CLAUDE.md is Brandon's standing instruction, so sub chats stay off here until he changes that line. Nothing on this page was switched on while finding this out.