feat(workspace): one-line attach toast, and a /workspace Status view for the detail

[ralphstodomingo]

Issue for this PR

Closes #1311

Type of change

• New feature

Stacking

Base is feat/workspace-sidebar-status (#1279, the sidebar's memory and skill-sync lines), which now sits on main with #1278 (the /workspace menu) merged. The sidebar tile here carries both #1279's lines and this branch's attach line, in that order under the name: integrations, memories, skills, pinned hint, URL. The branch also carries #1308 and #1310 (the engine's unfulfilled report and the attach report), because the view reads that report; their commits show in this diff until they merge to main, after which this rebases to its own commits.

What does this PR do?

The attach toast carried the whole engine report — every undelivered key grouped by reason, with the engine's detail — and on a workspace with a few gaps it read as noise. Numbers belong in the toast; the keys and reasons belong somewhere they can be read again.

• The toast is one line: 2 of 9 integration tools available · 7 need attention. Details: /workspace, with · N more via VS Code when a live bridge serves extension tools. describeMissing / describeExtensionServed are gone; reasonPhrase keeps the wording for the view.
• An attach snapshot per directory — workspace, engine version, the allowlist, what the engine served, its report — kept in memory and in altimate-attach-snapshots.json under the state directory, because the TUI plugin runs in a different process from the overlay (the same reason the binding cache is a file). Bounded to 64 directories; written best-effort; a test seam keeps the suite out of the real state directory.
• status-view.ts, transport-agnostic like manage.ts: the snapshot joined to the workspace's selection and the catalog gives one row per integration — served / partial / missing with reasons / idle for an extension without a window — attention first, keys beyond the allowlist as extras, and a headline the toast, the menu row and the sidebar share. If the API cannot be reached the view still renders from the snapshot alone, rows named by id.
• /workspace → Status: the menu's first row, whose description is the headline read from the snapshot (no network before the menu opens). It opens the view: an integration row with counts and the reason, muted sub-rows for its keys (gaps with reasons first, then what is available, capped), and Open on the web / Re-read / Done as action rows. A snapshot from a workspace this project was since re-linked away from is ignored.
• Sidebar: the Workspace tile shows the headline under the name once a session has attached, same staleness guard, refreshed on the tile's existing poll.
• Boot box, workspace mode only: under "What is Altimate Code", three lines through a new welcome_extra slot — the mode and the linked workspace, the slash commands the mode adds (/workspace, /skills), and the integrations line: "attach on your first message" before a session, the toast's numbers with a pointer at /workspace after. Unlinked projects get the link command instead. The panel asks for the plugin runtime without throwing, so provider-less renders (its unit tests) omit the slot.

Claims

• C1 — The toast never names a key or a reason: only counts and the pointer; the reasons are in the view (engine-overlay.test.ts, every announce case).
• C2 — The view's numbers are the toast's numbers: statusHeadline and attachSummary derive served / declared / gaps / extServed the same way from the same snapshot (status-view.test.ts "counts match the toast").
• C3 — The snapshot crosses the process boundary: the overlay persists it on every settled attach and the plugin reads the file when its own memory has none (attach-snapshot.test.ts; verified live: the menu row shows the counts in the TUI process).
• C4 — A stale snapshot is never shown: the menu row, the view and the sidebar all compare the snapshot's workspace id with the current binding.
• C5 — No network before the menu opens: the Status row's description is computed from the snapshot; the API is read only when the view itself is opened.
• C6 — Outside workspace mode the boot box is byte-identical: the plugin that fills welcome_extra is registered only under the workspace flag, and an empty slot renders nothing.

Residuals

• R1 — Custom integrations (numeric ids) are named Integration N: the catalog read is the built-in list; the custom list is a second call not made here.
• R2 — Headless run prints nothing on a settled attach, as before; the one-line summary is the TUI's.
• R3 — The sidebar picks the line up on its existing 30 s poll rather than the instant the attach settles.

How did you verify your code works?

• bun run typecheck clean in packages/opencode, packages/tui and packages/plugin; test/altimate/workspace + test/mcp/engine-unfulfilled.e2e.test.ts: 486 pass (new: attach-snapshot.test.ts, status-view.test.ts, welcome-lines.test.ts; updated: the overlay announce cases, engine-types, the e2e report check); packages/tui welcome-panel.test.tsx still passes without a plugin runtime.
• Live on a local stack (backend on this machine, workspace with Jira, GitHub, Altimate, Power User and a custom MCP declared): first prompt → toast 2 of 7 integration tools available · 5 need attention. Details: /workspace; snapshot file written; /workspace → Status 2 of 7 integration tools available · 5 need attention; the view lists GitHub and Jira (no usable connection), the custom and retired integrations (no longer in the catalog), Altimate (available keys), Power User (via VS Code); the sidebar tile shows the same line under the workspace name.

Screenshots / recordings

Terminal captures from the local run (200-column window).

The toast on the first prompt:

Workspace "e2e-demo-live"
2 of 7 integration tools available · 5 need attention. Details: /workspace

/workspace, with the Status row first:

                             Workspace — e2e-demo-live · 0 memories           esc

                             Search

· 3.3s                     ● Status 2 of 7 integration tools available · 5 need a
                             Refresh Pull the workspace's skills and memory into
                             Sync Re-send local memory the workspace never receiv
                             Unlink Detach this project from the workspace.
                             Done Close this menu.

Status:

                             e2e-demo-live · 2 of 7 integration tools         esc
                             available · 5 need attention

                             Integrations
· 3.3s                     ● ○ GitHub 0 of 1 · no usable connection
                                 create_branch no usable connection
                             ○ Integration 1 0 of 1 · no longer in the catalog
                                 demo_tool no longer in the catalog
                             ○ Integration retired-integration 0 of 1 · no longer
                                 retired_tool no longer in the catalog
                             ○ Jira 0 of 2 · no usable connection
                                 jira_get_issue no usable connection
                                 jira_create_issue no usable connection
                             ● Altimate 2 of 2
                                 altimate_analyze_snowflake_query available
                                 altimate_analyze_snowflake_table available
                             ◌ Power User for dbt 0 of 2 · needs a VS Code window
                                 get_projects via VS Code
                                 get_children_models via VS Code

                             Actions
                             Re-read Read the selection and the last attach again

The boot box in workspace mode, before and after the first message (right column):

What is Altimate Code
Altimate Code is a specialized data engineering harness …

Workspace mode · linked to e2e-demo-live
/workspace — status, refresh, sync, unlink · /skills — the workspace's skills
Integrations: attach on your first message

Workspace mode · linked to e2e-demo-live
/workspace — status, refresh, sync, unlink · /skills — the workspace's skills
Integrations: 2 of 7 integration tools available · 5 need attention — /workspace for the reasons

The sidebar's Workspace tile after the attach:

Workspace
e2e-demo-live
2 of 7 integration tools available
· 5 need attention · /workspace

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

🤖 Generated with Claude Code

https://claude.ai/code/session_01GHBUvb843k1R7UAGi8Ya9b

---

Summary by cubic

Replaces the attach toast’s full engine report with a one-line summary and adds a /workspace Status view for integration details. Attach gaps now come from the engine’s ai.altimate/unfulfilled report, requiring engine version 0.7.2; older engines receive the upgrade offer instead of attaching without gap data. Closes #1307, #1309, and #1311.

Details

• Commits each MCP listing with its report through MCP.snapshot, counts distinct sanitized tools once, and accepts numeric integration IDs.
• Persists a bounded attach snapshot per directory so the menu, sidebar, and boot box can share status across processes while ignoring stale workspace bindings.
• Shows served, partial, missing, and idle integrations with reasons and keys, including snapshot-only rendering when the API is unavailable.
• Posts one sanitized attach report per distinct outcome without exposing raw engine details.
• Adds workspace-mode boot box status lines and calls out tools served through a live VS Code bridge.

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

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}