Repository navigation
Point the tmux file-limit banner at a restart for legacy servers - #5
Merged
millwright-software merged 2 commits intoNov 11, 2026
Conversation
The open-file-limit banner always said "Close an extra agent-desk window", but a server on the old 256 default stays capped no matter how many windows close, and a user hitting it may have only one window open. Closing a window frees descriptors for a moment; it never lifts the ceiling. Add ServerFiles.Relief(): a Low() (legacy, <1024) server is told to restart the tmux server so a fresh one inherits agent-desk's raised 16384 limit (the real fix since v1.0.28), while a roomier server that is merely full still points to closing a window. All three banner branches use it. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
… is full
- Relief() for a low-limit server now says the restart ends every session
(R resumes Claude ones), so the banner never points at the destructive
fix without its cost.
- A full server cannot be probed, and the failed probe blanked the cached
reading, so the "server is full" banner fell back to "Close an extra
window" even on a 256 server. PipeManager keeps the last good reading
(LastRoom) and that branch uses it.
- The low-limit notice keeps its reason ("another agent-desk window won't
fit") ahead of the instruction.
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
millwright-software
added a commit
that referenced
this pull request
Nov 11, 2026
#5) On a tmux server stuck at the old 256 default the banner said "Close an extra agent-desk window", which only buys a moment and assumes a second window exists. It now says only a tmux server restart lifts the limit, and that the restart ends every session (R resumes Claude ones). The "server is full" banner keeps the last good probe reading, since a full server cannot be probed. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
millwright-software
added a commit
that referenced
this pull request
Nov 12, 2026
#5) On a tmux server stuck at the old 256 default the banner said "Close an extra agent-desk window", which only buys a moment and assumes a second window exists. It now says only a tmux server restart lifts the limit, and that the restart ends every session (R resumes Claude ones). The "server is full" banner keeps the last good probe reading, since a full server cannot be probed. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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
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.
Problem
On a tmux server stuck at the old macOS 256 open-file default, the banner reads:
For such a server that advice is misleading:
v1.0.28 already added the permanent fix (agent-desk raises its own limit to 16384 so a server it starts inherits that), but a server started earlier — or by a plain
tmuxfrom a shell — keeps 256 until it exits. The in-app banner never surfaced that; onlytroubleshooting.mdpoint 3 did.Change
Add
ServerFiles.Relief(), the shortest instruction that actually gives the server room:Low()(legacy, <1024) server →restart the tmux server to lift the limit— a fresh server inherits agent-desk's raised limit.Close an extra agent-desk window(unchanged).All three banner branches in
tmuxServerWarning()now use it (pm.Room()is hoisted so the unreachable branch can consult the limit too;pm == nilkeeps the prior default phrasing).Test
TestReliefcovers both classes.go build ./cmd/agent-desk/,go vet, and the tmux suite pass.Reproduced on a live 256-capped server (pid,
ulimit -n256, 197 files, 19 sessions).