[teamleaderleo]

The app's headless cmux-tui owner (cmux-tui --headless --session cmux-app-nightly) was seen at about 150% CPU for 40 minutes on an idle Mac, against a budget of no CPU at idle. Two background threads in that owner can run with a zero wait once a deadline is in the past and nothing moves it. Each is fixed here with a test that fails on base.

1. mux-terminal-reap: a reap attempt that leaves the terminal reapable re-runs at once

When a due terminal's reap came back Retained or Reaped, the reaper dropped its deadline (forget). If the next scan still listed the terminal, it re-added the deadline at now + grace - unplaced_for. Since #29476, unplaced_for is the durable time the terminal was first seen unplaced, which is already past the grace, so the new deadline was now.

The thread then waited zero (recv_timeout(0)) and ran the next pass at once, and kept doing so. Every pass costs:

• a registry prune of keep and resume rows,
• a SQLite sync_terminal_unplaced write,
• a screen-archive capture,
• a guarded close.

When several terminals are stuck this way, their attempts run in parallel on mux-terminal-work.

A terminal ends up stuck this way whenever the scan and the close guard disagree about whether it is placed. The scan matches a view's runtime id or the content's placements. The guard matches any surface with the same host identity.

Fix: ReapSchedule::tried postpones the deadline by grace.max(MIN_RETRY) after every outcome, as Attached and errors already did. A scan that no longer lists the terminal (closed, placed again, or kept) still drops the deadline in observe_unplaced, so terminals that were really reaped or re-placed behave as before.

2. chief-brains: a brain still typing after the idle stop is due leaves a past deadline

next_deadline offered the idle stop (last_activity + 30 min) for every running brain. on_time stops only a brain that is not typing. So a turn that kept its typing on for more than 30 minutes left a deadline in the past that nothing moved. The thread waited zero, did nothing, and ran again, holding one core at 100% until the turn ended.

Fix: a brain has no idle deadline while it is typing, which matches on_time. When the typing ends, handle sets last_activity, and the stop counts from that point.

Loops touched: stop conditions and cleanup

• mux-terminal-reap:
  • Stop: the existing TerminalReaper::stop / drop (the stop flag plus closing the mailbox), and the thread ends when the Mux is gone.
  • Cleanup: terminal_reaper_events is cleared on exit (unchanged).
  • Waits now: at least MIN_RETRY (1 s) per stuck terminal, normally a full grace.
• chief-brains supervisor:
  • Stop: Signal::Shutdown, or the inbox disconnecting (unchanged).
  • Waits now: until a signal, a backoff retry, or the idle stop of a brain that is not typing.
• No new timers, observers or threads.

Tests (red on base)

• terminal_reap::tests::terminal_reap_schedule_waits_after_an_attempt_that_left_the_terminal_reapable: one terminal unplaced for three graces, with a reap attempt that leaves it reapable. The test simulates the thread's waits for one second and counts the passes.
• terminal_reap::tests::terminal_reap_schedule_drops_a_settled_terminal_once_it_is_no_longer_reapable
• chief_brains::supervisor_idle_tests::a_brain_typing_past_the_idle_stop_leaves_no_past_deadline

Performance

