write_file
Destructive
Create a note, or REPLACE its whole content (needs write access). Adding a line to a note that already exists? Use append_file. Changing one part of it? Use patch_file — write_file with a short text erases everything else. Replacing an existing note: pass base = the version read_file printed at the end of that note, so you never overwrite what someone else (a person, another AI) changed since you read it — if it changed, you are told to re-read and merge. The brain is found from the path: omit workspace and pass it only when the tool asks for it (a new branch, or one present in several brains), with the brain the user chose.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | The note's version as printed at the end of read_file (an ISO timestamp). Pass it when replacing an existing note. | |
| path | Yes | ||
| content | Yes | ||
| overwrite | No | ||
| workspace | No | Brain to act on: its id, «mio» (yours), or the owner's name/email as shown by search. Usually OMIT it: a path that already lives in one brain is found there, for reads and writes alike. Pass it only when the tool tells you to (a NEW branch, or one that exists in several brains) — with the brain the user named; when they were not explicit ASK THEM. A brain where the branch does not exist is refused even if you name it. |