Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneesskunk-ape

Relationships

#4643 Swampify: read-only panel on the dashboard's Agent sessions page over core's contracts, and agent-sessions.md made current

Opened by skunk-ape · 11/11/2026· Shipped 11/13/2026

Part of Swampify onboarding. Depends on #4650, which moves the Swampify contracts into core (candidate set v2, offer v1, comparison v2) and exports them through the dashboard's lib/agent_sessions/ door.

Repo: swamp (dashboard and design docs).

Goal

Add a read-only Swampify panel to the dashboard's Agent sessions page, locally and under swamp serve. It shows the latest candidate set, the offer made from it and the pick, and any comparisons. Also bring design/surfaces/agent-sessions.md up to date now that the extension is published.

The panel imports the contract from core. There is no copy, no drift test and no pinned hash.

Panel

  • Where it shows. On the Agent sessions page, only when a candidate set exists. If there are candidate sets but no session records, the page itself shows too; today it is hidden unless sessions exist.

  • How it lists. It lists items with data.query, using the contract's predicates and its list select, which includes modelName. It shows the newest item by the contract's rule and names the behavior that owns it.

  • The offer, when there is one. It leads the panel:

    • its state (offered, picked, built or declined);
    • the reading harness and model;
    • each option's name, why, what it becomes and the candidates it stands for;
    • the picked option and its target, when there are any.
  • Candidates. Each candidate is one row:

    • its label, kind, invocation and rank;
    • occurrences, sessions and directories;
    • first and last seen;
    • median weighted tokens and tool calls per occurrence, with the ranges on expand;
    • failure rate.

    Expanding a row shows:

    • its excerpts, as text and never as HTML;
    • its session refs, which link to the session on this page when that record exists;
    • for considered candidates, the offer's reason for leaving them out.
  • Comparisons. These are read through their summary tags, and a body is opened only when expanded. Each shows the target, outcome, history and forward figures as ranges, build cost and break-even.

  • Set header. It shows the window, the scope and when the set was generated. A thin set says so, from the summary's thin, and an empty one says nothing repeated.

  • Computes nothing. The panel shows what the items hold and does no maths.

  • Skipped items. An item the reader skips shows the reader's note and never its content.

  • Access. Under serve, data.query already drops what the viewer may not read. The panel adds no access logic.

Design doc

Make design/surfaces/agent-sessions.md current:

  • Publication. The extension is published. Remove "nothing is published while the extension is a prototype" and the "unpublished" reasoning in the record-version and sync sections.
  • Sync. Records, candidate sets and offers sync like any repo data. Where they go is the user's choice; the extension's job is to say what is read and stored. An exclude pattern still keeps them out of a shared datastore.
  • The panel. Describe the panel next to #4650's Swampify section: what it reads and that it computes nothing.

Out of scope

  • The contracts (#4650).
  • swamp start.
  • Writing anything from the dashboard. It stays read-only.
  • Telemetry.

Done when

  • Unit tests cover the panel's states:
    • absent with no set;
    • a set with no offer;
    • an offer in each state;
    • a thin set and an empty set;
    • a skipped set, offer and comparison;
    • a candidate with and without a comparison.
  • An integration test drives the panel's queries through serve's handlers against a repo holding a set, an offer and comparisons, including items the viewer may not read and items owned by two behaviors.
  • The page appears for a repo that has a candidate set but no session records.
  • agent-sessions.md is updated as described above.
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 16 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/13/2026, 12:25:14 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
skunk-ape assigned skunk-ape11/11/2026, 3:59:08 PM

Sign in to post a ripple.