--- title: reed dev description: Live preview while you edit. --- ```sh reed dev [--dir ] [--content ] [--port ] [--strict-tokens] [--strict-components] ``` Starts a local preview server that rebuilds as you edit `docs.json` and your content. **Prerequisites:** a prior successful `reed prefetch` on this machine, and a Corepack-resolvable package manager. Given those, `dev` needs no network. ## Options Project root. Defaults to the current directory. Content directory. Defaults to `/content`. Port to listen on. Escalate every warning except `DS-D*` to an error. Escalate `DS-D*` design-system warnings to errors. ## What dev does not produce `dev` renders pages. It does **not** write the build-only outputs: no `llms.txt`, no markdown mirrors, no `sitemap.xml`, no `robots.txt`, no `_headers`. The `` link and footer link that point at `llms.txt` are absent under `dev` too, since there would be no file for them to point at. If you are working on a derived surface rather than on pages, run `reed build` and inspect the output directory — `dev` cannot show you those. ## Sharing one compile path `dev` compiles through the same path as `check` and `build`, so a page that renders in `dev` renders in `build`. The difference is which outputs get written, not how the content is interpreted.