Skip to content

Releases

2.5.3

Choose a tag to compare

@not-so-fat not-so-fat released this 16 Nov 21:10
5bdaf27

Fix: connecting an OAuth card works on a second host that shares the deck store (NOT-631)

  • A card synced from another machine (deck store shared via git) carries an automatically registered OAuth client bound to that machine's redirect URI. On a host with a different redirect URI (for example a cloud host with AGENT_DECK_PUBLIC_URL), Connect reused that client and the provider (e.g. Linear) rejected the sign-in. Connect now registers a fresh client for the current redirect URI when the stored one was registered for a different address and the provider supports dynamic registration, and clears any secret left by the previous client. Clients you entered yourself, and providers without dynamic registration (e.g. a Slack app), are unchanged.

2.5.2

Choose a tag to compare

@not-so-fat not-so-fat released this 13 Nov 22:43

Change: folder binding is optional — headerless sessions use your default deck (NOT-598, NOT-600 to NOT-606)

  • The connection no longer needs a per-folder pin. Set a default deck once with agent-deck default <deck>; any Cursor, Codex, Claude Code or Muse chat without a pin binds to it. Existing pins keep working and keep precedence. Shipped agent text, skills and docs (NOT-603) now describe this behaviour.

Fix: a deleted or unreadable default deck is reported, not silently treated as no default (NOT-606)

  • agent-deck default with no argument now says so when the saved default is broken: Default deck: <name> (deck no longer exists, run agent-deck default <deck>) when the saved deck id is no longer in the store, and Default deck file is unreadable: <path> when default-deck.json is corrupt or an unknown version. The exit code stays 0, and the file is never auto-cleared or rewritten.
  • A headerless session that lands in the explain-only unassigned session because no default applied now gets one sentence naming the reason: the missing default deck, or the unreadable default-deck.json path. Sessions with no default file see the unchanged message.
  • The shared reader gains readDefaultDeckState (none / ok / unreadable) so callers can tell "never set" from "set but broken"; readDefaultDeck keeps its null result.

Fix: a folder assignment to a deleted deck falls through to the default deck (NOT-604)

  • A local MCP session whose folder assignment (.agent-deck/use.json) names a deck that no longer exists now resolves as if the folder had no assignment: it binds the user default deck when one is set, instead of landing in the explain-only unassigned session. A launch deck header naming a deleted deck still fails closed, and the assignment file is never rewritten.
  • With no usable default deck, the session stays explain-only and the GRANT_REQUIRED reply names the missing deck by its saved deckName, so the user can see which assignment went stale.

Fix: agent-deck stop never stops another home's daemon (NOT-605)

  • runStop now terminates only the supervisor and listeners recorded in the current home's run.json. The port-listener fallback runs only for listeners whose process environment or /health identity reports the same AGENT_DECK_HOME; otherwise it prints that the daemon on those ports belongs to another home and exits 0 without signalling it. This fixes an isolated-home stop SIGTERMing the production daemon on :1110/:1111.

Change: doctor says which deck source a folder would use (NOT-602)

  • agent-deck doctor prints Deck source: <launch header | folder assignment | default deck | none> (<name>) for the current folder, using the same precedence the daemon binds with (launch deck header, then the v3 folder assignment, then the user default deck). A folder with no assignment and no default says none and names the agent-deck default <deck> remedy instead of hiding behind Issues: none.
  • Run from the home folder, the Cursor inspection no longer prints ~/.cursor/mcp.json as both Global and Project: Project prints none (run doctor inside a project folder), and the headerless global fallback no longer raises a bogus missing-workspace-header issue.

Feature: session receipt marks the default-deck fallback (NOT-601)

  • When a session is bound to the user default deck because no folder pin resolved, display_summary in get_session_context and get_session_binding ends with default deck, no folder pin, so the silent fallback is distinguishable from a pinned folder on the first turn. Folder-assigned, launch-selected and session-override receipts are unchanged, as are the status line and menubar text.

Feature: headerless sessions bind the user default deck (NOT-600)

  • A local MCP session that arrives with no deck header and no usable folder assignment now binds the user's default deck ($AGENT_DECK_HOME/default-deck.json) instead of landing in the explain-only session, so a missing pin or unapproved project server no longer makes Agent Deck unreachable. Precedence is strict: launch deck header, then folder assignment, then default deck; hosted and grant-bound sessions are unchanged.
  • Set, show, or clear the default with agent-deck default [<deck>] [--clear], or from the dashboard decks panel (per-deck "Set as default", current-default row with Clear). No default is ever auto-selected.
  • Such sessions report binding source default-deck in get_session_context and get_session_binding. With no default set, or a default naming a deleted deck, behaviour is unchanged (explain-only session, GRANT_REQUIRED).

After upgrade

  • Upgrade the CLI, then restart the daemon (agent-deck start --daemon --no-open after it stops), run agent-deck default <deck> once, and reload each host. Existing folder pins need no change.

2.5.1

Choose a tag to compare

@not-so-fat not-so-fat released this 13 Nov 00:24

