Command cheatsheet¶
Angelo has no literal slash-commands. Instead, a handful of natural-language phrasings reliably trigger a specific tool or workflow — you say the thing, the agent runs it. This page collects those phrasings in one place so you always have an at-a-glance list; each subsystem's own page repeats its slice of the table under a Commands heading.
A few conventions for reading the tables below:
- Say this lists a few interchangeable phrasings for the same intent — you do not have to match them exactly, they just give the agent (and you) an anchor.
- What runs names the actual MCP tool, CLI command, or workflow it maps to.
- Actions marked (dashboard) are driven from a dashboard's UI, not an MCP tool — the agent can describe or open them, but you perform them in the dashboard. Everything else the agent can run directly.
Coordinator — multi-agent runs¶
| Say this | What runs |
|---|---|
| "coordinate this", "use the coordinator", "run the pipeline", "spin up agents for this" | Scope → design a task graph → execute in waves (create_graph) |
| "run overnight", "let it cook", "independent run", "keep going while I'm away" | An unattended run: keep-awake + pre-cleared approvals, higher rigor, no mid-run prompts |
| "be thorough", "high rigor", "red-team this", "don't cut corners" | rigor="high" with a fuller checker panel and more extension cycles |
| "just do it", "low rigor", "quick and cheap" | rigor="low" (or a solo engineer for trivial work) |
| "extract this corpus", "grounded extraction over these sources", "mine these papers into the schema" | create_extraction_graph (the prep → extract → scribe → audit → link → synthesize pipeline) |
| "resume that run", "pick the stranded run back up" | manage_runs(action="resume") |
See Coordinator.
Memory — persistent knowledge¶
| Say this | What runs |
|---|---|
| "commit", "commit this", "push it up", "commit and push" | Record a memory entry then git commit (+ angelo memory commit flush) — the two travel together |
| "what were we doing", "catch me up", "pick up where we left off" | session(action="pickup") |
| "wrap up", "hand off", "save the session" | session(action="handoff") |
| "log this decision", "checkpoint this", "record that" | record(...) (decision / checkpoint / experiment / note) |
| "remind me to…", "add a todo", "we should do X later" | record(type="todo") under the most specific entry |
| "show the research tree", "what's the plan", "recall" | recall |
| "have we tried this", "search memory for X" | search |
| "where is X defined", "what lives in this module" | codebase() |
| "save this as a skill", "remember how to do this" | skill(action="save") |
| "open the memory dashboard" | launch_dashboard |
See Memory.
Zettelkasten — literature-review knowledge graph¶
| Say this | What runs |
|---|---|
| "note this", "add to the zettelkasten", "remember this definition" | note(action="add") (auto-note protocol) |
| "grow this note", "add depth to X" | note(action="update") |
| "what should this link to", "find connections", "any related notes" | suggest(kind="connections") |
| "suggest structure", "what synthesis notes are we missing", "find the hubs" | suggest(kind="structure") / suggest(kind="concept-hubs") |
| "research X", "what do the sources say about X", "any disagreements on X" | query_topic |
| "frame this question", "map the landscape for X" | frame_question |
| "build the syllabus", "assemble the reading list", "what should I read next" | syllabus(action=…) |
| "remine this org", "reclassify into the dimensions" | remine |
| "look this up in Zotero", "find the paper on X" | zotero(action="lookup") |
| "open the zettelkasten dashboard", "show me the graph" | launch_dashboard |
See Zettelkasten.
Spines — arranging a corpus¶
| Say this | What runs |
|---|---|
| "what spines exist", "list the spines", "which arrangements do we have", "show unfinished spines" | spine(action="list") / schema(action="spines") |
| "suggest a spine", "propose an arrangement", "what dimensions could organize this" | Spine suggestion from a frame result (dashboard) |
| "make a spine", "define an arrangement by methodology", "new organize-by axis" | Create a proposed spine definition (dashboard) |
| "organize by X", "set the default spine" | project(action="set_default_spine") |
| "promote this spine", "materialize it", "build the spine graph" | spine(action="promote") (proposed → spine) |
| "demote the spine", "unmaterialize", "back to a lens" | spine(action="demote") (spine → proposed) |
| "resync the spine", "route the new notes in", "update membership" | spine(action="resync") |
| "verify the spine", "check the synthesis", "audit for overreach" | spine(action="verify") (read-only; semantic=true for the over-reach tier) |
| "delete this spine", "drop the arrangement" | spine(action="delete") |
| "draft against this spine", "walk the spine", "build the outline for this spine" | syllabus/outline build with a spine partition |
| "attach this claim to the spine", "route this into the right dimension" | note(action="attach") |
| "write this dimension's portrait", "mark this node materialized" | note(action="update", replace_body=…) + flip synthesis_status → materialized |
See Spines.
Synapse — grounded navigation and cross-store synthesis¶
| Say this | What runs |
|---|---|
| "answer this from the project evidence", "navigate what we know about X", "give me a grounded answer with citations" | synapse(action="navigate", question=…) → deterministic answer surface or labeled abstention |
| "synthesize", "connect practice to canon", "build the synapse links", "cross-link memory and the zettelkasten" | synapse(action="build") (typed cross-store overlay) |
| "build the claim links", "align practice to claims" | synapse(action="build", kind="claim") |
| "synthesize the claim cells", "ground the practice–claim briefs" | synapse(action="synthesize") |
| "does practice contradict the literature", "add practice to the debate map" | synapse(action="debate") |
| "show the matrix", "practice vs canon", "where do we disagree with the literature" | synapse(action="matrix") |
| "search everything", "look across both stores", "what do we know about X" | synapse(action="search") |
| "frame this across both", "map the landscape (practice + canon)" | synapse(action="frame") |
| "what connects to this", "show the cross-store links" | synapse(action="connections") |
| "find cross-connections", "what links across graphs" | suggest(kind="cross-connections") |
See Synapse, Grounded navigation, and MemDSL v1.
Ops / CLI¶
| Say this | What runs |
|---|---|
| "run doctor", "is my install ok", "check the setup" | angelo doctor |
| "kill angelo", "restart the MCP servers", "stop everything" | angelo kill |
| "update angelo", "pull the latest" | angelo update |
| "set up angelo here", "scaffold the config" | angelo init |