{"version":"2.1.292","anchor":"fork-from-a-repo-less-session-records-a-repository-url","canonical_anchor":"fork-from-a-repo-less-session-records-a-repository-url","heading":"\/fork can send a repository address when no git address is found","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/fork-from-a-repo-less-session-records-a-repository-url","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### `\/fork` can send a repository address when no git address is found\n\nWhen forking a session finds no git repository address, Claude Code now falls back to another repository address\n\n**Unclear.** Whether `\/fork` now works from a folder that is not a git checkout is not stated.\n\n**What**\n\nWhen `\/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.\n\n**Why**\n\nThis is aimed at forks started from a folder that is not a git checkout.\n\n- Area: Elsewhere\n- Names: `\/fork`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}