Repository navigation
No guide for adding an agent after install (#38) - #71
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: Claude <noreply@anthropic.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.
Requested by Simon · project thread
What was wrong
INSTALL.md gets you one agent. Nothing explained adding a second: the one command, the two places an agent lives, naming rules, why an agent might not show in Deck, starting it, or removing it.
What changed
docs/adding-an-agent.md: create (with model choice), naming rules, appearing in Deck (includingMC_INBOX_AGENT_ALLOWLIST), starting withboot-agents.sh, first-boot prompts, first message from Deck, removal, and the likeliest failures with how to tell..specs/38-add-an-agent-guide/SPEC.md.How verified
Ran every step in a clean sandbox with a real Deck and a real runtime: create (VERIFIED), bad name, duplicate name, agent visible in Deck, allowlist hiding it (a write returned 500), boot with the trust prompt, trust answered No (agent exited, day-one skipped) and the fix, a message sent from Deck and the reply arriving in the thread, and removal with Deck dropping the agent. Also green: typecheck, test, check:boundaries, check:leaks, check:licence, check:lib-version, check:dashes, rig self-test.
Not verified
Fixes #38
🤖 Generated with Claude Code
https://claude.ai/code/session_01ByrScobyMJ5eQ8EQZzEcWB
Generated by Claude Code