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

# Using coding agents

> Hand the setup to a coding agent. Everything in Pult is code, so there's nothing it can't do.

Everything about Pult lives in your repository: inboxes, resources, actions, roles, views, triage and notifications. That makes it a good job for a coding agent. It can read your app, write the definitions, check them and open a pull request, and your team reviews the result like any other change.

## Docs for agents

These docs come in plain Markdown for agents to read:

* [llms.txt](https://docs.pult.sh/llms.txt) lists every page with a one-line summary.
* [llms-full.txt](https://docs.pult.sh/llms-full.txt) is all of the docs in one file.
* Every page is also available as Markdown at its address plus `.md`, like [/build/actions.md](/build/actions.md). The menu at the top of each page also copies it or opens it in Claude or ChatGPT.

Point your agent at `https://docs.pult.sh/llms-full.txt` before it starts.

## A starting prompt

```
Set up Pult in this app. Read https://docs.pult.sh/llms-full.txt first.

1. Install the pult package and add pult.config.ts.
2. Add a resource for each kind of record our support and moderation work
   touches, next to the code that loads it, with get, find, title and
   render. Add the actions our team does by hand today, with when
   conditions, and use danger, approval or reauth for anything destructive.
3. Add inboxes for the things we currently get alerted about, send items
   from where they happen, and use fingerprints so repeats land on one item.
4. Add a home page with the counts we watch, flags for the features we
   roll out gradually, and roles that match how our team is split up.
5. Run `bunx pult build` and `bunx pult check`, fix every problem, and
   commit .pult/ with the code.
```

Adjust the middle to what your team does. Agents do best with concrete examples: "we ban users from the admin panel at /admin/users", "crashes come from Sentry webhooks in src/webhooks/sentry.ts".

## Checking an agent's work

`pult check` catches what an agent is most likely to get wrong: actions that don't exist, states that don't exist, triage running something dangerous, broken relations and pickers, and definitions that do work when imported. Run it in CI so nothing broken can merge.

`pult diff` shows what a deploy would change, including who gains or loses which permission. Read it before deploying anything an agent wrote.

## Agents working in Pult

Coding agents set Pult up; agents can also work in it. An agent token with a role can triage, assign, comment and run actions through the [Console API](/reference/api), with every step recorded under its name.


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