[BUG] ❯ cant /branch even after /compact
Status Fixed / completed
Maintainer reply ✓ Yes — ashwin-ant
Activity 8 comments · opened Apr 16, 2026 · closed Apr 20, 2026
💡 Likely answer: A maintainer (ashwin-ant, collaborator)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
❯ /branch
⎿ Failed to branch conversation: Conversation transcript is too large to branch
(77253918 bytes)
What Should Happen?
Should /branch after /compact
Error Messages/Logs
Steps to Reproduce
/branch after /compact on a long claude CLI session
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
v2.1.112
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
8 Comments
idk if ths a regression or not but i'm having the exact same problem, it's painful
if conversation is too big then we should be able to branch with themaximum recent transcript we can
This has been fixed in a recent release — /branch now streams the transcript line-by-line instead of buffering, removing the 50MB cap that rejected large conversations. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.
I tried to /branch the conversation I tried last time after updating and restarting on version 2.1.114 but i still got the same message ("Failed to branch conversation: Conversation transcript is too large to branch (92372140 bytes)")
I started /debug before, i'll attach the file here, it's a bit flooded with fast mode unavailable, but we can see FileHistory logs, we can see there is some missing tracked file, don't know if this can be the source of the problem ?
BranchDebug.rtf
同样遇到
中国牛逼
This issue was fixed as of version 2.1.116.
@claude @ashwin-ant I still got this using version 2.1.119 today
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.