Skip to content

Force --teammate-mode in-process on Claude CLI commands#665

Merged
Iron-Ham merged 1 commit intomainfrom
Iron-Ham/force-teammate-mode-cli-flag
Feb 16, 2026
Merged

Force --teammate-mode in-process on Claude CLI commands#665
Iron-Ham merged 1 commit intomainfrom
Iron-Ham/force-teammate-mode-cli-flag

Conversation

@Iron-Ham
Copy link
Owner

Summary

  • Passes --teammate-mode in-process directly on the Claude CLI command for both BuildStartCommand and BuildResumeCommand
  • This supplements the settings.local.json approach from Prevent Claude Code Agent Teams from using tmux inside Claudio #664 with a higher-precedence CLI flag that cannot be overridden by user settings or $TMUX auto-detection
  • Adds test assertions for the flag in both start and resume command tests

Context

The fix in #664 writes teammateMode: "in-process" to .claude/settings.local.json in each worktree, but CC's "auto" mode can still detect $TMUX (inherited from Claudio's tmux session) and switch to split-pane mode. CLI flags take highest precedence in CC's config resolution chain, making this the definitive fix.

Test plan

  • Existing tests updated to verify --teammate-mode in-process is present in both start and resume commands
  • go test ./internal/ai/... passes
  • go build ./... and go vet ./... clean

The settings.local.json approach from #664 can be overridden by
user-level settings or $TMUX auto-detection. Pass the flag directly
on the CLI for both start and resume commands to guarantee in-process
teammate mode at the highest configuration precedence.
@Iron-Ham Iron-Ham merged commit 41f05e6 into main Feb 16, 2026
4 of 6 checks passed
@Iron-Ham Iron-Ham deleted the Iron-Ham/force-teammate-mode-cli-flag branch February 16, 2026 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments