What an agent can do
Fifteen tools cover the life of a document: find it, read it, write it, file it, and get it back after a delete.Reading
Writing
Organizing
Deleting and restoring
The tools describe themselves. Each one carries its own documentation, and
get_taxonomy returns your brain’s folders, types, tag registry, and a canonical example of every document format — so a connected agent can discover everything it needs at the moment it needs it. The agent skills teach the full write workflow up front, which saves the discovery round trips.
How rejections work
Validation on every write path is strict, and every rejection states two things: what went wrong, and how to fix it — because the agent, not a person, is the one who has to act on it. An unknown format lists the valid ones. An ambiguous folder name lists the candidate paths and names the field to resend. A body that parses but is not in the format’s exact spelling comes back with the corrected bytes attached, so the retry is mechanical rather than a guess. That way agents correct themselves inside their own loop, instead of leaving a half-written document or a board with no columns for a person to find later. A rejected write is a normal step in a working agent loop, not a fault. Two behaviors are worth knowing as a person:- An agent asked to delete a non-empty folder is told how much would go, and told to confirm with you before anything is removed.
- When a workspace reaches its plan’s document cap, agent writes are blocked with the same explanation you would see. See Plans and limits.
Connect an agent
Sign in from your client, or use an access token.
Agent skills
Skills that teach an agent these tools and the document grammars.
Document formats
What each format is for, and what you can do with it in the app.