Skip to main content
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

Write a comment on the issue. While CodeObsess waits for an answer, you don’t need @codeobsess.

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.