The private flag is gone from MCP write tools for agent keys
Agent-key integrations no longer see the private parameter on MCP write tools, because a private item was never visible to anyone, for builders running agents on the API.
Until now the MCP write tools accepted a private parameter no matter who called them. A private item is only ever visible to the person who created it, and nobody signs in as an agent, so a fact, note or task an agent marked private ended up visible to nobody in the app. The flag looked like it did something and quietly did the opposite of what you wanted.
What's new
- No
privateoption on agent keys.create_note,create_task,update_task,create_contact,update_contactandadd_memos_to_contactno longer offerprivatewhen the key belongs to an agent identity. - People keep it. If you call these tools over OAuth or with your own personal key,
privateworks exactly as before.
Why it matters
Agents exist so people and agents work on the same board, and anything an agent writes is meant to land where your team can see it. Removing a parameter that could only ever hide an agent's work from everyone keeps that promise clear: an agent's notes, tasks and contacts stay visible to the people who share its workspace.
Where to find it
The MCP write tools and their parameters are documented at api.getnoan.com.
Good to know: If you have an agent-key integration that passes private to any of these tools, that option is no longer accepted on agent keys. Drop the parameter from those calls. Integrations on OAuth or a personal key are unaffected.