Change: agent-deck upgrade --scan <dir> migrates every assigned folder (NOT-577)

  • agent-deck upgrade --scan <dir> (repeatable) walks the directory for folders with a .agent-deck/use.json and converts their legacy mcp-launch entries to pure MCP in one command, including the Cursor project .cursor/mcp.json entry. --scan <dir> --check lists the planned changes and writes nothing. The Codex plugin step runs once per invocation. See docs/MCP_LAUNCH_MIGRATION.md.

Fix: upgrade no longer lets the Codex plugin step block the MCP migration (NOT-576)

  • The MCP config migration now runs and prints before the Codex plugin step.
  • Every codex subprocess has a timeout (60 seconds by default, AGENT_DECK_CODEX_TIMEOUT_MS to override), so a hung codex call cannot stall upgrade.
  • When codex plugin add fails after a successful remove, the output now includes the cache-clearing rm -rf and codex plugin add recovery commands. Agent Deck still never deletes the cache itself.

Change: doctor reports the real connection state per host (NOT-574, NOT-586)

  • agent-deck doctor prints a Host connections block for Codex, Claude Code, Cursor and Muse with one state and a one-line remedy each: no-entry, entry-daemon-down, entry-daemon-up-no-session, connected, folder-not-trusted, folder-not-repository (Muse) or stale-conflicting-entry (Muse). An installed entry alone is no longer reported as OK.
  • A stopped daemon is reported as entry-daemon-down for every host that has an entry, ahead of any trust remedy.

After upgrade

  • Upgrade the CLI, then agent-deck stop && agent-deck start. Run agent-deck upgrade --scan <your projects directory> once to migrate every assigned folder; restart each host afterwards.

2.5.0

Choose a tag to compare

@not-so-fat not-so-fat released this 12 Nov 15:51

Change: Codex, Claude Code, Cursor and Muse connect over plain MCP (NOT-561 to NOT-572)

  • The default connection no longer needs an agent-deck executable on PATH. This fixes the Codex desktop plugin failing to start because the app launches its MCP host with a minimal PATH. Each host now talks HTTP to the daemon directly.
  • agent-deck use <deck> writes a per-folder entry that names the folder in an x-agent-deck-workspace header: .codex/config.toml for Codex, .mcp.json for Claude Code and Muse, .cursor/mcp.json for Cursor. No deck id is written; the server resolves the deck from the folder's .agent-deck/use.json (NOT-562, NOT-563, NOT-567, NOT-571).
  • agent-deck setup --client codex|claude|cursor|muse writes a global headerless HTTP fallback entry. A folder with no assignment lands in the explain-only unassigned session. Agent Deck's own earlier mcp-launch entries are replaced; custom entries are never changed (NOT-565, NOT-567, NOT-570).
  • The Codex, Claude Code and Cursor plugins no longer declare an MCP server; they supply skills and guidance only. The repository-root .mcp.json is removed (NOT-565, NOT-567).
  • What each host needs once: Codex requires the folder to be trusted in ~/.codex/config.toml (a per-run override is not enough); Claude Code and Cursor ask you to approve the project server; Muse loads project config only inside a trusted git repository.
  • The Muse launcher path is retired (NOT-572). agent-deck mcp-launch and the bridge remain for Claude Desktop, which is still launcher-based.

Fix: sessions survive a daemon restart for hosts that never re-initialize (NOT-569)

  • Cursor and Muse do not send a new initialize after the daemon answers 404 to a stale Mcp-Session-Id, so a daemon restart used to end Agent Deck for the rest of that host session. In local mode, a request with an unknown session id whose headers resolve to a deck (workspace header with an assignment, or an authenticated deck header) is now served on a recovered session and keeps working on the same id. Everything else keeps the 404 (no deck-resolving header, unassigned workspace, a session the server itself closed, hosted and grant-bound sessions). /health counts these as recovered sessions.

Fix: doctor reports the real Codex connection (NOT-564)

  • agent-deck doctor reports the Codex host's real connection state and labels the plugin manifest as manifest-only, instead of treating an installed manifest as a working connection.

Docs

  • Design notes with the live evidence behind these changes: docs/design/launcher-free-host-connection.md (Codex and Claude Code, NOT-561) and docs/design/muse-pure-mcp-connection.md (Muse, NOT-568).

Release tooling

  • The packaged-install smoke asserts Muse's headerless HTTP entry and the current setup next steps (it still expected the old launcher entry).

Not changed

  • Claude Desktop keeps using agent-deck mcp-launch.

2.4.0

Choose a tag to compare

@not-so-fat not-so-fat released this 31 Oct 21:38

Change: delegation is MCP-only for agents (NOT-540)

  • The agent-deck-run skill and the generated harness delegation paragraph now delegate exclusively through Agent Deck MCP: get_session_context, optional human-approved switch_deck, start_run (brief built in memory, explicit tool profile, resume id, finalization preparation, pinned playbook version), get_run paged by cursor to a terminal state, and cancel_run. Each failure (missing MCP, WORKSPACE_REQUIRED, provider unavailable, a rejected switch, error/died, cancellation) stops with a short report instead of a CLI remedy; reports carry runId, sessionId, tool profile, and terminal state with no host log path. agent-deck setup refreshes the skill and harness for Claude, Codex, Cursor, and Muse. The host CLI agent-deck run stays available for operators (installation, diagnostics, recovery); see docs/DELEGATION.md.

