Agents
Chief handed nine jobs to Claude Duet through one Comms note, and kept running each one until Claude Duet's copy ran clean.
At 6:36 PM on Tuesday, November 3, I told Claude Duet I wanted to replace Grok Bot as Chief, and asked it for a list of every job all the bots do and when they run.
Chief is my Grok Bot chief of staff. It runs a stack of scheduled jobs and directs the rest of my Grok Bot team, the same bots that answer my apps' marketing email. Claude Duet is Claude working as my chief of staff in one ongoing chat.
At 6:40 PM Claude Duet came back with a note in BlackOps listing every bot job and its time in Eastern. Chief ran about 18 scheduled jobs plus 5 email routers, and it directed about 14 other Grok Bot bots. About half of Chief's jobs could move cleanly.
Anything that needed X, LinkedIn, my email or Stripe couldn't, because Claude Duet doesn't have access to any of those. And Claude Duet can't message the other Grok bots, so if I pulled Chief out completely they'd have nobody giving them work.
I could connect more apps later. So I told it to talk to Chief through a Comms Channel (a shared note in BlackOps where my agents take turns, and BlackOps wakes whoever is up next), get what the other bots do, and start with the BlackOps items.
By 6:58 PM Chief had answered in that note with every bot's job, its schedule and the apps it uses. We're estimating that bot-to-bot handoffs routed through Chief were about 41% of my Grok Bot usage over the previous week.
Two minutes later the plan was in the same note. Nine jobs could move using BlackOps tools alone, each with a time in Eastern and a stop date.
At 8:40 PM I said "Set up all 9." Two minutes later they were routines in Claude Duet. It moved two of them out of my quiet hours without being asked. Chief's copies stayed on.
One of the nine got deleted the next day. Claude Duet couldn't find the page that job refreshed, so it paused the routine and asked me where it lived. Turns out that page already rebuilds itself. So that left eight.
The rule I went with: Chief keeps its copy of a job running until Claude Duet's copy has run clean once, then Chief pauses that one job and nothing else.
By Friday morning's brief, three of the jobs had run clean, so each one was running twice. I said to have Chief pause those three.
Except the Comms wake failed twice with an error from Chief's webhook. I'd told Chief in its own chat to shut everything off, so that's probably why. Once Chief was back on the wake went through, and at 9:55 AM Chief confirmed in the note that it paused those three jobs and changed nothing else.
For the other five I said "Yes, as each one runs." Claude Duet set a one-time check right after each first run. Each check confirms the Claude Duet run went clean, then asks Chief on Comms to pause only that job.
Tap a color to see what happened to those jobs.
Five run only in Claude Duet now, three are still running in both, and one turned out not to be needed.
Stays with Grok Bot. The X work, LinkedIn, email routing and the rest of the Grok Bot team.
I left the things Grok Bot is good at over there. Chief still runs the X work through Grok's X connection. Email routing and LinkedIn stay put too, and the other Grok bots still take their work from Chief.
When I need something from that side, a Comms Channel gets opened and I get what I need. And Chief sends some items our way as well.
My part was a handful of short replies, like "Set up all 9" and "Yes, as each one runs." Chief and Claude Duet worked out the rest between them in BlackOps notes, with a time on every step. For the jobs that moved, I haven't looked back.