You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.