> ## Documentation Index
> Fetch the complete documentation index at: https://docs.boardrepo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use the handbook from a coding agent

> Give your coding agent the same BoardRepo workflow references that designers and reviewers use.

When a task mentions a board review or a KiCad Push or Pull, start by looking up what the designer should see. The web app and KiCad plugin operate on the same project and saved versions. This handbook covers both.

## Connect to the documentation

In Codex, add the handbook as a documentation source:

```sh theme={null}
codex mcp add boardrepo-docs --url https://docs.boardrepo.com/mcp
```

In another MCP client, add the same URL as a remote HTTP server. You can also read the [page index](https://docs.boardrepo.com/llms.txt) and follow a page as Markdown.

Try asking: **“After I push from KiCad, how do I send a reviewer the exact revision I just saved?”** The answer should connect the plugin’s Push action with version history and the full revision-specific sharing link. For evidence about an actual board, use the [BoardRepo project connection](https://docs.boardrepo.com/integrations.md) with the appropriate account permissions.

## Trace a report across the app and plugin

Suppose someone reports that Pull finished but the old PCB is still on screen. Establish which version was saved on the web, which version reached disk, and what the open editor is displaying. These observations distinguish a version-selection problem from an editor reload. The [Push and Pull guide](https://docs.boardrepo.com/kicad/push-and-pull.md) describes the expected handoff and how to recover an interrupted Pull.

When changing the implementation, open the contributor instructions in your authorized checkout. They identify the code and tests for that revision.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.