Action history and rewindAgents run commands on your machine. This is the record of what actually ran, what it printed, and what it changed, with a way back.What is recordedEvery shell command, file write, dependency install and network call an agent makes, with its output, exit code, duration and the card it belonged to. Kept locally, never uploaded, and it does not expire until you delete it.Three scopesSCOPEUSEPer cardWhat this card did to your machine, in order. The first place to look when a card misbehaved.Per projectEverything across the project’s cards, so you can find the command that changed the environment last Tuesday.Per workspaceThe whole instance, filterable by command, path or exit code.
UndoAny action, or any run of actions, carries Ask the AI to undo. That does not silently reverse anything: it files a card with the actions attached, so the undo goes through Prepare, a plan you approve, and Review like any other change. Reverting a file write is mechanical; reverting a migration is not, and the plan will say which one you are dealing with.RewindRewind is the session-level counterpart: pick any point in a conversation and return to it. The transcript after that point is set aside, file changes made since are reverted in the worktree, and the card’s plan and tasks go back to how they were. You then continue from there with a different instruction.Audit logging on Crew and Fleet is built on the same record, with retention and CSV export, so what a reviewer sees and what you see are the same events.