A wiki your agents read and write
Architecture and conventions in one knowledge base. Agents cite it when they build and update it when they learn.
Living documents
Pages update when the code does. An agent that changes a module updates its page in the same run.
Answers with citations
Ask how billing works and get the answer with the file and the line.
Specs that start work
Write the change as a spec and send it to intake. The plan keeps its acceptance criteria.
The codebase, explained. Kept current.
Knowledge is what turns a capable agent into a colleague who knows how you do things.
Pages that stay true
Agents write the wiki from the code. From then on, they keep the pages matching it.
Ask the codebase
Questions get answers with sources. Every answer links to code or a page.
Specs to intake
Requirements, design and acceptance criteria in one document. Send it to intake and the plan keeps the criteria.
Frequently asked questions
The questions engineering teams ask before the first run.
In your anturno workspace. You own every page.
anturno never trains a model on your code, pages or traces. What a model provider may keep or train on is set by the terms of the key or subscription you connect.
Yes. Pages have a normal editor, and edits by people take precedence over an agent’s until the next run confirms them.