Every tool says its `sessions` (chat, agent or both). The file tools read, write, edit, glob, grep and list are shared; mkdir, mv, rm, search, python and the forge verbs (commit, branch, pr, merge, tag, release) are the chat's; show and recall are new and shared. New fields: `requires` (page, display, forge) with the exact `unavailable` answer, and `confirm: always` for merge, tag and release. knowledge_*, notes_search, note_view and note_manage leave the chat. Default rules for the new tools; modes.json says what `confirm` does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
26 lines
841 B
JSON
26 lines
841 B
JSON
{
|
|
"name": "plan_submit",
|
|
"scope": "shared",
|
|
"sessions": "both",
|
|
"risk": "interact",
|
|
"exclusive": true,
|
|
"block": "tool",
|
|
"purpose": false,
|
|
"aliases": {
|
|
"cli": [
|
|
"plan_exit"
|
|
],
|
|
"llembas": []
|
|
},
|
|
"description": "Present the plan written with plan_write for approval — only in plan mode, and only once the plan is written.\n\n- The user approves it (and you continue, now allowed to make the changes), asks for a revision (change the plan with plan_write or plan_update, then call plan_submit again), or asks you a question (answer it, then call plan_submit again).",
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"path": {
|
|
"type": "string",
|
|
"description": "Ignored: the plan is the one written with plan_write. Kept for callers that still send it."
|
|
}
|
|
}
|
|
}
|
|
}
|