A platform you can rewind.

Auditable means there is a forward log of what happened. Reversible means the platform can take the downstream state and restore it to what it was before the log started. Nearly every BPA platform is auditable: Zapier shows run history, Make shows scenario logs, Pipefy has causal lineage. Almost none are reversible, because reversing requires both a log of the prior state before each action and the ability to re-enter every downstream app to restore it. Clone is reversible because the Computer Agent captures prior state on the way in and uses the same screen on the way out.

src/components/architecture.tsx, lines 60-64. The file defines four founding principles of the product. The fourth is Always reviewable, and reads: Every action Clone takes is logged and reversible. Preview drafts before they send. See every file it touched. Roll back an entire morning of work with one click if you need to. That file is public, 159 lines total, and is the reason this page is not a generic BPA listicle.

No, not structurally. Their integration layer is the vendor's API. Once the API call returns success, the downstream app has done the thing, and the BPA platform has no pathway back into the app beyond issuing another API call. Some downstream apps expose a reverse endpoint for a subset of actions (Gmail does not, for instance, not for sent mail outside the 30-second window). Many do not. Clone does not rely on reverse endpoints. It uses the same screen a person would to undo the action, so it works on every app the agent works on.

No. The Always reviewable principle is enforced by the Computer Agent layer, not by the specific connectors. For every ritual you run, the agent captures the prior state of each touched field and the message ID, invoice number, or record ID of each created object. Rollback uses that log automatically; you do not pre-wire a rollback path per app.

As far as your log goes. The log lives at ~/.clone/memory/ on your Mac, and you decide how long you keep it. Most practices keep it indefinitely and version it in git; it is plain markdown, not a proprietary format. A one-click rollback command typically targets a named window like the last run or this morning, but you can also pick a specific action out of the log and reverse just that one.

Yes, the same risk any reversal has in any system. That is why the rollback flow previews the full reverse sequence before executing. You see the eleven actions the agent is about to take, in order, before any of them run. You can confirm, skip specific steps, or cancel. It is not a blind undo button.

RPA platforms (UiPath, Automation Anywhere, Blue Prism) also log UI-level actions, which is closer in shape to Clone than a Zapier or Make log is. The difference is the authoring surface and what the log is used for. RPA execution logs are debugging artifacts, inspected inside the vendor's orchestrator. Clone's log is a first-class product surface: it is markdown on your disk, addressable from the chat window, and designed to be read as prose by the person who ran the ritual.

It stays on your Mac as markdown under ~/.clone/memory/. Uninstalling Clone does not delete it. You can grep it, diff it, commit it to git, or copy it to another machine. This is the fourth principle's structural consequence: the log is not a record inside a vendor cloud that vanishes on cancellation.

When you orchestrate high-volume API calls across a defined set of cloud apps, when you live inside the Microsoft 365 estate, when you need a BPMN artifact an auditor can sign, or when you have a full-time automation admin already. Clone is built for the opposite case: a solo or small practice, a mixed stack with at least one awkward app, and a preference for plain English over a canvas.