Skip to main content

What it does

With GitHub Issues as your ticket tool, CodeObsess picks up work from issues in your chosen repositories and reports back on the same issue. GitHub Issues needs GitHub as your code host.

Set it up

  1. Choose GitHub Issues as your ticket tool on Home.
  2. Do the Home steps: Link your GitHub account, Connect GitHub, Choose repositories and Connect your Claude account. Inviting your team is optional.
  3. Home shows Your setup is complete and invites you to open your first issue.

Who can start a run

A person who:
  • is a member of your company in CodeObsess,
  • has linked their GitHub account in CodeObsess, and
  • has write access to the repository on GitHub.
Anyone else who writes @codeobsess is ignored, without a reply.

How to use it

  • Start: write @codeobsess in a new comment, or in the issue’s text when you open it. Editing a comment never starts a run.
  • Status: CodeObsess reacts with 👀, then posts one status comment and edits it as the run moves: Queued, Planning, Building, Testing, Needs input, PR ready, Failed or Stopped. It has a View session link.
  • Questions: CodeObsess mentions the person who asked. While it waits for an answer, your next comment counts without @codeobsess. You can also answer on the ticket’s page in CodeObsess. The first answer wins.
  • Try again: a new @codeobsess comment starts a new attempt with its own status comment.
  • Stop: write @codeobsess stop.
The repository decides which repository is the main one for the run.

What access it needs

The CodeObsess GitHub App’s Issues: read and write permission, on top of what GitHub needs.

Disconnect

Change your ticket tool in Settings › General, or uninstall the GitHub App (see GitHub).