A coding agent on your machine. The PO in control.

The agent runs on a company VM with a clean folder per case. The PO comments mid-run and it adjusts; rollback is a button with confirmation.

Processes to start with

Features and bugs

The agent does

Implements on the company VM, with the project folder and the case's branch.

The person decides

Reviews in a "Waiting for approval" stage. A send-back counts as rework in the agent's indicators.

Change of course

The agent does

Gets a comment made during the run right away, such as "don't touch the payments module".

The person decides

Comments on the case without waiting for the run to finish.

Rollback

The agent does

Runs the ready-made instruction behind the "Roll back" button.

The person decides

Confirms first. Without confirmation, nothing runs.

Quick actions on the case header

  • Roll back
  • Summarize the case

On the CaseFy screen

Stopping undoes nothing. Resuming picks up where it stopped.

Example: someone stops the run mid-work. CaseFy records who stopped it and keeps what was already done; the next run resumes the same conversation.

Run stopped by a person, with the agent's work kept on the case.
SUP-2026-00007Run stopped by a person; what was already done stays on the case. (CaseFy screen, example data)

For whoever sets it up

The machine connects with a one-time code and only opens outbound connections. Use a dedicated machine: the agent has full access to it. With Azure DevOps connected, the PR and the pipeline show on the case.

Start with a process you already run.

Create an account, connect a company machine and put an agent on one stage. It does the work; you decide when the case moves on.

Free plan forever · No credit card