From ticket or spec to a tested pull request.
CodeObsess is an AI engineer for early-stage startups. Bug, feature request or small fix: write a ticket or a spec. Get the root cause, a plan, or a pull request with passing tests and screenshots of the change working. Nothing merges without a human.
- ›ticket receivedAdd GST number to invoice PDF
- ?asked on the ticket“All invoices, or only B2B?”
- ✓answer receivedonly B2B
- ›sandbox startedisolated container
- ›implementing3 files changed
- ✓unit tests48 passed
- ✓browser checkinvoice page renders
- ✓screenshots attachedbefore.png · after.png
- ⇢pull request #142 openedreview required
The problem
Every ticket waits for a developer to start from zero. Hours of digging before the first line of code.
CodeObsess does the first pass on every ticket. Your developers start from its findings, plan with it, or hand the whole ticket over. It makes your team faster. It does not replace anyone.
Bug
The root cause with evidence: the failing path, the lines of code, logs and a reproduction. Before anyone opens the code.
Feature request
A plan against your real codebase: the files it touches, the risks, and the work split into tickets.
Take over
Say go ahead on the same ticket and CodeObsess builds it, tests it and opens the pull request.
How it works
From ticket to pull request.
- 01
Write a ticket or spec
CodeObsess picks it up the moment it is created. Follow-up comments join the same task.
- 02
It asks when unclear
A vague ticket gets questions on the ticket, not guesses in code.
- 03
It builds in a sealed workspace
Its own container, your repo's rules, your test suite, a real browser.
- 04
You get a PR with proof
Test results and before/after screenshots inside the pull request.
- 05
You review. You merge.
CodeObsess never merges on its own.
Built for trust
Your code stays yours.
Isolated runs
Every task runs in its own container. One company's code is never visible to another.
What lands on your desk
- ✓A pull request on its own branch
- ✓Results from your own test suite
- ✓Screenshots of the change in a browser
- ✓Progress updates on the ticket
Scoped GitHub access
Install the CodeObsess GitHub App on the repositories you choose, and only those.
Secrets stay yours
Keys are injected only while a task runs.
Your AI key, your spend
Bring your own AI provider key. Usage is billed to you directly — you see every rupee.
Human review, always
Every change arrives as a pull request for your team to approve.
Your repo's rules
It follows the conventions you already wrote down for your team (CLAUDE.md, AGENTS.md).
Pricing
One plan for the pilot.
Limited to the first pilot cohort.
- ✓2 tasks running in parallel
- ✓Unlimited tickets in the queue
- ✓Works with GitHub and your ticket tracker
- ✓Bring your own AI key (Anthropic, OpenAI, Gemini)
- ✓Direct support from the founder
Coming during the pilot
- →Dashboard: active runs, open PRs, merged work and AI spend in one place
- →Roles: admins see everything; developers see their own tasks and PRs
- →Weekly summary reports
FAQ
Questions founders ask.
Does CodeObsess replace developers?+
No. It does the first pass (root cause, plan, or the change itself) so your developers start ahead. Every change is reviewed by your team.
Who owns the code in the pull requests?+
Your startup owns all code in the pull requests. CodeObsess keeps no rights to it.
Which AI models does it use?+
The models available through the API key you connect. You choose the provider and see the bill.
Can it investigate without writing code?+
Yes. Ask for the cause or a plan and it answers on the ticket with evidence and changes no code. When you are ready, tell it to go ahead.
What if a ticket is vague?+
CodeObsess asks clarifying questions on the ticket before writing code.
Can it merge without us?+
No. It opens pull requests; your team merges them.
Which tools does it work with?+
Today: GitHub for code and Linear for tickets. Using something else? Tell us.
How do we start?+
Email us. We set up the GitHub App and ticket connection with you in one call.
Join the first cohort.
We are onboarding 2–3 startups before the end of 2026. Tell us your startup, team size and the first bug or feature you would hand it.
or write to admin.codeobsess@gmail.com