Repository navigation
fix(spawn): remove --session <team> override that breaks tmux topology - #1012
Conversation
The --session flag overrides the team config's tmuxSessionName, creating a separate tmux session instead of using the parent session resolved at team creation. This caused workers (reviewers, council members) to land in isolated sessions instead of the project session. - Remove --session <team> from council SKILL.md spawn commands - Remove --session <team> from council member config examples - Add "Spawn Session Rule" to genie-orchestration.md - Add --session constraint to team-lead AGENTS.md
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
--session <team>from council SKILL.md spawn commands — this overridesresolveSpawnTeamWindow(agents.ts:693) and creates a separate tmux session instead of using the team's configured parent session--sessionwhen--teamis set--sessionprohibition to team-lead constraints — prevents AI from hallucinating--session <team>on spawn commandsRoot cause
resolveSpawnTeamWindowcheckssessionOverridefirst (line 693). When--session review-wavesis passed, it skips the team config lookup entirely and creates/uses a session calledreview-waves— a separate session from the parent project.Without
--session, line 695 readsteamConfig.tmuxSessionNamewhich was correctly set at team creation time from the parent session.Test plan
--teamonly