Skip to content

Bug: omc team tmux worker panes collapse to 1 column in npm runtime (bridge/cli.cjs) #2135

@emreozenses

Description

@emreozenses

Hi, we found a reproducible geometry bug in the active npm runtime path of OMC team mode on macOS + tmux.

Environment:

  • macOS
  • tmux
  • npm/global install of oh-my-claude-sisyphus
  • team mode via omc team ...

Symptom:
omc team starts, but worker panes collapse to 1-column width, which makes prompts unreadable and causes waitForPaneReady to time out.

Observed before local hotfix:

  • window: 80x24
  • leader pane: about 78x24
  • worker panes: 1x24 / 1x8 / 1x7
  • waitForPaneReady timed out repeatedly

Important finding:
This is not a raw tmux bug on our machine.
A detached raw tmux test works correctly:

  • new-session -d -x 200 -y 50
  • split-window -h -l 50%
    Result:
  • window: 200x50
  • panes: about 99x50 and 100x50

Root cause we identified:
The active execution path is not the cached plugin copy, but the npm runtime file:
~/.nvm/versions/node/v22.22.0/lib/node_modules/oh-my-claude-sisyphus/bridge/cli.cjs

In that file, the team session creation path is missing geometry controls:

  1. new-session is missing -x 200 -y 50
  2. split-window is missing -l 50%

Because of that, the session starts with default 80x24 geometry and worker panes collapse.

Local hotfix that solved geometry for us:

  1. Add -x 200 -y 50 to the new-session call
  2. Add -l 50% to the split-window call

After local hotfix:

  • window became 200x50
  • leader pane became 80x50
  • worker pane became 119x50
  • waitForPaneReady timeout disappeared

So the geometry issue appears fixed by those 2 changes in bridge/cli.cjs.

Suggested upstream fix:
In the active npm runtime file bridge/cli.cjs, update the team session creation path to:

  • create detached tmux sessions with explicit geometry
  • create worker splits with explicit width percentage

Optional follow-up:
Mixed worker geometry is now correct for us, but we still need to validate worker count / state cleanup separately. That appears to be a different issue, not the geometry issue.

If helpful, I can provide:

  • exact before/after pane size outputs
  • local patch diff
  • reproduction commands

Metadata

Metadata

Assignees

No one assigned

    Labels

    agentsRelated to agent definitionsbugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions