[DOCS] Commands page still lists `/fork` instead of `/branch`

Status Fixed / completed

Maintainer reply None cached

Activity 3 comments · opened Mar 17, 2026 · closed Mar 18, 2026

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/commands

Section/Topic

Conversation branching command

Current Documentation

The docs currently say:

/fork [name] | Create a fork of the current conversation at this point

What's Wrong or Missing?

Claude Code v2.1.77 renamed /fork to /branch and kept /fork only as a compatibility alias.

The commands reference still documents only /fork, so the canonical command name in docs no longer matches the product.

Suggested Improvement

Update the commands page to list /branch [name] as the primary command and note that /fork still works as an alias.

If any other command index or quick-reference page lists the slash command explicitly, use the same naming there.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/commands | Slash command table still uses /fork as the documented command name |

Total scope: 1 page affected

Source: Claude Code v2.1.77 release notes

Exact release entry:

Renamed /fork to /branch (/fork still works as an alias)

View original on GitHub ↗

3 Comments

kayossouza · 7 months ago

I ran into this as well. The docs at https://docs.anthropic.com reference /fork but the actual command in the CLI is /branch. This confused me when I first tried it. Happy to submit a PR to fix this if needed.

coygeek · 7 months ago

Issue #35143 Verification

Title: [DOCS] Commands page still lists /fork instead of /branch
Issue Date: 2026-03-17
Verification Date: 2026-03-18
Status: RESOLVED

---

Issue Summary

This issue reports that the commands reference page still documents /fork as the primary command name for conversation branching, whereas Claude Code v2.1.77 renamed it to /branch with /fork retained as a compatibility alias.

---

Verification Results

Claim 1: The commands page lists `/fork` as the documented command name

Status: RESOLVED
The commands page at https://code.claude.com/docs/en/commands (line 37) now reads:

/branch [name] | Create a branch of the current conversation at this point. Alias: /fork

This matches the v2.1.77 change exactly: /branch is the primary command name and /fork is documented as the alias.
Verdict: The commands page has been updated to reflect the rename.

Claim 2: The common-workflows page references the command

Status: RESOLVED
The common-workflows page at https://code.claude.com/docs/en/common-workflows (line 624) reads:

Forked sessions (created with /branch, /rewind, or --fork-session) are grouped together under their root session

This also uses /branch as the primary name.
Verdict: The common-workflows page is consistent with the rename.

---

Current State

| Claim | Status |
|-------|--------|
| Commands page lists /fork as primary name | RESOLVED - now shows /branch with /fork as alias |
| Other pages use outdated naming | RESOLVED - common-workflows uses /branch |

---

Suggested Fix

N/A - issue has been resolved.

---

References

URL: https://code.claude.com/docs/en/commands
Line 37: /branch [name] listed as primary with /fork as alias
URL: https://code.claude.com/docs/en/common-workflows
Line 624: Uses /branch as the primary command name
URL: https://code.claude.com/docs/en/changelog
Line 84: v2.1.77 entry confirming the rename

---

Conclusion & Recommendation

Primary Concern: The commands page was reported as listing /fork instead of /branch, but it has since been updated.
Resolution Status: RESOLVED
Recommendation: CLOSE
The commands page now lists /branch [name] as the primary command with /fork documented as an alias, exactly matching the v2.1.77 change. The common-workflows page is also consistent.

github-actions[bot] · 6 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.