Ticket in.
Merged PR out.Here's the receipt.
Four AI agents take a GitHub issue to a merged pull request. You watch in plain English, answer when asked, and see what each ticket cost.
Runs on your serversWorks in your repoBills to your model key
Add SSO
| AGENT | TIME | COST |
|---|---|---|
| Define | 4m | $0.38 |
| Developer | 22m | $2.11 |
| QA | 9m | $0.71 |
| Tech Lead | 3m | $0.21 |
| TOTAL | 38 min | $3.41 |
- QUESTIONS ASKED
- 1
- APPROVALS
- 1
- PULL REQUEST
- #1187
How it works
Four agents.
One issue. One pull request.
Each agent does one job, then hands off. You step in only where you asked to.
-
Define
Reads the issue. Writes a short spec and the checks it must pass.
Out: spec, 5 checks
Gate: you approve
-
Developer
Writes the code on its own branch. Runs your tests.
Out: commits, green tests
-
QA
Runs every check in a real browser. Keeps screenshots as evidence.
Out: pass/fail, screenshots
-
Tech Lead
Reviews the whole change. Opens the pull request for you.
Out: pull request
Configurable
Your team, your rules. Swap an agent, attach skills, add a gate at any hand-off.
What you see
Plain English.
No terminal required.
Every step is a short sentence. When an agent needs you, it asks and waits.
- 14:02DefineReadthe issue and two linked threads.0:40
- 14:03DefineFoundSSO settings already exist for admins.1:10
- 14:05DefineWrotea spec with five checks.Approved1:50
- 14:06DefineHanded offto Developer.
- 14:07DeveloperReadthe login flow and session code.4:30
- 14:19DeveloperWroteOkta sign-in, behind a setting.11:40
- 14:26DeveloperRanthe test suite. 312 passed.3:20
- 14:28DeveloperHanded offto QA.
- 14:30QAAskedShould SSO users skip email verification?Waited 1m0:55
- 14:31YouYes. Skip it.
- 14:36QARanall five checks in a browser. All pass.4:40
- 14:37QAHanded offto Tech Lead.
- 14:40Tech LeadFoundnothing blocking. Opened PR #1187.2:50
The ledger
An example week.
| # | Ticket | Time | Cost |
|---|---|---|---|
| 412 | Add SSOQ | 38m | $3.41 |
| 409 | Fix CSV export timezone | 31m | $2.87 |
| 415 | Rate-limit the public API | 54m | $5.12 |
| 416 | Typo in invoice email | 22m | $1.94 |
| 418 | Paginate the audit log | 47m | $4.60 |
| 420 | Retry failed webhooks | 35m | $3.08 |
| +6 | 6 more tickets | 3h 41m | $20.06 |
| 12 merged | 7h 28m | $41.08 |
On-prem
Your servers.
Your repo.
Your model key.
One deployment per client, inside your network. It can run with no internet at all. Nothing is mirrored to us.
- Your networkTroupe runs on a server inside it: the four agents, their receipts and logs.
- Your repoIt works in your GitHub, on a branch per run.
- Model endpointIt calls the model with your credential.
- You and your teamYou approve, answer and merge from a browser.
- Public internetCut. The link out is optional.
Network
Air-gap ready.
Installs on your hardware. Runs with no outbound internet if you need it to.
Code
Stays in your repo.
Agents work on a branch in your GitHub. Nothing is copied off your servers.
Models
Your credential.
Bring your own model key. You pay the provider directly, and see every cent.
Before you ask
What buyers ask first.
Which models does it use?
Claude through your own Anthropic key, or Kimi. You pick per team, and can pin a model per agent.
Who reviews the code?
You do. A Tech Lead agent reviews first, then opens the pull request. Nothing merges without your click.
What if an agent gets stuck?
It stops and asks you one question in plain English. The run waits until you answer.
How long to install?
One server, Docker Compose, and a GitHub App.
Bring a real ticket.
Keep the receipt.
Bring a real ticket. We'll run it with you and show you the receipt.
Your email app opened with the request filled in. Press send and we'll reply to pick a time.
Nothing opened? Write to troupe@redpebble.ai.