AgentWiki

Generated pages and durable notes

Open Engineering → AgentWiki. A build creates pages for known databases, clusters, servers, integrations, tools, agents, workflows, skills, and repositories. Start at the overview page to browse by kind.

Generated content refreshes from inventory. Notes are curated by people and agents and survive every build. Use notes for operational findings and custom pages for runbooks. When a source disappears, its page is marked stale and its notes remain. Only custom or stale pages can be deleted.

Read and contribute from a run

exo wiki get overview

exo wiki search "orders database"

exo wiki get database/orders-replica --facts

exo wiki note database/orders-replica --body "Check replica lag before reporting."

exo wiki put --title "Payments runbook" --kind custom --body-file runbook.md

The CLI uses your user login on a workstation and the agent identity inside a run. Dashboard reads require wiki:read; builds and curated edits require wiki:write. Edits retain revisions.

Source repositories

Add a GitHub repository using a deployment's GitHub integration or an encrypted access token. Builds refresh its metadata, top-level layout, clone instructions, and README. Integration access is resolved as the person who added the repository, under the tool's access and policy checks. A failed refresh retains the last successful snapshot and reports the error.

MCP and Markdown access

Create a wiki MCP server to expose a selected slice of the wiki. Scope can combine kinds, slug prefixes, and tags; all configured conditions must match. Choose read, notes, or write access. Generated content stays read-only even for a write token.

The same token serves POST /api/v1/wiki-servers/<id>/mcp and GET /api/v1/wiki-servers/<id>/md/index.md. Send it in the Authorization header. Tokens are shown once on creation or rotation, and a server can be paused without rotating its token. Set include_notes: false to share generated content only.