write_org_doc
Persist something durable — a resolved answer, a runbook, a decision — so the next agent inherits it. Ephemeral chat output is lost. Commits immediately if your grant allows it, and is refused if it does not. The confirmation says whether it CREATED the document or OVERWROTE one, names any directory that did not exist before (check it against what you meant — a typo in folder_path silently mints a new one), and carries a console link you can hand to a person. Set metadata with YAML frontmatter at the top of content: type (one of: meeting-notes, playbook, spec, brand-asset, web-clip, contract, misc — anything else becomes misc), title, summary, and tags as a list. tags is the write-side spelling of what the listing tools call label. status takes active or inactive and is not a label: inactive retires a document — it stays in the folder and stays openable in the console, but agents stop retrieving it. Omit it unless you mean to retire something.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | the document name, e.g. "Q3 summary.md". Cannot contain "/" — put folders in folder_path instead. END IT IN .md unless you mean otherwise: only .md and .mdx render in the console, and anything else opens as plain text with no way to switch. Nothing is appended for you. | |
| share | No | the share id, when this location was shared with you from another workspace — list_org_folders prints it. Omit for your own folders. | |
| token | No | Bearer token identifying the principal. Usually omitted — supplied by the transport (HTTP Authorization header or the server's AGENTLEFS_TOKEN env). Only pass this to override. | |
| content | Yes | ||
| folder_path | Yes | folder names, outermost first, e.g. ["handbook","policies"] |