Claude Code is the deepest coding agent. Clerk should not live in a terminal.

Claude Code is the one I would want in a repo at 1 a.m.

It is deep. It stays in the files. It has the manners of a senior who actually reads the tests. Everything is a session, and for code that is the right grain. You start. You end. You have a diff.

Then people put the rest of the company in the same grain, because the agent is so good they forget the grain exists.

Clerk does not belong in a terminal.

Everything is a session, on purpose

A coding agent that kept a year of random jobs in the same shell would be a haunted house.

Sessions bound the mess. They make undo possible. They make "this was for the auth refactor" a closed object. Cowork is the isolated-folder cousin. Codex is the parallel-cloud cousin. Claude Code is the deep one in the repo.

Honor that. Do not ask it to also be:

• A standing backlog for non-code work
• An inbox with an address
• A place Mail can leave a card for Watch
• A cost desk for lanes that ran while you slept
• A stop rule for customer email

Those are ops. The layer has a name even if the screenshot does not.

If your "team" is three Claude Code windows and a sticky note, you have three sessions and a sticky note. The sticky note is the only persistent teammate, and it does not wake anyone.

Maker might. Clerk should not.

Composition is allowed to be asymmetric.

Maker is building a landing page, a script, a small tool. Let Maker work like a developer. If that means Claude Code, good. The artifact comes back. You review.

Clerk is unpaid invoices, weekday 9, draft, stop before send. If that lives in a terminal, two things happen. You become the scheduler. And the day you close the laptop on a trip, Bell & Rowe does not get the nudge.

Mail is worse in a shell. Replies want an address, a thread, a log, a gate. A terminal is a mouth without a mailbox.

Watch needs to still be Watch at 6 a.m. Sessions do not like 6 a.m. unless you wrap them in cron and then you invented a worse Octopus.

Anthropic's 2026 numbers: 57% of orgs on multi-stage workflows, 16% crossing teams. Claude Code will dominate the coding stage. Crossing into ops is a different product. Microsoft 2025: 82% of leaders expecting digital labor to stretch capacity. Stretching capacity in a ten-person shop is not "everyone got a better terminal." It is "the recurring work did not need a better terminal."

Add the persistent team

Keep Claude Code.

Add a desk where jobs persist. Named teammates. They can hand each other work. You see Needs you. You see cost. You bring the Claude plan you already pay for, or ChatGPT, or Grok, or OSS in the $99. No per-task markup. Computer stays on. Own email. Vault. Approvals. Stack accounts, fallback mid-task. Dedicated workspace, never train. Seven-day money-back. Dedicated VM for agencies: talk to us.

The coding session remains the deep tool. The teammate is the one who still has a job when the session ends.

The cron trap

The clever move is wrapping Claude Code in a schedule so it "becomes" ops.

I have done the clever move. It works until it does not.

A cron does not give you Needs you. It gives you a log file and a 2 a.m. email that the job failed because a login prompt appeared. A cron does not give Mail an address. It gives you a script that sent from your personal account, which you will regret. A cron does not let Clerk wake Watch. It lets you write more glue.

At that point you did not save a product. You built a worse desk in bash.

If the work is a repo, stay in the session. If the work is a lane, put it on a teammate whose computer is already on. Secrets in the vault, not in the shell history. Sending still waits for a tap. You can still open Claude Code from Maker when the artifact is code.

It cannot do judgment, relationships, showing up in person, or taste. A terminal cannot either. Do not ask either of them to sit in the room with the client.

Cowork is the same split with a sandbox instead of a repo.

If you only write code, maybe you only need Claude Code. If you also have customers, an inbox, and a calendar, stop making the terminal pretend it is staff. It is a brilliant specialist. Let it specialize.