# Working with agents

Hand a conversation to your own coding agent, or let Bud run one on a task.

There are two ways to get from a thread to a change. With the [factory](/docs/app/guides/factory) set up, make a task from the thread and start it: a coding agent works on it in a sandbox, you follow it on the **Agents** screen, and Bud pushes its branch only after someone approves. Bud never starts a run on its own.

Or keep your own agent, in your editor or terminal. Bud doesn't send your comments to it; you bring the context yourself, and a good thread makes that a copy and paste.

## A useful handoff

Include the page, what should change and how to check it:

```text
Route: /collection
Change: The title pushes the first row below the fold. Keep the title on one line
        and the first row visible at 1440px.
Check: / and /collection in both themes.
```

For code comments, include the file and lines. If a comment is outdated, give the original lines and ask the agent to find the current code.

## Close the loop

Set the thread to **In progress** while the work happens. When the page updates, check it on the canvas, reply with what changed and move the thread to **Needs approval** or **Resolved**.

## Docs for agents

Every docs page is available as Markdown: add `.md` to its URL or send `Accept: text/markdown`. [`/llms.txt`](/llms.txt) lists every page and [`/llms-full.txt`](/llms-full.txt) contains all of them.