Feature: MCP run tools (NOT-539)

  • Bound MCP sessions get start_run, get_run and cancel_run: start or resume a host-local run (tool profile, finalization preparation, one pinned playbook version), page its ordered events with a cursor, and cancel it — without the CLI or host loopback access. The deck is the session's live deck (a session-only switch_deck included) and the cwd is the workspace the launcher bound the session to; neither is a tool argument, and .agent-deck/use.json is not consulted. A session launched without a workspace gets WORKSPACE_REQUIRED. Reference in docs/MCP_RUN_TOOLS.md.

2.3.2

Choose a tag to compare

@not-so-fat not-so-fat released this 30 Oct 16:30

Feature: pinned playbook runs (NOT-537)

  • New agent-deck run --playbook-version <playbookId>=<versionId> flag runs one session against a stored older version of one playbook, so a baseline-vs-candidate evaluation can test each version without touching the live playbook. The run's MCP session reads that version's title, body and triggers with no open patches (marked with pinnedVersionId) and cannot file playbook proposals; the pin lives only as long as the run's session.
  • The pin travels through each client's explicit per-run MCP server env (a -c mcp_servers.agent-deck override for Codex, an inline SDK MCP server for Claude), since MCP stdio servers never see inherited process env. Cursor and Muse have no such override, so a pinned run with those clients fails closed before any model work instead of silently reading the live playbook. The pin is recorded in the run's meta.json as playbookPin.

2.3.1

Choose a tag to compare

@not-so-fat not-so-fat released this 29 Oct 23:18

Feature: evaluation scenarios (NOT-535)

  • New dashboard-authenticated REST API for evaluation scenarios, manually curated feedback-derived cases for one target playbook: POST/GET /api/evaluation-scenarios, GET/PUT /api/evaluation-scenarios/:id. A scenario can only become ready with task input, a historical failed output, at least one existing feedback signal and one deterministic expectation. Reference in docs/EVALUATION_SCENARIOS_API.md.
  • The Feedback page can now curate evaluation scenarios from selected signals with a scenario editor. Expectation types match the agent-deck experiment evaluate evaluator.

2.3.0

Choose a tag to compare

@not-so-fat not-so-fat released this 29 Oct 21:17

Feature: agent-deck experiment evaluate

  • New agent-deck experiment evaluate <manifest.json> [--json] command deterministically compares frozen baseline and candidate outputs against per-case expectations (contains, not_contains, equals, regex) and reports absolute artifact complexity (bytes, words, non-empty lines).
  • No optimizer or automatic promotion: candidate generation, live runs and human acceptance stay outside the evaluator.
  • Example manifests in docs/examples/experiments/ (basic, rsi-feedback-smoke); the smoke example turns two real feedback signals into cases and proves the data path, not that the candidate is better.

2.2.0

Choose a tag to compare

@not-so-fat not-so-fat released this 15 Oct 15:12

Feature: same-host agent run API (NOT-479 to NOT-486)

  • One host-local execution service (createAgentRunService in @agent-deck/backend) now owns the client adapters, run records and start/resume lifecycle; agent-deck run and the backend share it with unchanged JSONL and meta.json shapes (NOT-479).
  • Authenticated HTTP API for remote grants that carry the explicit run capability (default off, owner toggle): POST /api/agent-runs (Idempotency-Key required, bounded body, deck allowlist), resume, status and cursor-ordered normalized events. Failed bearers are rate-limited in hosted mode (NOT-480).
  • GET /api/agent-runs/capabilities lists only clients whose real host preflight passes; idempotent POST /api/agent-runs/:runId/cancel signals the run-owned process group; running records are reconciled after a backend restart. Caller reference in docs/AGENT_RUN_API.md; real Codex smoke recorded (NOT-481).
  • Optional finalization behind a separate grant capability (default off): GET /changes returns the reviewed path/sha256/mode manifest, POST /finalize creates exactly one local commit on expectedBaseCommit with a compare-and-swap ref move (NOT-486).

Codex run adapter (NOT-482, NOT-484)

  • Codex runs emit a stable final assistant result.
  • Codex resume allows trusted same-profile edit continuation.

2.1.1

Choose a tag to compare

@not-so-fat not-so-fat released this 15 Oct 06:17
92e3293

Docs / plugin packaging (NOT-432)

  • Cursor Marketplace prep: .cursor-plugin/plugin.json and .cursor-plugin/marketplace.json; public skills cleaned before marketplace submission.
  • Agent plugin now uses a single skills/ source for Claude, Cursor, Codex and Muse, with delegation and setup prerequisites documented in the agent-deck-run and agent-deck-setup skills.
  • Operator-verified delegation poll interval, round cap and Muse initialize instructions in docs/DELEGATION.md.
  • No runtime behavior change.