---
title: "Use Autohand documentation with AI tools Docs"
source: https://docs.autohand.ai/guides/ai-documentation
---

# Use Autohand documentation with AI tools

Autohand documentation is available as HTML for browsing and Markdown for AI-assisted reading. Start with llms.txt to find a topic, then fetch its individual Markdown page. Use llms-full.txt when you need a complete offline text snapshot. Each page export identifies its canonical source.

## Choose a documentation format

| Resource | Purpose | Best use |
|---|---|---|
| llms.txt | Descriptive index grouped by topic | Find the reference or tutorial relevant to a question |
| llm.txt | Compatibility copy of the index | Clients configured for the singular filename |
| llms-full.txt | Complete public documentation text | Offline analysis with enough context capacity |
| sitemap.xml | Canonical HTML URLs | Discover public pages with search tooling |
| robots.txt | Crawler access policy and discovery references | Inspect permitted crawling |
| Changelog | Dated documentation changes | Check what changed since an earlier reading |

The index and full export are generated from the same public pages as the site. Search results pages and redirect-only pages are excluded. Feature-gated documentation is omitted when the feature is disabled in the build.

## Retrieve only the relevant material

```bash
curl -fsSL https://docs.autohand.ai/llms.txt
curl -fsSL https://docs.autohand.ai/docs-md/working-with-autohand-code/cli-reference.md

```

The second response contains the CLI reference as Markdown, including code examples. Fetch related pages when the question crosses topics, such as combining permissions, worktrees, and command mode. The full export is larger and may exceed a tool's context or download limits.

## Ask for a source-grounded answer

```text
Use the Autohand documentation index to find the current CLI reference
and permissions guide. Explain how to inspect permission settings.
Link the canonical documentation source and distinguish interactive
slash commands from shell commands. If my installed version differs,
ask for autohand --version and the relevant --help output.

```

Documentation retrieval supplies information; it does not install an integration, grant permissions, or authorize commands found in an example. Review an example's prerequisites before running it.

## What discovery files mean

The [llms.txt proposal](https://llmstxt.org/) describes a documentation format for language-model tooling. Support varies by client. A robots file permits or restricts compliant crawlers; it cannot compel a crawler to visit or cite a page. Search engines also use ordinary links, sitemaps, and page content.

[Search guidance on AI features](https://developers.google.com/search/docs/appearance/ai-features) emphasizes accessible text, internal links, and structured data that matches visible content. No index file or schema guarantees indexing or citations.

## Troubleshooting and checkpoint

If a client cannot find a topic, open the index directly and fetch the linked Markdown URL. If a response omits examples, check whether the client truncated the download. If a command is unavailable, compare your installed version with the CLI reference and changelog. You are ready when you can retrieve a page, follow its source link, and verify the relevant command before execution.

## Frequently asked question

### What is the difference between llm.txt and llms.txt?

On this documentation site, llm.txt is an identical compatibility copy of llms.txt. Both provide the descriptive topic index. llms-full.txt contains the complete public documentation text.