Guides
CLI Reference
Complete reference for all doxa commands
Every doxa command, with accurate usage and examples.
doxa new#
Scaffold a new documentation project from the Mintlify-style starter template
(a docs.json plus example MDX pages).
Options:
--name <name>— site name written intodocs.json--theme <theme>— starter theme (mint,maple,palm, …)--docs-dir <dir>— output folder (default:docs)--force— overwrite existing files
doxa dev#
Start a local preview of your docs. Inside the monorepo it uses the full Next.js renderer for full fidelity; otherwise it falls back to a lightweight preview.
Options:
--port <n>— port to serve on (default:3000)--lite— force the lightweight preview
doxa agent#
Run the OpenCode-powered AI agent against your local docs. It reads docs.json,
edits your .mdx files directly, and keeps navigation consistent. This is a
one-shot task runner, not an interactive chat.
Options:
--model <m>—free(default),claude,opus,gpt, or a fullprovider/modelid.claude/opusneedANTHROPIC_API_KEY;gptneedsOPENAI_API_KEY.--retries <n>— retry transient OpenCode stalls/errors (default:3)
doxa models#
List the model aliases (free, claude, opus, …), show which credential each
needs, and print the models OpenCode can currently see.
doxa broken-links#
Scan every .md/.mdx page and report broken internal links — references
to pages that don't exist in docs.json or the docs tree.
Example output:
doxa openapi-check#
Validate an OpenAPI/Swagger specification (JSON or YAML).
Reports parse errors and confirms the spec is well-formed.
doxa llms#
Generate llms.txt and llms-full.txt for your docs, following the
llmstxt.org standard. llms.txt is a curated index of
every page grouped by navigation; llms-full.txt concatenates every page's
content into one file for LLM ingestion.
Options:
--site-url <url>— base URL for absolute links (otherwise links are root-relative)
The published docs site also serves these live at /llms.txt and
/llms-full.txt, so this command is for generating static copies to commit or
preview locally.
doxa create#
Create a GitHub repository pre-populated with a starter docs site, then point your dashboard project at it.
Options:
--private— create a private repo--token <token>— GitHub token (otherwise uses$GITHUB_TOKENorgh auth)--docs-dir <dir>— docs folder in the repo (default:docs)--name <name>— site name