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

Relationships

#4714 Swampify: after a swamp start kick-off, the skill hands the pick to the Swampify page and keeps one build per session

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

Part of Swampify onboarding. Follows #4706 (brief entry, compare and the compared state), from a first run.

Repo: swamp-extensions (@swamp/agent-sessions, the swampify skill).

Goal

When Swampify starts from swamp start, the review and the pick happen on the Swampify page, and each build runs in its own agent session. The skill writes the offer and sends the user to the page; it doesn't run the pick in the terminal.

Why

  • On a first run from a kick-off, the skill offered and built in the same session and never pointed back to the page. After the build it offered the next option in the same session again.
  • The page is where the review is designed to happen. Its Swampify! button hands a build brief to a fresh session.
  • compare finds a build's cost from the session that ran this offer's pick and built. Two builds in one session mix their costs; one session per build keeps the figures clean.

Changes

  • offered, after a kick-off brief. Write the offer, summarise it in a line or two (how many options, their names), and send the user to the Swampify page to review and pick. Print the page link the brief carries; with none, name the page (swamp dashboard, then Swampify). Then stop. Pick in the terminal only when the user asks to.
  • compared and graduated, after a build brief. Show the comparison as now, then point to the page for the next pick. Don't offer the next option in this session.
  • Asked directly ("what should I automate?"), with no brief, keep today's terminal flow as the fallback, and mention the page once.
  • Agree the link line's wording with the swamp issue that adds it to the briefs, and pin it with a test.

Out of scope

  • The start page and the Swampify page (swamp).
  • compare itself.

Done when

  • Routing evals cover: a kick-off stops at offered and points to the page; a build brief ends at compared with no next-option offer; a direct ask keeps the terminal pick.
  • The skill passes tessl review at 90% or above, and its trigger and routing evals still pass.
  • A manual run from a swamp start kick-off reaches the page for the pick, builds in the session the page launches, and returns to the page afterwards. The implementer checks this locally, and no transcript content goes in the PR.
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 7 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

11/13/2026, 6:27:41 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
skunk-ape assigned skunk-ape11/13/2026, 2:56:28 PM
Editable. Press Enter to edit.

system commented 11/13/2026, 2:52:57 PM

Classified automatically when this issue was filed.

  • Source: Extensions

If you feel this classification is incorrect, add a ripple to tell us so.

Sign in to post a ripple.