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
Reference documentation for every feature agents ships. Read 00-concepts.md first if you are new — it covers DotAgents repos, resource kinds, and the layered resolution model that everything else builds on.
Source-grounded: every command, flag, and YAML field is sourced from src/. If you spot a mismatch, the code wins — please file an issue.
Core
How agents-cli is laid out on disk and how it decides what to load.
Design decision: fold the secrets broker into a hardened, always-on daemon — make the host reliable enough to carry the critical service rather than routing around it.
Open a command as a tab or split pane in iTerm / Ghostty / tmux, local or over --host. Powers sessions resume.
Conventions used in these docs
Architecture diagrams are ASCII so they render anywhere and diff cleanly.
YAML schema blocks document the on-disk format. Field types come from the matching TypeScript interface in src/.
Command reference tables list every subcommand and flag. Run agents <cmd> --help if anything looks stale.
Recipes are numbered, copy-pasteable shell sequences. They run end-to-end, not toy snippets.
Demo clips under assets/videos/ are 6–15s real terminal captures. The pipeline is documented in ../assets/videos/README.md.
Contributing
Docs live as plain Markdown so they can be edited by anyone and rendered anywhere (GitHub, VS Code preview, future MDX wrapper for agents-cli.sh). When you add or rename a command, update the matching doc in the same PR. The verification loop:
agents <cmd> --help # confirm every flag mentioned in the doc still prints
rg -o '\[[^]]+\]\([^)]+\)' docs/*.md # quick scan for broken relative links