metric	before	after	delta	harness or run link
reaper passes in 1 s, one terminal left reapable by its reap	1000 (the test's cap; the wait is 0, so unbounded)	1	-99.9%	terminal_reap_schedule_waits_after_an_attempt_that_left_the_terminal_reapable
reaper wait after that pass	0 s	30 s (the grace)	+30 s	same test
chief-brains wait with a brain typing past 30 min idle	0 s (one core spinning)	none until its typing ends	no spin	a_brain_typing_past_the_idle_stop_leaves_no_past_deadline
headless owner CPU at idle on the Mac that showed it	~148% (40 min)	to be read after the next NEXT nightly		sample after nightly

Related: #33099 fixes the "cmux-tui stopped and could not start again" toast, not this cause. #33117 (open) adds a cap on the reap grace in the same file; the two do not conflict.

Agent session: agent session

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Fixes two hot loops that spin the headless cmux-tui owner at ~150% CPU on idle: the terminal reaper and the Chief-brains supervisor can wait zero, doing nothing, when a deadline falls in the past and nothing moves it.

Bug Fixes

• mux-terminal-reap: a reap attempt that leaves a terminal reapable now keeps a retry floor (the next deadline is the later of the scheduled one and the floor), so the terminal is retried after at least MIN_RETRY instead of being re-added as due at once. A terminal that a scan no longer lists drops its deadline and floor; one placed again and closed again gets a fresh grace from its new unplaced time.
• chief-brains: a brain that is typing has no idle deadline (matching the idle stop in on_time), and the idle stop counts from when its typing ends, so a past deadline can no longer sit untouched and keep the thread spinning.
• Adds four tests covering the waits; all fail on base.

^{Written for commit bb990df. Summary will update on new commits.}

[github-actions]

cmux status _{(one comment, edited in place; each line is updated by the job that owns it)}

Review fa06154: HQ feed card · gallery before/after runs · checks

App of this head (app.zip, kept 1 day)

gh workflow run reload-build.yml -R manaflow-ai/cmux --ref feat-cmux-next -f tag=pr33173 -f ref=lane/tui-reap-retained-backoff -f platform=macos -f backend_mode=local

red: cmux-next checks (god files, concurrency, crash safety, l10n); no finished base run on 4575ff4 to compare; do not merge until green; see lane-rules

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4165528235801 (b08cc6f4d3)
• cmux NEXT nightly 1.0.0-nightly.4165709173201 (7f6fe51cc3)
• cmux NEXT nightly 1.0.0-nightly.4165880669801 (de5076464a)
• cmux NEXT nightly 1.0.0-nightly.4166004947701 (abcde7ea04)

[teamleaderleo]

Review (codex gpt-6.1-sol high, sweep, via the review router; full diff from merge base eeb28af to this head): SHIP at 9dba1e8

No P1/P2 findings.

[cursor]

Bugbot needs on-demand usage enabled

Bugbot uses usage-based billing for this team and requires on-demand usage to be enabled.

A team admin can enable on-demand usage in the Cursor dashboard.

[blacksmith-sh]

Found 2 test failures on Blacksmith runners:

Failures

Test	View Logs
test_every_compile_job_names_its_warm_sources (main.ThisTree.test_every_compile_job _names_its_warm_sources)/ test_every_compile_job_names_its_warm_sources (main.ThisTree.test_every_compile_job _names_its_warm_sources)	View Logs
test_the_repository_highlights_validate (main.DigestTests.test_the_repository_highl ights_validate)/ test_the_repository_highlights_validate (main.DigestTests.test_the_repository_highl ights_validate)	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[teamleaderleo]

Review (codex gpt-6-astra high, next-review): SHIP at fa06154

SHIP at fa06154
Visual verdict: no images; Leo tries the build

1. [P2] [follow-up] cmux-tui/crates/cmux-tui-core/src/mux/terminal_reap.rs:165: The capacity-limit path bypasses the new retry floor. With more than 16 reapable terminals, lines 407–409 add the oldest terminals to due regardless of their postponed deadlines. A stuck terminal therefore still incurs archive capture and guarded close on every topology wake. Make capacity-triggered attempts respect the retry floor while allowing an initial attempt before the normal grace expires, and add coverage with more than 16 terminals.

Source review completed; tests could not run because this box has no Rust toolchain.

Follow-ups:

• Respect retry floors in capacity-triggered reap attempts and test that path.

[teamleaderleo]

Review (codex gpt-6.1-sol high, sweep, via the review router; full diff from merge base 76505c9 to this head): SHIP at fa06154

No P1/P2 findings.

[cmux-bot]

cmux-bot approves fa06154: an independent review passed this exact head (next-review receipt by teamleaderleo). A push needs a new review; a later BLOCK at this head dismisses this approval.

A newer verdict blocks d6258ef (no independent SHIP at the head).

[cursor]

Bugbot needs on-demand usage enabled

Bugbot uses usage-based billing for this team and requires on-demand usage to be enabled.

A team admin can enable on-demand usage in the Cursor dashboard.