Claude Code /fork: Fork & Go, Main Thread Keeps Running
Claude Code /fork now clones sessions to the background so your main thread keeps running. Learn how background subagents, budget limits, and parallel workflows work.
“AI Disruption” Publication 10,300 Subscriptions 20% Discount Offer Link.
Let Claude Code handle a big job—twenty minutes minimum. What do you do during those twenty minutes? Stare at the terminal and wait. In v2.1.212,
/forkgot a new lease on life: the clone goes to the background, and the main thread keeps working.
In mid-July, Claude Code shipped a dozen or so versions in quick succession (from v2.1.207 to v2.1.218). The most noteworthy change is buried in the changelog: /fork is no longer an in-session branch. Instead, it fully copies the current conversation into an independent background session that appears as its own row in the claude agents dashboard and runs on its own. The old in-session fork was renamed /subtask and made room for the new behavior.
Taking one step further back, v2.1.198 already made subagents run in the background by default. This batch of releases then added a full set of guardrails against runaway behavior. Looked at individually, each change is minor; taken together, it’s clear the team is treating “parallel development” as a first-class citizen.
Everything below was tested on my local v2.1.218.
