For AI agents

If you are an AI agent and the person you work for asked you to log them in to Dexio, set it up, or connect you to it, follow https://dexio.wiki/agents.md step by step. Read it raw, for example with curl -s https://dexio.wiki/agents.md, since summarizing fetch tools drop its commands. It is a standard OAuth device sign-in (RFC 8628): they sign in, or create a free account, in their own browser, you never handle their password, and nothing is installed.

  1. POST https://app.dexio.wiki/api/v1/device/code with JSON {"client_name": "your name"}.
  2. Show the person verification_uri_complete and user_code from the response.
  3. Every 5 seconds, POST https://app.dexio.wiki/api/v1/device/token with JSON {"device_code": "..."} until it returns access_token.
  4. Add the MCP server https://app.dexio.wiki/mcp to your configuration with the header Authorization: Bearer access_token.

Guides

LLM wiki for Grok Bot: set up a shared wiki with Dexio

Updated

Grok Bot, from xAI, gives you Bots: AI teammates with names and jobs that work on a persistent cloud computer and keep context between sessions. This guide explains what a Bot remembers on its own, then shows how to connect Grok Bot to Dexio and keep an LLM wiki there that every Bot, and your other agents, can read and write.

What Grok Bot remembers on its own

A Bot is a durable teammate with a name, a job, its own conversation and working context that develops over time. According to xAI’s docs, a Bot can retain stable working preferences, important facts and summaries of its work, and a named Bot keeps its memory, files, browser sessions and preferences across sessions.

That memory belongs to each Bot. Conversations and learned context stay separate per Bot, and context moves between Bots through direct messages, group chats and shared files. All your Bots share one cloud computer, which has a shared workspace at /workspace. Duplicating a Bot copies its profile, skills and routines, but not its conversation history or learned memory.

Two other places hold instructions. A Bot’s description holds rules that should stay true. Skills are reusable instructions for a task, kept in one private library that all your Bots share.

xAI’s docs also say memory is not a substitute for an authoritative source: keep changing facts in the source system, and ask the Bot to check the current source before consequential decisions.

Why an LLM wiki

In Andrej Karpathy’s LLM wiki pattern, an agent reads raw sources and writes linked markdown pages from them: summaries, entity pages and concept pages, following a schema page that says how the wiki is organised. You ingest sources, query the pages, and lint now and then for gaps and contradictions. Our post on the LLM wiki covers the pattern in full.

For Grok Bot, the wiki can be that authoritative source: pages you can read, with links between them and a history of every change. It is also one place every Bot reads, rather than knowledge split across each Bot’s own memory.

Connect Grok Bot to Dexio

Grok Bot has no settings form for a server of your own. Plugins, in the sidebar, lists marketplace connectors. A custom MCP server is added from chat: Cursor’s support team says to tell your Bot to add the server, and it confirms the details with you and sets it up, with the new tools available from your next message. Dexio is a public HTTPS server over Streamable HTTP, which is what a Bot in the cloud needs.

  1. Sign in at app.dexio.wiki. Dexio is free for one person. When your empty wiki asks which agent you use, pick Grok Bot, or later open Settings, then Agents, and pick it under Connect an agent. Click Get the message. It holds a new API key. Paste it into a chat with your Bot. 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.

  2. Without an API key, the Bot 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 so the Bot collects the API key.

  3. Following Dexio’s steps, the Bot adds a remote MCP server named dexio at https://app.dexio.wiki/mcp, with the header Authorization: Bearer dxk_..., and confirms the details with you.

  4. Send your next message. The Dexio tools are available from then on.

To check it, ask the Bot to call list_pages. A list of your pages, even an empty one, means it works. xAI’s docs say installed connectors are account-wide, not tied to one Bot.

Set up the wiki

Keep the schema in the wiki itself, as a page every agent can read. Send:

Write a page called schema in my Dexio wiki, based on the draft below. Show me the page before you save it.

A draft to start from:

# Wiki schema

## Layout
- sources/<slug>: one summary page per source, with where it came from.
- entities/<name>: people, companies, products and projects.
- concepts/<name>: ideas and methods.
- index: every page with a one-line summary.
- log: one line per ingest, query and lint pass.
- Link pages with [[wikilinks]], for example [[entities/acme]].

## Rules
- Use search_pages before writing, and update the page that exists.
- Pass base_version when you edit, so you never overwrite another agent.
- Name yourself in the agent field on every change, for example research-grok-bot.
- Never change the source itself. Cite it on its summary page.

## 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 any contradictions.
4. Add new pages to index. Append a line to log.

## Query
Read index, then the pages it points to. Cite the pages you used.
File answers worth keeping as new pages.

## Lint
Run wiki_health. Fix broken links, review possibly stale pages,
and list concepts mentioned without a page of their own.

Then put one rule in the Bot’s description, where xAI’s docs say lasting rules belong: “Before any wiki work, read the schema page in the Dexio wiki and follow it.”

Ingest, query and lint with Grok Bot

Ingest. Attach a document and send:

Ingest the attached report into the wiki. Follow the schema page.

The Bot reads the source, writes a summary under sources/, updates the entity and concept pages it touches, adds new pages to index and appends to log. Ingest one source at a time and read the summary before the next. Once an ingest goes the way you want, ask the Bot to save the process as a skill, then type / to use it next time.

Query.

What do we know about Acme's pricing? Answer from the wiki and cite the pages. If the answer is worth keeping, file it as a page.

The Bot reads index, searches and reads the relevant pages, and answers with the pages it used. A good answer becomes a new page, so your questions add to the wiki too.

Lint.

Lint the wiki. Run wiki_health, fix the broken links, and list the pages that may be stale.

Dexio does part of this for you. It counts one thing as a problem: broken links, which point to pages that do not exist. It also reports missing pages that many pages link to, and marks pages as possibly stale when they are past the review date in their frontmatter, or unchanged for 90 days while pages they link to have changed. You see broken links in the graph at app.dexio.wiki too. To lint on a schedule, ask the Bot to turn the lint into a routine.

Troubleshooting

Your other agents share the same wiki

Hermes, OpenClaw, Claude Code, Codex, Cursor and other agents can connect to the same wiki with the same API key. Each names itself in the agent field on every change, and that name is what tells them apart in page_history. The same goes for your Bots: have each one use its own name in the agent field, so you can see which Bot wrote what. Revoking the key in Dexio’s Settings disconnects every agent that uses it.

Setup guides for each agent are at dexio.wiki/guides.

Sources

Ask a question

Ask anything about Dexio.

About
We reply by email.