Work the inbox

The inbox (/inbox) is one feed over every source that can wait on a human: workflow gates, paused agents, induced-skill proposals, profile-version proposals, memory reviews, AI-scaffold proposals, governor recommendations and your notifications. Newest first, one list — the sources are filter chips, not separate tabs.

Read the feed

1. Open Inbox in the sidebar. The chips across the top name every source you can see, each with its live count. A source your role cannot read has no chip at all — not a chip showing zero.

2. Click a chip to narrow the feed to that source. The URL follows the chip (/inbox?source=suggestion), so a filtered inbox is shareable and survives a reload.

3. Decide in place: each row carries the buttons its source allows. Rows you may not decide (for example a governor proposal when you are not the workspace owner) render without decide buttons rather than failing on click.

Note

The sidebar badge counts only what waits on a decision by you — unread notifications never inflate it, and nothing is marked read just because you opened the inbox. Read state moves when you act on a row.

Apply a governor recommendation

A recommendation names the profile, the concrete change and the evidence it stands on — for example “Pin backoffice to claude-sonnet-4-5 · Auto → claude-sonnet-4-5 · 10 successful run(s) · Avg $1.37/task”. The primary button carries the change itself (Pin to claude-sonnet-4-5), never a bare “Apply”.

1. Read the meta line. The run count is the recommended model’s own successful runs, and the average cost is computed over exactly those runs.

2. Open Show details for the full evidence and the proposed configuration diff before you decide.

3. Click the apply button and confirm. SupaCloud sends the model you were shown along with the confirmation: if the recommendation was refreshed to a different model between rendering and your click, the apply is refused rather than silently applying something you never saw.

4. To decline instead, choose Dismiss and give a reason. A dismissal is a decision, not a snooze — the same recommendation is not raised again while it still recommends the same change.

Caution

Applying and dismissing a recommendation, and running the analyzers, are workspace-admin actions: they change agent-profile configuration. Members can read the recommendations but see no decide buttons.

Why a recommendation may be missing

A recommendation is only raised when SupaCloud can name a concrete target. If the busiest profile’s successful runs carry no determinable model — or fewer than three successful runs on the winning model — no card appears rather than an empty one. A run counts as successful when its pull request was merged, or is still open; a pull request that was closed unmerged does not count.

Decided recommendations stay available: with the recommendation chip active, switch on Show decided to read the history, including the reason a recommendation was dismissed.