Repository navigation
feat: setup.sh, one command from a clone to a running Deck and two named agents - #148
Merged
Merged
Conversation
…rst-conversation briefs create-agent.sh --status reports complete, incomplete or absent from the homes and writes nothing; complete needs the markers and the whole scaffold, never a lone .kind. --person stamps the user's name into the role brief, --kind member adds a brief for agents the platform agent creates, and the persona probe sources the agent's own .env.secrets in its subshell only. The assistant's first-boot message gains one sentence. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
…d two agents Validates the effective configuration before writing anything, refuses root and a non-loopback HOST, creates the roots, .env and the starter agents through first-run.sh, optionally stores an API key only in the starters' .env.secrets with a pending marker and rollback, verifies both agents, starts Deck on loopback and boots exactly the two starters only if both verified. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
INSTALL.md gains a Quick setup section (python3-yaml joins section 1's apt line), the README and base docs point at it, and the rig runs its unattended block as an ordinary user with a negative control. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
--replace-key needs a key source even with --yes, a pending marker always stops before verification, the key write takes a lock, key paths refuse symlinks and git work trees, and the persona probe redacts credentials from the runtime output it prints. --status parses settings as JSON, checks the brief matches the kind and reads a dangling home symlink as incomplete; first-run and setup trust it instead of a bare kind marker. boot-agents reports prompt and non-prompt waiting separately so setup exits 5 only for real prompts. HOST is parsed like dotenv, --model is validated before any write, and --no-start no longer reports Deck as running. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
…probe on the raw reply Setup re-reads the key and marker state after taking the lock, compares destination paths with their real paths (before staging and renaming too), and treats any Git discovery failure other than not-a-repository as a refusal. The persona probe decides its verdict on the raw reply and redacts only what it prints, reading .env.secrets as shell assignments. --status requires the kind's own role heading. Boot counts the API key approval prompt, and a monitor wait that ends on a prompt, as prompts. HOST drops a trailing comment, and a stale lock is explained, not removed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
… to the marker's pair --status reads absent only when neither the agent home nor its inbox folder exists as any entry; any other state that is not whole is incomplete. A mixed --replace-key repair refuses, before any write and with the marker kept, when the marker's pair is not two distinct agents or differs from the selected starters. Docs qualify credential, status, redaction and acceptance wording. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
…ditional Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
…I, state supported runtimes Install and build output goes to a log under the deck home with a one-line status and the tail on failure. With no agent CLI on PATH setup says once what is needed, which CLIs are supported and where to get them, and still exits 4. README and INSTALL list the supported CLIs; the SPEC records the runtime support read from the code and scopes in-Deck detection as a follow-up. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
…eat/clean-machine-install
… text Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
…eat/clean-machine-install
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Simon Dixon <simon-inkie@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #147 (name your assistant); base is that branch, retarget to main after #147 merges.
What
scripts/setup.sh: one command from a fresh clone to a running Deck (loopback only) and the two starter agents (assistant and platform, viafirst-run.sh), with an optional API key, then a first-conversation brief so the assistant asks what the user does and the platform agent proposes agents to fit.HOSTresolved like the launcher (env, then.env) and refused if non-loopback before any write. Exit codes 2 > 1 > 3 > 4 > 5 > 0. Refuses root; non-TTY needs flags..env.secrets; never in argv or logs; validated before install; written via a recorded pending marker with next-run reconciliation (not an unconditional both-or-neither claim); a lock around the transaction; symlinked homes and git work trees refused.create-agent.sh --status <name>(complete/incomplete/absent, writes nothing, fails closed),--person,--kind member;first-run.shand setup count an agent as existing only when--statussays complete.Spec:
.specs/151-clean-machine-install/SPEC.md. Issue: #151.Review and tests
🤖 Generated with Claude Code