Claude Code v2.1.292 · 6 Oct 2026
/fork can send a repository address when no git address is found
When forking a session finds no git repository address, Claude Code now falls back to another repository address
You'll notice Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
1 Signal: worth watching, 1 to 5
Elsewhere Area: what it touches
Improvements Kind: in v2.1.292, 06 Oct 26
Improvements Section of the release
Unclear Whether /fork now works from a folder that is not a git checkout is not stated.
What
When /fork creates a copy of the session in the cloud and Claude Code cannot find a git repository address for it, it now falls back to a different repository address instead of sending none. The result of the fork is also reported separately for forks.
Why
This is aimed at forks started from a folder that is not a git checkout.
How sure we are
Something disagrees Something we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt Whether `/fork` now works from a folder that is not a git checkout is not stated.
See this entry in the whole of v2.1.292 →
6 Oct 2026 · 331 entries, this one is #125.
Use it now19 You'll notice163 Nothing to try yet14 Under the hood135
Open the release →
Names in this entry
slash /fork Copy the current conversation into a new background session and keep working here. Pass a prompt and the copy starts working on it immediately; without one it waits in agent view for its first prompt. Except when the copy edits in place , Claude Code instructs it to create a worktree of its own before making code changes; the isolation instruction requires Claude Code v2.1.221 or later. To hand a side task to a subagent whose result comes back into this conversation, use /subtask; to switch into a copy yourself, use /branch. Requires Claude Code v2.1.212 or later; on v2.1.161 through v2.1.211, and whenever agent view is turned off , /fork starts a forked subagent instead
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 124 of 331
Remote Control drops the oldest subagent updates when too many queue up
You'll notice Elsewhere
In v2.1.292 Improvements release-page order
Next → · 126 of 331
MCP servers can be listed before their resources finish loading
You'll notice MCP