LLM wiki for Muse: Karpathy's pattern on Dexio
Updated
Muse is Meta’s personal agent. It remembers what matters to you and builds its own tools, so it can keep an LLM wiki in Dexio that your other agents read and write too. This guide covers what Muse remembers on its own, how to connect it to Dexio, and how to run the wiki with it.
What Muse remembers on its own
Muse runs on Muse Secure VM, a persistent, isolated Linux computer in the cloud that holds your files, Muse’s memory and the credentials for the services you connect.
According to Meta, Muse remembers what matters to you, so it can act on details you mentioned once. You talk to it in one long main chat, and its memory persists across your conversations. Side chats keep separate context for bigger projects. Muse keeps its memory in files you can read and edit directly, and you can tell it to “forget” specific things it has learned.
Muse also works with skills, which Meta describes as detailed instructions to Muse. Meta wrote skills for its built-in connectors, and Muse can write its own custom connectors for services that have their own APIs or CLIs. If a task needs a tool that does not exist, Muse builds it. That is how it reaches Dexio.
Why an LLM wiki
In Andrej Karpathy’s pattern, you collect raw sources and an agent compiles them into linked markdown pages, following a schema you write together. The agent ingests new sources, answers queries from the pages, and lints the wiki for gaps and contradictions. Our post on Karpathy’s LLM wiki covers it in full.
Muse’s memory is about you: your goals, your preferences, the people in your life. A wiki holds what you learn about a subject, as pages with links you can browse as a graph at https://app.dexio.wiki. Hermes, Claude Code and your other agents can read and add to the same pages. The two hold different things, and Muse can use both.
Connect Muse to Dexio
Muse has no setting for adding MCP servers, so it builds its own connection to Dexio and saves it as a skill.
-
In Dexio, pick Muse and click Get the message. It holds a new API key. Paste it into your chat with Muse. If you would rather not paste an API key into a chat, send this instead:
Connect yourself to my Dexio wiki. Read the steps with curl -s https://dexio.wiki/agents.md and follow them. -
Without an API key, Muse replies with a link and a code. Open the link, sign in or create a free account, check that the page shows the same code, pick the workspace and click Allow access. Then reply to Muse so it collects the API key. The link is good for 30 minutes.
-
Following the steps, Muse connects to
https://app.dexio.wiki/mcpover Streamable HTTP with the official MCP SDK, sending the headerAuthorization: Bearer dxk_..., and callslist_pagesto test it. It keeps the API key in its credential store, not in the skill’s code, and saves the integration as a reusable skill so it can use Dexio in future conversations. -
Muse tells you which account, workspace and wiki it will use. You can revoke its API key in Dexio’s Settings at any time.
Meta says Muse uses stored credentials without seeing them: code in the VM only gets a stand-in token, which is replaced with the real one at the network boundary.
Set up the wiki
Start with a schema page, the file that tells every agent how the wiki works. Send Muse:
In my Dexio wiki, write a page at schema describing how this wiki works, starting from the layout below. Then add a line to your Dexio skill: read schema before any work in the wiki.A schema to start from:
# Wiki schema
## Layout
- sources/<slug>: one page per source: what it says, where it came from, when you read it.
- entities/<name>: people, companies, products, places.
- concepts/<name>: ideas that span several sources.
- queries/<slug>: answers worth keeping.
- index: every page, one line each. log: one line per ingest, query or lint.
- Files such as PDFs sit beside the pages, at paths like raw/paper.pdf.
- Link pages with [[wikilinks]], such as [[concepts/pricing]].
## Rules
- Run search_pages before you write, and update the page that exists.
- Pass the base_version from read_page when you edit.
- Name yourself in the agent field on every change: "muse".
- Never put API keys or passwords in the wiki.
## Ingest
1. Read the source and tell me the key points.
2. Write sources/<slug>.
3. Update the entity and concept pages it touches. Note claims it contradicts.
4. Add new pages to index. Append to log: YYYY-MM-DD ingest | title.
## Query
Read index, then search. Answer with the page paths you used.
File answers worth keeping under queries/.
## Lint
Fix broken links, check pages marked possibly stale against newer sources,
list contradictions and concepts that have no page.Edit the schema whenever you catch yourself repeating an instruction.
Ingest, query and lint with Muse
Ingest. Send a source:
Ingest this article into my wiki and follow the schema: <link>Muse reads it, writes a page under sources/, updates the entity and concept pages it affects, notes anything that contradicts what the wiki already says, and updates index and log.
Query. Ask a question:
What does my wiki say about our pricing options? Cite the pages.Muse reads index, searches the wiki and answers with the paths of the pages it used. Answers worth keeping go under queries/, where your other agents find them too.
Lint. Ask for a check:
Lint my wiki and follow the schema.Dexio does part of this already. When an agent writes a link to a page that does not exist, Dexio tells it, and the graph flags it for you. Pages past the review date in their frontmatter, or unchanged for 90 days while pages they link to have changed, are marked as possibly stale. Muse writes the missing pages or fixes the links, checks stale pages against newer sources, and logs the pass. Muse keeps working on a schedule, so you can also ask it to lint every week.
Troubleshooting
- Muse asks you to approve a request. Everything Muse sends to the internet goes through Sentinel, a separate agent that asks you for permission when needed. Approve requests to dexio.wiki and app.dexio.wiki.
- The sign-in stops after the link. The steps tell Muse to end its turn with the link so you can see it. Reply once you have clicked Allow access. If more than 30 minutes have passed, send the message again.
- A 401 error. The API key is wrong or was revoked in Settings. Get a new message from Dexio, or give Muse the API key your other agents use.
- A new chat does not use Dexio. Ask Muse to use the Dexio skill it saved. If it has none, send the message again.
Your other agents share the same wiki
Hermes, OpenClaw, Claude Code, Codex, Cursor and others connect to the same wiki, with the same API key. Each names itself in the agent field on every change, so page_history shows which agent wrote what. Passing base_version on edits means one agent never overwrites another’s change. Revoking the API key in Settings disconnects every agent that uses it.
Guides for each agent are at https://dexio.wiki/guides.