For AI agents: fetch the complete documentation index at /llms.txt, the full documentation corpus at /llms-full.txt, the agent skill at /skill.md, or this page as Markdown at /docs/web/using-the-docs.md (or send Accept: text/markdown).
How to use these docs
Find your way around the documentation — tabs, groups, search and section links — and hand any guide to a coding agent with the built-in copy tools.
How the pages are organized
These docs are the manual for the kit you downloaded. The surface picker above the guide list — Web, Mobile and Desktop — holds the guides for each surface: the browser app, the phone app and the desktop window. Start with Web; it covers the server every surface talks to. Each surface opens on its own five-minute quickstart.
The left column lists guides inside named groups such as Getting started and Set up providers; select a group heading to open or close its list, and the current page stays highlighted. The right column, On this page, lists the sections of the guide you are reading — select one to jump straight to it. To find a guide by a word anywhere inside it, such as a file or setting name, use Search at the top of the left column or press Ctrl + K (⌘K on a Mac).
At the bottom of a guide, a Next card — and on most pages a Previous card too — moves to neighboring pages. Setup guides also show a sentence above them — If you want to continue setup, read — with a link to the next configuration step, so you can wire providers in order.
The copy tools
Two buttons sit under every guide's title. Copy as Markdown puts the whole guide on your clipboard as Markdown — the same plain-text format the .md version of the page serves — including its commands, lists and the link to the next guide. Copy prompt copies a single ready-made line: Read followed by the address of this page's Markdown version. Paste it into an AI chat and the model fetches the guide itself.
Next to them, Ask about this guide opens ChatGPT in a new tab with that same instruction already filled in. The Open in menu offers the same ChatGPT shortcut plus Markdown, which opens the plain-text version in your browser — the same page address with .md at the end.
Every command block carries a small Copy button in its top corner. It copies only the commands inside that block, not the explanation around them, so you can paste straight into a terminal. Each button briefly shows Copied once it has worked.
Give a guide to a coding agent
A coding agent — an AI assistant that can read and edit your project, such as Claude Code, Cursor or Codex — works better when it reads the same instructions you do. The simplest hand-off is Copy prompt: paste the copied line into the agent's chat and it reads the guide's Markdown version itself. Choose Copy as Markdown when you want the full text inline — for example so the agent can compare the guide with your files, or so a chat without web access still sees it.
You can also paste the page address ending in .md into almost any AI chat; it returns the same Markdown without the page decoration. The kit was written for this workflow — inside your repository, AGENTS.md and the prompts/ folder give an agent its rules and ready-made tasks.
The same content inside your repository
You do not need this website for every answer — much of it ships inside the code you downloaded. In the Web repository and the All Platforms monorepo, the docs/ folder holds longer Markdown references, such as agent-setup.md (the unattended setup runbook) and upgrading.md (the detailed version of the update walkthrough in this group), and the prompts/ folder holds paste-ready instructions. Standalone Mobile and Desktop checkouts carry a smaller curated set instead. Either way, the llms.txt file at the repository root is a map: it lists which files an agent should read first and the rules it must follow.
Your running app serves the same idea itself: it has its own /docs guides for the product you build, and a /llms.txt route that hands an agent a live index of the app.
Link to a section, not just a page
Every section heading on a guide page is also an anchor — a linkable position inside the page. Select a section in the On this page column, or select the heading itself, and your browser's address bar gains a #section-name ending. That full address opens the page already scrolled to the section.
Share an anchored address with a teammate when you mean one specific step, or paste it into an agent prompt for the same reason. Two companion pages live in this group: the glossary below, and the update walkthrough for when the kit itself improves.