[teamleaderleo]

Carries #24311 (its owner session is gone and its branch sp-attn-b is outside the lane/ namespace this lane can push), with its commits and authorship, onto current feat-cmux-next, plus the fix for the review BLOCK at c27c81c826cf.

Carry changes

• Merged current feat-cmux-next (latest at 06e35107b02). One conflict, in SidebarMapping.swift, where base now names the row's face tab face (cmux-next sidebar: a page a chat opened leaves the chat's row icon #23700/cmux NEXT: agent open makes a chat-only workspace; a chat names its row over an idle shell #26709). Kept base's code and this PR's attention dot and reason.
• BLOCK fix (23ffe9524a7): a mark from a daemon without request ids ({reason, at_ms} only) stayed ringed until the agent cleared it, because going in and Dismiss Highlight skipped marks with no request_id. Hiding the ring is this client's view state, keyed by the client-local attention generation, so it now covers those marks. A press on a mark replaced since the press is still dropped: with no request id it compares the generation captured at the press. The owner clear still requires the id (tab-attention-request-id-v1). Test: TabAttentionTests.aLegacyMarksRingHidesOnEntryAndDismissHighlight.
• Menu validation fix: a row this PR scopes to its machine (Dismiss Highlight, Mark Tab Unread) is now validated against that machine as well as run on it.

Scope. This PR scopes only its own two rows (Dismiss Highlight on a workspace row, Mark Tab Unread on a tab) to the right-clicked object's machine. Every other menu row, and every handler that resolves a tab or workspace id, works exactly as on base: by first match across machines. An attempt to scope every row here (44d10315..ad63a5fc) kept surfacing more first-match lookups downstream and mixed machines inside one action, so it is reverted. The general fix ((machine, id) resolution everywhere, plus a lint against bare locateTab(id)) is tracked in manaflow-ai/cmuxterm-hq#5338.

---

Leo-ask: ask-12231fbe5e

Leo: "idk where things are man i dont see anything other than the current workspace which is you and you have a cmux next github brwoser tab open (we need to have cmux expose this harder if it isn't already/hve better instructions)"

Slice B of the "needs you here" surface: the app shows a tab an agent marked. The daemon half is #24286 (tab.update {attention}, cmux attention request|clear, tab-attention-v1), and this PR lands after it: the bundled-daemon capability check needs that daemon. The palette command and Needs you list item come in slice C, the agent instructions in #24299.

What changes

• The tab record's extra.attention {reason, at_ms} becomes TabModel.attention (TabAttention, CmuxNextDaemon).
• TabModel.showsUnread reads it, so the existing blue treatment shows it everywhere showsUnread is read. There is no new dot and no new drawing code:
  • the tab's dot (TabItemMapping);
  • the screen bar;
  • the sidebar tab list;
  • the pane's blue attention ring.
• The workspace row gets its manual dot, and its text line shows the reason ("Confirm GitHub access") ahead of any notification text.
• Going into the pane (a click or a key) or Dismiss Highlight hides the ring. The dot stays until the agent clears the mark, the page goes elsewhere or the tab closes. A new request (a newer at_ms) rings again.
• Mark as Read on the tab also drops the mark (tab.update {attention: null}, when the daemon has tab-attention-v1).
• notifications.attention.showOnSidebar = false hides it like any unread.

Tests

TabAttentionTests (CmuxNextAppTests):

• parsing, including malformed values;
• showsUnread follows the record;
• the row's dot, the reason and the tab dot; showOnSidebar off hides it;
• the ring rings, stays on focus, hides on a click and comes back for a new request; Dismiss Highlight hides it.

Fleet compile-check at 2ae8268: compile check app: passed.

Capture

Real captures at the head 9638e536 (after) and at the merge base 3f6df909 (before). Each one is a fleet build driven on a capture mini, in light and dark. Each state is a steps file: create an Attention workspace, run cmux attention request --tab current --reason "Confirm GitHub access", then the steps named below.

After: the marked workspace's row while another workspace is shown. Rows show their text line (sidebar.density expanded, sidebar.workspaceRow.notification true), then a Work workspace takes focus. The Attention row has the blue dot and the reason "Confirm GitHub access" as its text line. Its tab row has a dot.

Capture steps-1c499ee5bb at 9638e5361e28 (fleet build, capture mini, text checked for private data)

Light	Dark

Before (same steps on base): the Attention row has no dot, and its text line is the folder (~). Its tab row has no dot.

Capture steps-1c499ee5bb at 3f6df9091dec (fleet build, capture mini, text checked for private data)

Light	Dark

After: the marked pane, then split right (default compact rows, with the row collapsed by a click on its chevron). The marked left pane keeps the attention ring while focus is in the new right pane. Its tab in the strip and the workspace row show the blue dot.

Capture steps-f0b5afd4e4 at 9638e5361e28 (fleet build, capture mini, text checked for private data)

Light	Dark

After: a click into the marked pane (a debug.mouse click in the left pane). The ring is gone. The tab dot and the row dot stay until the agent clears the mark, as described above.

Capture steps-361ccfa69e at 9638e5361e28 (fleet build, capture mini, text checked for private data)

Light	Dark

Before (the split steps on base): no ring, no tab dot, no row dot.

Capture steps-f0b5afd4e4 at 3f6df9091dec (fleet build, capture mini, text checked for private data)

Light	Dark

The reason line shows only where a row shows its notification text: expanded rows with sidebar.workspaceRow.notification on, on a row other than the one shown. On default compact rows, and on the shown workspace's row, only the dot shows.

Viewed after image: yes
Visual verdict: Yes, the blue dot, the reason line and the pane ring reuse the existing unread treatment with no new chrome, and the click hides only the ring, so it would sit fine next to ChatGPT or Claude.

Agent session: agent session

🤖 Generated with Claude Code

[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.

[teamleaderleo]

Review (independent Codex gpt-6.1-sol, high, via the review router; full diff from merge base f3ae1f8 to this head): SHIP at 5825e87.

No P1/P2 findings.

[teamleaderleo]

Review (independent Codex gpt-6.1-sol, high, via the review router; full diff from merge base f3ae1f8 to this head): BLOCK at 5825e87.

[P2] Packages/macOS/CmuxNext/Sources/CmuxNextApp/Notifications/NotificationCenterService.swift:432 - Opening/jumping to an attention-marked tab uses .open, but dismissAttention ignores that trigger, leaving the pane ring visible after the user has entered the tab - include .open in the dismissal triggers.

[teamleaderleo]

Review (independent Codex gpt-6.1-sol, high, via the review router; full diff from merge base f3ae1f8 to this head): SHIP at 8a0b088.

No P1/P2 findings.

[teamleaderleo]

Review (independent Codex gpt-6.1-sol, high, via the review router; full diff from merge base 3f6df90 to this head): SHIP at 9638e53.

No P1/P2 findings.

[github-actions]

Shipped in:

• cmux NEXT nightly 1.0.0-nightly.4112891057101 (ac6b39be7f)
• cmux NEXT nightly 1.0.0-nightly.4112983685701 (81085d9646)
• cmux NEXT nightly 1.0.0-nightly.4113159963901 (9408230f7a)
• cmux NEXT nightly 1.0.0-nightly.4113304608001 (567d1434e3)