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

# How a run works

> What CodeObsess does from your request to the pull request.

A **run** is one piece of work CodeObsess does on a ticket. It starts when you ask, and ends with a report, a question, or a stop.

## The steps

1. **Queued.** The ticket waits for a free run slot. Your company runs a set number of tickets at the same time; see [Limits](https://docs.codeobsess.com/usage/limits.md).
2. **Reading the request.** Your message wins over the ticket's shape. A question gets an answer. A request to split the work gets a breakdown. A request to build gets a plan.
3. **Checking existing work.** If an open pull request already fixes the problem, CodeObsess says so instead of opening another one.
4. **Planning.** Before writing code, CodeObsess writes a step-by-step plan and has it reviewed. Bigger features get a fuller plan. See [Plans and approval](https://docs.codeobsess.com/tickets/plans-and-approval.md).
5. **Building.** It writes the code, makes a simplicity pass and gets an independent code review. Every finding is fixed or answered.
6. **Testing.** It runs the tests. For screen changes it drives your app in a real browser at desktop and phone widths and takes screenshots.
7. **Pull request.** It opens a pull request and posts its report. See [Pull requests](https://docs.codeobsess.com/tickets/pull-requests.md).

## The report

The report always has the same parts: the pull request, what changed, what was verified, the manual tests for you, what was not verified, and what needs your decision.

## Where you see it

* **In your ticket tool:** a status comment that moves with the run, then the report.
* **In CodeObsess:** **Tickets** shows each ticket on a board or a list: Queued, In progress, Needs attention, In review and Completed. Open a ticket to see its conversation, plan, pull requests and screenshots, with **Reply** and **Stop**.

![The Tickets board with columns Queued, In progress, Needs attention, In review and Completed, each holding ticket cards](https://mintcdn.com/code-obsess/0ZvNNm_XHMri9byY/images/tickets/board-light.png?fit=max\&auto=format\&n=0ZvNNm_XHMri9byY\&q=85\&s=62eea9fda6632d951346d616a6f8961a)

![The Tickets list as a table with ticket, source, state, repository, pull requests, requester and AI columns](https://mintcdn.com/code-obsess/0ZvNNm_XHMri9byY/images/tickets/list-light.png?fit=max\&auto=format\&n=0ZvNNm_XHMri9byY\&q=85\&s=7bf1335dd5a99e5f12d3ab3b8e0d02d1)

## Where the work happens

Each run happens in its own locked-down space, with only the repositories it needs. CodeObsess starts in your product's main repository and may read others. Read-only repositories are never changed. Each changed repository gets its own pull request. See [Security and privacy](https://docs.codeobsess.com/security/privacy.md).

## Screen changes

For a new screen or a big change with no design attached, CodeObsess first shows a mockup and waits for your approval. Reply exactly `approve`, `approved` or `approve design` to approve. Anything else is feedback. A tiny fix goes straight to code.


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