spawn never pins a pane size - a stale 1x1 tmux client makes every new den one column wide
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start in container/lib/session_runtime.py at TmuxSessionRuntime.spawn and review the tmux command used to create detached sessions. Reproduce the stale 1×1-client condition described in the issue, then verify the new session uses manual sizing and a 200×50 floor. Re-run the affected rc6 rollup tests and confirm the nine pane-size failures are resolved.
Written by the indexing model from the issue text.
Description
Found while root-causing the 33 pre-existing test failures for the rc6 rollup (#406) — 9 of them are this, correctly alarming and misread as host flakiness.
Bug: TmuxSessionRuntime.spawn (container/lib/session_runtime.py) runs tmux new-session -d … without pinning a pane size. Under window-size latest with a stale client reporting 1×1 (a real state on the dev laptop, /dev/ttys000), every newly spawned detached session comes up one column wide. -x/-y alone does NOT fix it — window-size latest overrides it; window-size manual + resize-window does (proven live, four ways).
Why it matters beyond tests: the notify / den-reply path pastes prompts into panes no human has attached to yet. In a 1-column pane the prompt arrives mangled and the agent TUI has no room to render; the session only recovers when someone opens it.
Recommendation: spawn pins a floor at creation — window-size manual on the session it just made plus a resize (e.g. 200×50).
Full account with the experiments: wolts/uxwolt/wolt/drafts/rc6-preexisting-failures.md (uxwolt's tree).
🤖 Generated with Claude Code
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jerpint/woltspace
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
All issues in jerpint/woltspace
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100