Session and history
undo
Step the sheet back through its edit history.
Usage
undo [count]Angle brackets mark required arguments and square brackets optional ones. Available in the schematic and pcb editors. You can issue this yourself, and the AI agent issues the identical command — there is no second, hidden interface.
Arguments
count0 required, 1 optional.
Behaviour
Undoes the last count edits, most recent first, and names each one. Fails when there is nothing to undo, rather than reporting a no-op success: an agent asking to undo an empty stack has lost track of the history, and should see that. Stops early if the stack runs out, and says how many it actually undid. Pushes nothing itself, so an undo is never something you then have to undo. Refused while a route is in progress: the routing engine holds vertices and undo snapshots taken at beginRoute, and stepping the board out from under them leaves the engine describing a board that is no longer there. Commit or cancel the route first.
How the agent uses it
- The agent works in a perceive / act / verify / recover loop: it describes the design, issues
undoor another command, checks the result, and undoes the change if the check fails. - Commands report what they actually did. A refusal is a result, not a silent no-op — which is what lets the agent recover instead of building on a change that never happened.
- Anything the agent can do here, you can do yourself, and the reverse.
Other session and history
Try undo in the editor
Free to start on macOS, Windows and Linux. Bring your existing KiCad and Altium libraries.