Your product fixes itself
Troopy watches what customers do, say and pay. AI teammates write the fix and open a pull request, and you press Release.
From signal to pull request, on its own.
Self-driving means nobody has to start the work. It does not mean nobody checks it.
- 01
Signals come in
Visits, errors, support chats, payments and feedback. One observation is one signal.
- 02
Teammates sort them
On a schedule, they group signals into problems and put the worst first. Nobody has to ask.
- 03
You approve a plan
The Engineer writes the analysis and the plan. You say yes, or ask for changes.
- 04
A pull request lands
It builds on its own branch and passes every gate. You press Release when you like it.
It notices before anyone files a ticket.
Most problems never reach a ticket. Customers struggle, or they leave. Troopy hears them where they happen, and checks after a release that the problem is gone.
SessionsWhere people get stuck, click again and again, or leave. Read every 3 hours.
IncidentsThe errors and crashes of your apps, from any Sentry SDK.
SupportThe bugs that visitors report in a chat with your Support Agent.
BillingFailed payments, cancellations and the reasons people give, from Stripe.
FeedbackWhat customers said, sorted into themes and tied to your roadmap.
TestsThe places of your product whose checks begin to fail, from the QA tester.
Self-driving, not unsupervised.
The troop starts the work by itself. Nothing reaches your customers until a person says yes.
Its own branches
The Engineer works in a copy of your repo and pushes only troopy/ branches.
No merge by itself
A person presses Release. Auto-release runs only under your grant, with an end date and a daily number.
Every gate first
A second agent reviews the code, your CI runs, and the QA tester tries the change.
Secrets stay in the vault
A teammate names a secret by reference. It never sees the value.
Hard limits
Each run stops at 12 steps, and each teammate at 200 runs a day.
Customer words are data
What a customer types never gives an order to a teammate.
The work finds you.
On the web
Needs you, the board of tickets and every problem with its evidence.
- Coming soon
Troopy for Mac
The same troop in a window of its own, with a word when a fix is ready.
Telegram
The troop writes to you, and you answer from your phone.
CLI and MCP
Read the tickets and drive the troop from your terminal or another agent.
So what is left for you?
- 01
You pick the direction.The troop clears the road. Where the product goes next is still your call.
- 02
The chores leave your desk.Bug fixes and small repairs wait as pull requests. Read, release, move on.
- 03
A small team ships like a big one.Fixes no longer wait for headcount. Your people spend their week on what is new.