Docs that keep up with the work.
Every project has its own wiki: folders, pages and typed chapters, linked to the work they describe. Your agents read it before they act and write back what they decide.
Every project has its own wiki: folders, pages and typed chapters, linked to the work they describe. Your agents read it before they act and write back what they decide.
A page is a stack of typed chapters: text, code, diagram, HTML, slideshow or files. Each one is edited and discussed on its own, so two people never collide.
Agents use the same operations you do. They patch a single passage instead of resending the whole page, and everything they write carries their own name.
Link a page to work items, milestones and other pages, visible from both ends. Mention an item like PRJ-12 or another page in the text, and the link is made for you.
Mermaid diagrams, SVG and file trees are drawn from source, and Mermaid follows the app theme, dark mode included. Code chapters highlight all common languages.
An HTML chapter runs your own widget in a sandbox and reads project data with the reader's permissions. A slideshow chapter is a deck you present straight from the page.
Drop in Markdown, HTML, Word or PDF and Manager splits it into chapters along its headings. You check and adjust the split before anything is written.
Connected over MCP, your agent reads and writes the wiki with the same operations you use. On an open page, Edit, Expand, Review and Translate hand that page to your agent in one click.
Say to your agentManager: Write a wiki page in the Architecture folder on how we verify the payment webhook, with a sequence diagram and an example payload.
The agent creates the page in one go: an explanation, a Mermaid sequence diagram and a code chapter with the payload.
Say to your agentManager: Import onboarding.docx from our files into the wiki, one chapter per section.
The document becomes a new page, split along its headings. Ask for a dry run first and the agent reports the split without writing anything.
Say to your agentManager: Which wiki pages has nobody touched since the payments epic shipped, and which still describe the old flow?
The agent reads the page history and the chapters, names the stale pages and, if you ask, fixes the affected chapters in place.
Say to your agentManager: Turn the Q3 review page into a slide deck in the Noir theme.
The agent adds a slideshow chapter styled by Noir. Pick another theme later and the whole deck restyles with it.
The full picture, for when you want to check a detail.
Guides that put this feature to work in a real project.
Change an existing codebase one proposal at a time, with delta specs merged into living specs in your wiki, adapted from the open-source OpenSpec method.
Keep a long write-up moving: plan it in sections, hold your sources and drafts in one searchable place, and see in time which sections are stalling.
Turn scattered notes, papers, and experiments into a project that moves. Workstreams are tracked, the wiki stays current, and Manager shows you threads that went quiet before they go cold.
The wiki holds what stays true after the tasks are closed: architecture, conventions, decisions, runbooks. Your agents read it before they act and write back what they learn, so the next session starts where the last one stopped.
Get early access