Here is what a real solo founder orders.
$ git worktree list
~/app a1b2c3d [main]
~/app-review e4f5g6h [review-branch]
~/app-content i7j8k9l [draft-post]
Three checkouts. One machine. Each one runs its own Claude Code session that cannot touch the others.
That is a normal workday for me.
I run a one person shop. Content and code, same desk, same hour. Anthropic's common workflows page lists about a dozen recipes for everyday work, and the docs are strong. What they do not tell you is which recipes survive contact with a real workday and which ones stay theory.
After running Claude Code as my whole operation, five workflows carry the load. Here is the honest split.
https://code.claude.com/docs/en/common-workflows
The problem worktrees solve is collision.
You ask Claude to fix a bug. While it edits, you want to keep building a feature. Same repo, two streams of edits, and now your working tree is a fight nobody wins.
A git worktree is a second checkout of the same repo on its own branch. Claude runs inside it and never sees the other windows.
claude --worktree feature-auth
Real scenario from this week. The post you are reading was drafted in one worktree while a separate Claude session reviewed an open pull request in another. Neither touched the other's files. When the review finished I merged, came back to the draft, and never lost my place.
If you take one workflow from the docs, take this one. The setup cost is close to nothing and parallel agents stop stepping on each other.
The model's working memory is your budget.
Every file Claude reads to answer a question spends it. Ask "how does our auth refresh work" in a large repo and Claude reads a pile of files to answer. Those files now sit in the window for the rest of the session, crowding out the work you care about.
Delegate that to a subagent.
use a subagent to investigate how our auth system handles token refresh
The subagent reads in its own window and reports back a summary. Your main session stays clean.
I lean on this every time I research before I write. A scout goes out, does the reading, comes back with the findings, and my working session never fills up with raw source. How long a session stays sharp is the whole game, and a subagent is what keeps it sharp.
I keep a live app with real users on the line.
I do not let Claude edit it blind.
Plan mode makes Claude read and propose before it touches disk. Nothing changes until I approve it.
claude --permission-mode plan
Mid session you can press Shift+Tab to toggle it on. I treat it as the default for anything near production. Read first, plan, approve, then edit. Those few seconds of review have saved me from changes I did not want more than once.
Real work spans more than one sitting.
The expensive part of coming back is re-explaining what you were doing. Claude Code saves every conversation locally, so you do not have to.
claude --continue
That picks up the most recent session in the current directory. When I open a pull request with gh pr create
, the session links to it, and claude --from-pr <number>
drops me back into that exact session days later. For a knowledge vault I edit across a week, this is the difference between continuity and starting cold every morning.
The docs show you can pipe Claude into scripts for CI and batch jobs.
git log --oneline | claude -p "summarize these recent commits"
It is a real feature and it is useful. Here is the part the docs cannot tell you.
On 15 June 2026 Anthropic split Agent SDK billing from the subscription. Headless claude -p
runs now bill against the SDK, not against your Pro or Max seat. A nightly cron you set up months ago and forgot about can quietly change the shape of your bill.
My move was to stop reaching for headless as a reflex. For recurring work I prep the data in a plain shell job and consume it inside an interactive session with subagents, which stays inside the subscription. Same outcome, predictable cost.
If you automate Claude, know which side of that billing line your job runs on before you schedule it.
Use @
to pull a file or directory straight into the session instead of waiting for Claude to find it.
Explain the logic in @src/utils/auth.js
And when text is the wrong tool, paste a screenshot. Drag an image into the window, or paste it with ctrl+v, and Claude reads it. My fastest bug reports are a screenshot of the error and one line of "what is causing this". The picture carries the detail I would have spent five sentences describing.
| Workflow | When it earns its slot |
|---|---|
| Worktrees | The moment you run more than one stream of work at once |
| Subagents | Research or exploration in a repo big enough to flood the window |
| Plan mode | Anything within reach of production |
| Resume and PR link | Work that crosses more than one sitting |
| Headless pipe | CI and batch, with eyes open on billing |
| Prompt recipes | Daily, but you learn these in a day |
The prompt recipes in the first half of the docs are worth reading once. They are good habits and you absorb them fast.
The five above are different. They change how much work fits in a day, not how you phrase a single ask.
One more is coming. Anthropic shipped dynamic workflows in research preview on 28 May 2026, where a script orchestrates subagents and only the final answer reaches the conversation. That is the next rung above everything here, and it deserves its own write up once it leaves preview.
What workflow from your own setup earns its slot that a newcomer would skip? I want the one that is not in the docs.