Agent document edits

Beta

In-app agent suggestions are reviewed before they change a document. An explicitly authorized MCP command can also edit a document directly using your current permissions and a version check.

Suggestion flow

1. Ask for a document suggestion from a supported lifecycle document surface.
2. Review the preview before anything is inserted or replaced.
3. Dismiss the suggestion to leave the document unchanged.
4. Apply the suggestion to write through the same editor and save path as a human edit.
5. Integrity records provenance for the approved agent apply event.

What agents can change

Agent suggestions can insert or replace document content. They cannot directly change structured planning fields such as status, priority, Team, lead, dates, Version, Initiative membership, Issue links, Health, or permissions.

Safety boundaries

• Suggestions require edit permission on the underlying lifecycle object.
• Applying a suggestion records an agent_apply event with display-safe metadata.
• Search, export, and agent context use plain-text and Markdown projections, not raw Yjs state.
• Restricted Source Library or workspace-object references are redacted, replaced with generic labels, or omitted when the viewer should not see them.
• Hidden or unavailable references are not serialized into exported Markdown or agent-ready payloads.

Related

Mentions through MCP

An authorized MCP agent can mention readable Issues, Features, Initiatives and eligible people without constructing editor data. When editing existing content, it must preserve the editable references returned by the document or comment reader. Unresolved mentions remain restricted; the agent gains no target access. Rich blocks that are outside Markdown editing can be preserved while surrounding text changes. Stale edits fail so the agent can read the current version first.