Agents in the wiki
Agents read wiki pages as session context and can keep them current as the work changes. Whether a proposal lands immediately or waits for a human depends on the space’s agent edit policy.
Reading
Section titled “Reading”Agents read pages in spaces their session can see. The wiki is context, not authority over governance: session scope and environment policy still decide what the agent may act on. A page describing a system is not the same as a connector being live for the tenant.
Suggest
Section titled “Suggest”In spaces with agent_edit_policy: suggest, the agent proposes page changes instead of making them. Each proposal flows to Approvals as a Wiki-kind approval: review what the agent wants to change, on which page, and why, then allow or deny. The decision method is the same gate as any other approval — see Approving agent actions.
Direct
Section titled “Direct”In spaces with agent_edit_policy: direct, the agent may edit pages directly within its session scope. Use direct only where agent-written updates are routine and the space audience accepts them; shared reference stays on suggest.
Finding pages by record
Section titled “Finding pages by record”wiki_search accepts an about filter: pass a record URL and get back the pages about that record. Before writing a new page for a record, search first — the page it needs may already exist. Nothing is auto-created per record, so the check is on the writer: link the existing page instead of duplicating it.
What next
Section titled “What next”- Wiki spaces: per-space policy, visibility, and grants.
- Obsidian sync: editing synced spaces from a vault.
- Approvals: the product reference for the queue all kinds flow through.