Repository navigation
Closed
Labels
agentsAgent lifecycle / bootAgent lifecycle / bootenhancementNew feature or requestNew feature or requestinstallInstall / setup flowInstall / setup flow
Description
Origin
Deck super-assistant MVP roadmap, M3 (8 November 2026), following the maintainer's
direction to let users name their assistant and platform agent during setup.
No matching original Linear ticket was found in a bounded check.
Problem
After install, a new user has to create every agent one at a time with
create-agent.sh, choosing names and roles with no guidance. Deck then lists
all agents as equals in alphabetical order, so nothing tells the user which
agent to start talking to, and no agent knows it is expected to help set up
the others.
Proposed behaviour
- A single first-run command asks for two names: an assistant (the main
orchestrator the user talks to first) and a platform agent (the
"brain surgeon" that edits Deck, makes plugins and creates agents when the
assistant asks). The defaults areinkieanddoctor, both editable. - Both names are checked before anything is created. Each agent is made with
create-agent.sh, so it exists in both homes and each newly created agent
uses the existing boot-phrase check by default. - Each agent gets a short role brief with the other agent's name stamped into
it (the role and peer are stamped text, not something the probe checks). - Deck pins the assistant to the top of the agent list.
- The command can run without prompts (
--assistant,--platform) and is
safe to run again.
Acceptance
- With a working Claude CLI, running the command with two valid names produces
two agents, each passing the persona-loading probe, with the role brief and
the other agent's name stamped into each one'sCLAUDE.md. - An invalid, duplicate or taken name stops the run and creates nothing. A
name is only checked for an agent that is actually missing. - A rerun detects the existing assistant and platform role markers (
.kind)
and skips those agents without probing them. It does not match a pair against
supplied names, and it does not revalidate the peer relationship or the rest
of the scaffold. With both markers present it creates nothing and exits 0,
with no verification claim. With one present it creates only the other, under
the peer name the existing agent already holds. If a different name is
supplied, the saved name is used and a warning is printed; if the peer stamp
is missing, the supplied name (or a prompt) is used. An invalid name at a
prompt can be retried; an invalid name passed as a flag stops the run. - Without a usable Claude CLI, or when verification is skipped, both agents
are created and reported as not verified (exit 4), not as a pass. - The Claude probe (
claude -p) proves persona loading only, not the role
and peer stamps. Those are checked separately by test, plus a manual
interactive check. - Exit codes keep their meaning: 1 refused or scaffold error, 3 failed probe,
4 verification unavailable or skipped, 0 success or a no-op rerun. - Deck shows the assistant first, whatever its name, when it is visible in Deck's existing
inbox roster and the persona and inbox roots match the configuredAGENTS_ROOTandINBOX_ROOT. An unsetAGENTS_ROOTresolves to the
default agents home,~/agents; Deck has no defaultINBOX_ROOT. A populated list
with no assistant keeps its alphabetical order; a missing or unreadable
.kindmeans no pin. The empty-state copy changes to name the first-run
command.
Out of scope
- An in-app setup screen, model keys, connecting mail or calendar, intake.
- Conversational onboarding, the next issue: on first run Inkie asks the user
what they do and has the platform agent create agents to match. - Renaming or removing agents.
- Any new permission system for the platform agent.
- Workflows, a runs view, plugins, workspace, Brain changes, backup.
Implementation
Tracked in PR #147. Issue creation records the agreed work; it does not establish merge or installation acceptance.
Metadata
Metadata
Assignees
Labels
agentsAgent lifecycle / bootAgent lifecycle / bootenhancementNew feature or requestNew feature or requestinstallInstall / setup flowInstall / setup flow
Activity
docs(specs): number name-your-assistant spec as #150 and sync issue text
docs(specs): drop the extra blank line at the end of the #150 issue text
simon-inkie commentedon Nov 19, 2026
Delivered by PR 147 (name your assistant at first run). Closing.