In case this is helpful to anyone else running multiple sessions in Claude Desktop, I put together a repo with some things that have helped me: https://github.com/wshallwshall/claude-multisession Cross-session announce and steering
- tell the other sessions what you’re about to touch, and queue a message into a session that’s already running. Claims and locks
- so two sessions don’t pick up the same work item. ccx doctor
- checks whether your hooks are actually installed and wired, by hashing the installed file against the source and then firing a real attack at each one. Found two broken installers of my own on its first run. A worktree gate
- stops a session writing into the main checkout, or switching a worktree onto another session’s branch. Worktree create/remove/rescue
- one worktree per session, plus a reaper that won’t delete one somebody is working in. A number allocator
- if you have ADRs or anything else numbered, two sessions guessing the same next number merges clean and quietly corrupts the sequence. Notes on landing N branches into one trunk
- four different states all show up as “can’t merge”, and under squash-merge the usual staleness checks lie. Tips and traps
- the stuff I wish I’d known first. submitted by /u/Wsz2020
Originally posted by u/Wsz2020 on r/ClaudeCode
You must log in or # to comment.