- Copies the repositories it needs into a locked-down space of its own, one per run.
- Plans the work and has the plan reviewed.
- Writes the code, gets an independent review, and runs the tests.
- For screen changes, tests the screens in a real browser and takes screenshots.
- Opens a pull request and reports in the ticket what it changed, what it proved and what it did not.
Where it works
- Ticket tools: GitHub Issues, Linear or Jira. Your company uses one.
- Code hosts: GitHub or Bitbucket Cloud. Your company uses one. GitLab isn’t supported yet.
- AI: each person’s own Claude account, or your company’s own AI key. CodeObsess adds no markup on AI. See Which AI runs a ticket.
Proof in every ticket
Every result names the tests that ran, shows browser screenshots for screen changes, says what was not verified, and links the pull requests.Start here
Join your company
Open your invitation and sign in.
First setup
Connect your code host, your ticket tool and your repositories.
Your first ticket
Ask CodeObsess to work on a ticket.
Troubleshooting
A run didn’t start, or something failed.