docs(workmux): default agent worktrees to --mode session - #27
Open
tomfordweb wants to merge 1 commit into
Open
Conversation
Agent-created worktrees used the default window mode, so every worktree in an epic added a window to the attached tmux session and left tens of empty windows behind. --mode session parks each worktree in its own detached session instead; workmux rm tears it down with the worktree. Also records why --config is not the way to set this: a --config file replaces the project .workmux.yaml rather than merging with it, so the worktree lands outside worktree_dir and skips post_create hooks and file copy/symlink ops.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent-created worktrees used workmux's default window mode, so every worktree in an epic added a window to the attached tmux session. A multi-worktree epic left tens of empty windows behind.
--mode sessionparks each worktree in its own detached tmux session instead. Verified live: worktree lands in the project'sworktree_dir, gets a detached session, adds zero windows to the attached session, andworkmux rmremoves the session with the worktree.Also records the trap I hit while looking for a config-level fix:
workmux add --config <file>replaces the project.workmux.yamlrather than layering on it. A probe with an alternate config put the worktree inandromeda__worktrees/instead of.worktrees/, which also skipspost_create(pnpm install) and every file copy/symlink. Pass the flag, not a config file.Touches the agent rule in three places:
AGENTS.shared.md,ai-tools/CLAUDE.md, and thespawn-workmuxskill.