Your coding agents get things done. We help you trust what they did.

Replume supervises every step your coding agent takes, steers it back the moment it drifts, and proves in a sandbox that the change works, so you supervise less and rework less.

Backed by
ReaktorX/ Exponential VC/
ReaktorX/ Exponential VC/

What changes with Replume

Without ReplumeWith Replume
The agent says “done”, but the task is not. The result is checked against your task before you see it.
Mistakes show up in code review, after the work. Drift is caught and corrected while the agent works.
Every session starts without your project’s history. Project context and memory carry over between sessions.
You learn what the agent really did only by reading the whole diff. A short report of what happened: verified, beyond the request, unknown, plus the time and tokens it cost.

How it works

The agent says “done”. Replume checks that against your task, steers the agent back when something is missing, and verifies the fix in a sandbox.

01

Understands your project

Replume reads your code, tests and past decisions, keeps them as project memory, and connects them to the task you give the agent.

Sample project context
TaskRefund orders paid by card
  • codesrc/billing/refund.ts
  • codesrc/payments/card.ts
  • testtest/refund.test.ts
  • decisionRefunds only within 30 days
02

Steers while the agent works

Replume follows the work in real time against your original task. When the agent drifts, it points it back right away, not after the pull request.

Sample session
10:02 agentAdds refund() to src/billing/refund.ts.
10:05 agentStarts rewriting src/auth/session.ts.
10:05 replumeThat file is outside the refund task. Leave auth as it is and finish the refund.
10:06 agentReverts the auth change and completes the refund flow.
03

Runs it in a sandbox with functional tests

The finished change runs in an isolated sandbox. Tests the agent wrote must fail before the change and pass after it, so a test that proves nothing does not count.

Sample sandbox run · task: filter products by price
04

Reports what is verified, what went beyond, what is unknown

One short report instead of re-reading the whole diff, with the time and token cost of each accepted change.

Sample report · task: avatar upload
Verified✓ Avatars are resized to 256px✓ New test fails before, passes after
Beyond the requestsrc/api/users.ts changed
UnknownFiles over 10 MB not tried
Time and tokens per accepted change14 min · 182k tokens

Every session, reviewed

What the agent did, what was checked, and what it cost, on one screen.

  1. TaskExport invoices as CSV
  2. Agent worksedits, runs, says “done”
  3. during the workSteerdate filter ignored
  4. Sandbox run4 checks, 3 pass
  5. Reportverified · beyond · unknown

Works with the tools you already use

Everything in one layer

Get started

Run one command in your repository. Replume works on top of the coding agents you already use.

Questions

What is Replume?

A supervisor for coding agents. It gives the agent your project context, keeps it on your task while it works, and checks the finished change in a sandbox, so you get a short report instead of re-reading everything.

Which coding agents does it work with?

Claude Code, Cursor, Codex, Hermes Agent and Copilot. It also connects to GitHub and Jira, so the task and the report can live where your team already works.

Does my code leave my machine?

Replume runs alongside your coding agent and keeps its records in your repository. Anything that contacts another service, such as GitHub, Jira or an optional model-based review, is something you connect or switch on yourself. Your coding agent keeps talking to its own provider as it does today.

How does install work?

Run in your repository. It sets Replume up next to the agents you already use; you keep working in your own tools.

How is this different from code review tools?

Review tools read the finished diff. Replume knows the original task and your project, steers the agent while it works, and runs the change in a sandbox, so its report says what is verified, what went beyond the request, and what is still unknown.

What does it cost?

Replume is in beta and pricing is not public yet. Join the waitlist or write to hello@replume.dev and we will get you started.

Do agents really say “done” when the task is not?

Often. In one 2026 study, when coding agents failed a task and stated an outcome, they reported success 75.8% of the time, about 3 out of 4. That is why Replume checks the result instead of trusting the claim.