destructive
ChatGPTOperations that require extra caution or confirmation. dedupe_knowledge is a read-only candidate scan; the remaining actions are consequential. Action names carry their resource because this tool spans resources. action = cancel_task | force_claim_task | dedupe_knowledge | dedupe_pair | unlink | restore_node_version | retire_objective | merge_workspace | cherry_pick_workspace | archive_workspace | archive_component | merge_topics | run_loop_attempt | doctor. run_loop_attempt executes the exact declared shell command supplied in the approval arguments with a scrubbed environment when trusted local repository execution is available; hosted MCP fails closed.
document
ChatGPTCreate long-form artifacts. action = create (a document — a plan, spec, or imported file) | create_diagram (a d2 diagram node).
fetch
ChatGPTFetch one node in full by its shareable id (TASK-N/KNOW-N/COMP-N/DOC-N/DIAG-N/EPIC-N/NODE-N), with its edges — this is how you read a full body (recall/search return summaries). Pass version to fetch a historical snapshot instead of the current one.
inspect
ChatGPTInspect one thing in depth: action = context (a node's neighborhood bundle) | provenance (why a node exists / what it superseded) | briefing (a session briefing) | claim_history (a task's claim/release trail) | workspace (a workspace's detail) | stats (project totals) | loop (fail-closed local Git verification of a task's protected check paths) | rag_status (what automatic topic recall is currently focused on).
knowledge
ChatGPTCapture or curate knowledge. action = create (file a typed fact — decision, lesson, risk, …) | review (mark a node re-verified against current reality). Merging duplicate knowledge lives in the destructive tool.
list
ChatGPTList a collection: what = nodes | components | topics | documents | diagrams | objectives | workspaces | comments | node_versions | projects, with per-what filters. what:"projects" is the project-less bootstrap (discover your slugs). Most collections page with limit/offset; a few return everything up to limit with no further paging.
list_tasks
ChatGPTList tasks, most-recently-updated first, filterable by status, component, assignee, and kind — the roadmap/board view of work. It returns task cards without bodies unless include_body is true; read one task in full with fetch. In clients that display apps, the result also renders as a task board for the user, so summarize it rather than repeating every task.
node
ChatGPTEdit a node or its structure. action = update (edit fields/body) | move (re-file under a component or workspace) | link (add a typed edge between two nodes). Removing an edge (unlink) lives in the destructive tool.
objective
ChatGPTShape the roadmap. action = create | add_milestone | attach (task → milestone) | move (task → objective) | detach | reorder | set_target | achieve. Retiring an objective lives in the destructive tool.
open_project_board
ChatGPTOpen the Stele project board beside this conversation, so the user can watch tasks while you work on them.
open_stele
ChatGPTOpen the Stele app for the user: browse their projects, open tasks, recent activity, and search. Use it when the user wants to see or browse their project, not to answer a question.
organize
ChatGPTProject housekeeping. action = add_component (a durable area of ownership) | rename_topic | feedback (report how well Stele is helping) | pause_rag (pause proactive context injection where the host supports it — a no-op where it doesn't).
project
ChatGPTManage projects. action = create (bootstrap a new project and its root component, owned by you). This is the first thing to call when you have no project yet; discover existing ones with list what:"projects".
recall
ChatGPTOne-call semantic + full-text recall over the graph — a ranked bundle of the decisions, tasks, risks, and documents most relevant to a question or topic. The default way to load context before acting; reach for search only for an exact-term or document-scoped lookup.
search
ChatGPTFind nodes or documents by the words they contain. Nothing here matches by meaning, so use recall for a natural-language question. method "keyword" (default): ranked full-text search over active nodes; terms are AND-combined, and a multi-word query that matches nothing is retried once as an OR of its words. It returns cards, not bodies (default limit 5). method "exact": the matching line per node for a literal substring, or a POSIX regex with regex:true, across every status including done and archived (default limit 50). scope "documents": a line search of document bodies, a literal substring or, with regex:true, a JavaScript regex; it ignores method and type, and limit caps the number of documents unless max_docs is set. Every hit carries id, title, and url; limit is at most 50, with no paging. Read a full body with fetch.
show_node
ChatGPTShow one Stele node (a task, knowledge entry, or document) to the user as a card in the conversation: its title, status, body, links, and provenance. Use it when the user wants to see a node. To read a node yourself, use fetch.
task
ChatGPTTask lifecycle. action = create | claim | complete | release | reopen | force_release | loop_finalize. Claim before you start and complete when done — these route through the atomic claim path that records accountability; never flip a task's status by hand. loop_finalize keeps correctness, independent review, and intent/scope verdicts separate. Irreversible task actions (cancel, force-claim) live in the destructive tool.
timeline
ChatGPTThe project's Timeline: automatic events captured on graph writes and task lifecycle actions, plus one-line custom entries. action = list (read it, newest first, keyset-paginated — not offset-based) | log (append a one-line custom entry). A logged entry is a short journal line, never reasoning or decisions — link the graph nodes that hold those instead. Logging can be turned off for a project; when it is, the call still succeeds but writes nothing.
workspace
ChatGPTManage a workspace overlay. action = create | update. Hosted MCP is stateless, so checkout-local activate/deactivate actions are not exposed; promoting or archiving a workspace lives in the destructive tool.