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

Relationships

#4705 Swampify: swamp start offers "Start from your past sessions" and launches a swampify kick-off task

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

Part of Swampify onboarding. Builds on #4650 (contracts in core), #4642 (the swampify skill in @swamp/agent-sessions) and #4643 (the Swampify page, and the swampify start task kind).

Repo: swamp (swamp start and its start page only).

Goal

A new user who has Claude Code or Codex history can pick "Start from your past sessions" on the swamp start page instead of typing a task. Start creates the workspace and launches their agent on a Swampify kick-off brief. The agent then pulls @swamp/agent-sessions, and its swampify skill assesses, offers and builds.

Keep every change inside swamp start:

  • no new CLI command or flag;
  • no new start task kind;
  • no change to the persisted start session's shape.

Approach

Reuse the existing swampify task kind. A swampify brief already carries the task text verbatim with its own steps; the build hand-off from the Swampify page works this way. The kick-off is the same kind with different text, so the brief layout and the launch prompt ("use the swampify skill") stay as they are.

Changes

  • Transcripts signal. Add two booleans to StartSignals: Claude Code transcripts (~/.claude/projects, or CLAUDE_CONFIG_DIR) and Codex sessions (~/.codex/sessions, or CODEX_HOME). Each is an exists check like kubeconfig, with nothing read.
  • Start page option. When either signal is on, show "Start from your past sessions" beside the typed task.
    • Disclosure. Before anything runs, it says plainly what will be read and what will be stored:
      • the agent reads transcript text, prompts and replies included, on this machine;
      • the workspace stores counts, costs and short redacted excerpts;
      • session records stay prompt-free;
      • where the workspace's data goes is the user's choice.
    • Window, defaulting to 30 days.
    • Scope: every session on the machine, with optional excluded paths.
    • Harness: Claude Code or Codex. Only harnesses whose signal is on can be chosen.
    • Workspace name, prefilled with swampify unless a workspace by that name exists; otherwise the usual placeholder.
  • Kick-off text. A constant in core, filled with the chosen window and scope. It tells the agent to:
    1. pull @swamp/agent-sessions;
    2. create the swampify behavior of type @swamp/agent-sessions;
    3. follow the swampify skill from its first state, with this window and scope.
  • Loading the skill. In a new workspace, the skill exists only after the pull. Check whether Claude Code and Codex pick up a skill installed mid-session.
    • If either doesn't, the kick-off text tells the agent to read the installed SKILL.md by its path.
    • If that isn't reliable either, start may run the pull and create the behavior itself before it launches, as long as that stays inside swamp start. Pick one, and write down why.
  • Design docs. Update design/surfaces/start.md and design/surfaces/swampify.md: the signal, the option, the kick-off brief, and that the same task kind serves both kick-off and build.

Out of scope

  • How the skill recognises the kick-off brief; that's a separate extension issue.
  • compare.
  • Telemetry.
  • Other harnesses.

Done when

  • Unit tests cover:
    • the signal with each directory present or absent, and with the environment overrides;
    • the option shown only when a signal is on;
    • the kick-off text, filled with window and scope, and containing no other user input;
    • the workspace name prefill.
  • An integration test saves and launches a kick-off task through the start server with a fake harness, and checks the brief and launch prompt.
  • A manual run on a machine with real history, using both Claude Code and Codex, goes from the start page to an offer item in the new workspace. The implementer checks this locally, and no transcript content goes in the PR.
  • A swamp-uat journey is filed for the start page path.
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 4 MOREREVIEW+ 10 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/13/2026, 12:54:37 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
skunk-ape assigned skunk-ape11/13/2026, 3:05:42 AM

Sign in to post a ripple.