|
For anyone who wants to try a branch or a beta without touching their daily instance. There's one trap worth knowing about. |
Answered by
Ark0N
Aug 15, 2026
Replies: 1 comment
|
The one rule: never point two instances at the same data dir or tmux socket. tmux is system-global, so a second server on the shared socket discovers the first one's live sessions and attaches to them, resizing and mutating sessions it doesn't own. Isolating
CODEMAN_INSTANCE=beta CODEMAN_PORT=5000 npx tsx src/index.ts webIf you're running from a git clone, |
0 replies
Answer selected by
Ark0N
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The one rule: never point two instances at the same data dir or tmux socket. tmux is system-global, so a second server on the shared socket discovers the first one's live sessions and attaches to them, resizing and mutating sessions it doesn't own. Isolating
$HOMEalone does not save you.CODEMAN_INSTANCEscopes both the data dir and the socket at once:If you're running from a git clone,
scripts/run-beta.shdoes exactly this. Andcodeman web -drefuses to start a second server on a data dir that already has one, which catches the accidental version of the mistake.