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>
34 lines
910 B
JSON
34 lines
910 B
JSON
{
|
|
"name": "write",
|
|
"scope": "shared",
|
|
"sessions": "both",
|
|
"risk": "write",
|
|
"exclusive": false,
|
|
"block": "edit",
|
|
"purpose": "purpose",
|
|
"aliases": {
|
|
"cli": [],
|
|
"llembas": [
|
|
"file_write"
|
|
]
|
|
},
|
|
"description": "Create a file, or replace one completely.\n\n- An existing file must have been read first; this fails otherwise.\n- To change part of a file, use edit — never rewrite a whole file to change a few lines.\n- Do not create documentation or README files unless asked. (AGENTS.md is the exception, when your instructions say to make or update it.)",
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"path": {
|
|
"type": "string",
|
|
"description": "File to write"
|
|
},
|
|
"content": {
|
|
"type": "string",
|
|
"description": "The complete new content"
|
|
}
|
|
},
|
|
"required": [
|
|
"path",
|
|
"content"
|
|
]
|
|
}
|
|
}
|