[BUG] BRAND NEW FEATURE = Branch naming convention makes branches unidentifiable in dropdown claude code web

Resolved 💬 3 comments Opened Jan 16, 2026 by digisurfsome Closed Feb 28, 2026

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?

claude code web

!Image

!Image

Problem:

Branch dropdown truncates names, showing only ~25 characters
The unique session ID (e.g., 5aEUV) is placed at the END of branch names
All branches look identical: claude/complete-seven-..., claude/complete-seven-...
Users cannot distinguish between branches
Leads to working on wrong branch, corrupted work, confusion
Simple Fix:
Put the session ID FIRST:

Current: claude/seven-coding-tasks-2pt70 → Shows as claude/seven-coding-ta...
Better: claude/2pt70-seven-coding-tasks → Shows as claude/2pt70-seven-co... ✓
Impact: Users are unknowingly working on wrong branches, causing data loss and project corruption.

What Should Happen?

Question??? When I start a new chat what should I have the branch set too. I got no notification this changed or know how to use it and I accidently changed files on a month long project because of not knowing . how does it work??? please explain so I can use it correctly

<img width="751" height="634" alt="Image" src="https://github.com/user-attachments/assets/0371ff76-692f-4ffb-97a9-108c4aa1e12a" />

Error Messages/Logs

Steps to Reproduce

recverse your naming pattern to having the 5 character id at front of name and descriptive after ... this change alone would solve the issue like this below

claude/seven-tasks-sequence-CKH6G

to

claude/CKH6G-seven-tasks-sequence

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

claude code web

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