Skip to main content
The llms.txt standard is a convention for publishing a site’s content in a form a language model can read directly, without parsing navigation, sidebars, or scripts. We publish both files it defines. They update automatically whenever this documentation changes.

llms.txt

An index: every page with its title, description, and a link. Roughly 14 KB.

llms-full.txt

The entire documentation as one plain-text file. Roughly 330 KB.

Which file to use

Use llms.txt when the model can reach the web. It reads the index, decides which page it needs, fetches that page, and spends nothing on the rest. Use llms-full.txt when it cannot, or when you would rather pay once for complete knowledge than pay per lookup. At around 330 KB it is roughly 80-90k tokens - comfortable in a large context window, wasteful in a small one.
Do not paste llms-full.txt into every request. Load it once at the start of a session, or attach it as a project-level document that persists.

What is inside

llms.txt is a flat list of links with descriptions:
Every link points at the .md version of the page, so following one costs no HTML. llms-full.txt concatenates those pages, each with a header and its source URL:

Any page as markdown

Both files are built from a third mechanism you can use directly: append .md to any URL on this site.
Useful when you know exactly which page you need and do not want either file.

Loading them into a tool

Download llms-full.txt and add it to the project’s knowledge. It persists across every conversation in that project, so the model has the full documentation without you re-attaching it.
SettingsFeaturesDocsAdd new doc, and give it:
Then reference it in chat with @Docs. Cursor indexes it and pulls in the relevant parts rather than the whole file.
Drop the file into the repository where the assistant will find it:
Then tell it where to look: “The 2extract proxy documentation is in docs/2extract-reference.txt - read it before writing the proxy configuration.”
Fetch and cache. The files are static and regenerate when the docs change, so a daily refresh is plenty.
For per-question retrieval rather than bulk loading, the Docs MCP Server is the better fit.

What this is good for

The recurring problem people hit with proxies is not the HTTP client - it is the username format. Geo, session, and protocol parameters are all encoded in the username, in a specific order, with specific separators. A model that has not seen the format invents something plausible and you get a 407. With the reference loaded, the assistant writes:
correctly, first time - including the rule that proxy names cannot contain hyphens.

Next steps

Docs MCP Server

Live search instead of a static file.

MCP Server

When the agent should act, not just read.