> ## 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.

# Replying

> Answer CodeObsess's questions and ask for follow-ups.

When CodeObsess needs something from you, it ends with a question and the ticket shows **Waiting for your reply.** On **Tickets**, it moves to **Needs attention**.

## Where to reply

> [tab] GitHub Issues
>
> Write a comment on the issue. While CodeObsess waits for an answer, you don't need `@codeobsess`.

> [tab] Linear
>
> Reply in the ticket's agent session.

> [tab] Jira
>
> Write a plain comment after the question.

> [tab] CodeObsess website
>
> Open the ticket on **Tickets** and use the reply box at the bottom. CodeObsess posts your reply in your ticket tool, naming you. You can also **Dictate** your reply.

## What happens

* A reply brings back the run's work, plan and conversation, and the run continues.
* A reply while the run is working reaches CodeObsess as a follow-up.
* To start over, reply `start fresh — ` followed by the new task.
* If someone pushed to CodeObsess's branch meanwhile, it builds on their work. It never force-pushes.

## Whose reply counts

A ticket's run continues on the AI of the person who asked. A teammate's reply becomes a follow-up on the teammate's own AI.

Members see a ticket's conversation, **Reply** and **Stop** when they can access its repositories, or when it is a ticket they asked for.


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