Product
One console. Five sessions. Nothing left behind.
IndieGent puts coding agents to work on your repos: issues become sessions, sessions become pull requests. You dispatch, direct and review — the machine does the hours.
Seven days free, no card · $19 once · bring your own agent
the operator
Ask one session what matters today.
Tank is one agent with the whole map in front of it — every project you have added, every open issue, everything running right now. It is where the day starts. Ask it what is worth doing, ask it what looks risky, or tell it to dispatch: the sessions open while you are still reading the answer.
It sees the portfolio
Every project, its open issues, and what each running session is doing — in one place, with nothing for you to re-type.
It triages in your words
“Anything worth shipping before lunch?” is a valid question. So is “what did we touch in checkout last week?”
It dispatches the work
Say the word and Tank opens the sessions itself — one agent per issue, each on its own branch, headless if you ask.
- you →anything worth shipping before lunch?
- tank →#86 (acme-api, retry loop has no jitter) and #214 (acme-storefront, promo code lost on retry). About an hour each. Dispatch both?
- you →both, headless
Running
- acme-api #86 · working00:42
- acme-storefront #214 · working00:31
headless
Work that needs no window.
A headless session has no terminal and no window at all. It is dispatched, it works, it wraps up, and it deletes its own workspace while you are doing something else. Five running at once is an ordinary afternoon — the console holds the state so your screen stays yours.
Nothing opens
No terminal window, no tab, no focus stolen mid-sentence. The work happens where you cannot see it, which is the point.
Five at a time
Each session gets its own workspace and its own branch, so concurrent sessions never collide. Fire five before dinner, review five pull requests after.
It raises its hand
A session that hits a decision only you can make stops and says so. Everything else it finishes on its own.
- papertrail #13118:24workingfeed import → streaming parser
- acme-api #9207:11tests128 passed, 0 failed
- castaway #4731:02wrapping upPR #49 opened · closes #47
- acme-ios #58—needs youpush-key strategy · two options staged
- acme-storefront #21424:50donewrapped up clean · workspace deleted
scheduled runs
Your roadmap grows overnight.
Point a scheduled run at your repos and it reads them while you sleep — what changed, what broke, what was left half-finished. By morning it has proposed at most three issues. Accept them into the roadmap, or dismiss them forever. Agents start shaping what gets built; you stay the editor.
Three, at most
A run that finds twenty things still proposes three. The cap is the feature: a queue you can clear in a minute is a queue you will actually read.
Dismissed is forever
Say no once and that idea is never proposed again — not by tonight's run, not by next month's.
Nothing lands unasked
A suggestion is an offer, not a decision. It becomes a real issue when you tick it, and never before.
Last night
- 18:04you close the laptop
- 02:00scheduled run wakes · reads 5 repos
- 02:19run ends · 3 suggestions waiting
- 08:12three cards waiting · nothing else touched
Suggested
acme-api
Add rate-limit headers to the public API
clients are retrying blind
AcceptDismisspapertrail
The import silently drops rows over 1 MB
seen in three runs this week
AcceptDismiss
capped at three per run · dismissed ideas are never proposed again
the lifecycle
Every session ends clean.
One issue, one agent, one branch, one workspace that did not exist this morning and will not exist tonight. The work leaves as a pull request against the issue it came from, and nothing else stays behind. Run twenty sessions a day and your Mac looks exactly as it did before.
Ephemeral workspaces
Every session clones into a workspace of its own and takes it away afterwards. Nothing accumulates, nothing to tidy.
Nothing app-specific is committed
Briefs, session state and scratch files stay outside your repo. A reviewer sees the change and nothing else.
A pull request that closes its issue
Work lands linked to the issue it came from, so merging closes the loop and the board stays honest.
- openworkspace created · branch lazy/promo-code-retry
- briefthe issue and the repo's conventions, written in for the agent
- workthe agent CLI you already use, running on your machine
- wrap upcommitted · pushed · PR #217 opened · closes #214
- clean upworkspace removed · nothing app-specific committed
What it needs
A Mac
macOS 14 or later. A native app that lives in your menu bar, not a dashboard in a browser tab.
Your own agent
IndieGent drives the agent CLI you already run. No second subscription, no key to paste, nothing new to learn.
GitHub
Your repos, your issues, your pull requests. The work lands where your work already lives.
The team you were going to hire.
Seven days with every wall down, no card. Then $19, once.
macOS 14+ · one-time purchase · no subscription