Build and maintain an LLM Wiki

Related notes can grow into a wiki. An LLM Wiki uses an agent to help connect and maintain its pages. They remain ordinary Markdown files you can read and edit yourself.

Before you start

Start with a file and any notes you saved in Build knowledge from your files. Use the in-app Agent panel for this guide. An external MCP client can also save wiki pages if you approve write access when connecting it.

Try a practice Space or a new wiki/ folder before asking the agent to change existing work.

Build the wiki

1. Add your source files.

   In Files, choose New folder and name it sources. Select it, then choose Upload file to add your document. Wait until its passages appear in Search. Keep originals in sources/ and your wiki pages in wiki/.

2. Ask for a small wiki.

   Replace the filename and topic below. Include the paths of any notes you want to build on:

   Read sources/my-document.pdf and my notes about the response requirements.
   Check for existing wiki/ pages and read them before making changes.
   Save the key requirements in wiki/overview.md, with source citations
   returned by your tools. Preserve useful findings and open questions.
   Create or update wiki/index.md with links to the pages and sources.
   Append a short maintenance note to wiki/log.md without inventing a date.
   Keep sources unchanged. Make uncertainty and conflicting evidence clear.

   Keep the Space open while the agent works. The pages should appear in Files.

3. Review the saved pages.

   Open wiki/index.md, follow the overview link, and check its citations against the original passages. Ask the agent to correct unsupported claims, then reopen the page to verify the changes.

4. Save instructions for next time.

   Ask the agent to save these rules in AGENTS.md at the Space root. If that file exists, read it first and incorporate the rules:

   Read wiki/index.md and relevant pages before answering or editing.
   Keep sources/ unchanged. Maintain knowledge in wiki/ as Markdown.
   Use source citations returned by your tools. Distinguish facts from
   inference and keep unresolved conflicts visible.
   Update the index when needed and append maintenance notes to wiki/log.md.
   Do not invent dates.

   Review AGENTS.md. The in-app agent reads it on later turns, but you still need to check its work.

Keep learning from the wiki

Start with what you already know:

Read the wiki and check the original files. What happens if a submission needs corrections? Cite the evidence and point out anything the wiki is missing or gets wrong.

Follow the citations and check the answer. Edit the page yourself, or ask the in-app agent:

Update the relevant wiki page with the answer and citations we checked. Preserve useful findings and open questions. Update the index if needed and add a maintenance note to the log.

Open the saved page to review it. Repeat as new questions come up.

Bring new files into what you know

Upload the new file under sources/ and wait until it is searchable. Give the agent its path and ask it to compare the file with the current wiki, update relevant pages, and cite the evidence. Keep disagreements visible rather than silently replacing earlier findings.

Review the changes. Your wiki should hold both what you learned and what still needs an answer.

If something gets in the way

• No pages appear: ask the agent to save to the named wiki/ paths, then check Files.
• A source is not ready: follow the processing guidance.
• A write reports a conflict: ask the agent to reread the current page and reconcile its changes.
• A claim looks wrong: correct it and check the revised evidence. Citations still need human review.

Explore your knowledge from another agent

Connect your own agent to search and ask questions about the wiki. Bring useful discoveries back through the editor, in-app agent, or an external agent with approved write access. Review the saved changes.