Skip to main content
Every state transition and every autonomous mutating tool call lands in the workspace audit log via AuditService.logEvent(). Mutating actions also capture a before-state snapshot for 7 days, after which the snapshot is purged (the audit entry stays forever).

​
What is audit-logged

New AuditAction values added by the agents feature:
ActionFires when
AGENT_CREATED, AGENT_UPDATED, AGENT_ACTIVATED, AGENT_PAUSED, AGENT_RESUMED, AGENT_DELETEDLifecycle.
AGENT_RULE_SET_CREATEDA new rule-set version is saved.
AGENT_CYCLE_COMPLETEDOne agent cycle finishes (summary in payload).
AGENT_AUTO_ACTIONOne autonomous mutating tool call (tool name + target id in payload).
AGENT_UNDO_APPLIEDSomeone clicked Undo in the workspace Undo Center.
AGENT_PENDING_RESOLVEDA pending item moved from OPEN to RESOLVED / DISMISSED.
AGENT_DATA_SOURCE_PULL, AGENT_RESULTS_PUSHEDInbound / outbound sync activity.
All entries appear in the existing Recent Activity UI alongside human actions, filterable by actor.type=agent.

​
The 7-day undo window

Mutating tool calls populate agent_undo_snapshot.before_state_json before dispatch via a Snapshottable interface implemented per affected service. The snapshot includes everything needed to restore: the entity’s full state at the time of the change, with a currentAfter field captured at undo time for drift detection.

​
What’s undoable

ActionUndoable?Note
Mismatch report state transitionsYesReverts to the prior state (typically OPEN).
Mapping mode preference changesYesRestores the previous mode.
Pending item creationsYes (via dismiss)Dismissing a pending item is equivalent to undo for human-facing escalations.
Memory notesNoManage via the Memory tab — delete notes directly.
Notifications sent (email / Slack / webhook)NoCannot un-send.
External webhook calls (push_results_to_sink)NoEgress side effect.
trigger_mapping_jobNoThe job runs. Future cycles can be cancelled instead.
remember() writesNoSame as memory notes — manage directly.

​
Using the Undo Center

/workspace/agent-undo (UI) or GET /api/v1/workspaces/{wid}/agent-undo (API). The table sorts by expires_at asc so soonest-to-expire is on top.
1

Pick an action

Click a row to see the before / after diff modal.
2

Click Undo

The runtime captures the current state, compares it to the snapshot, and applies the before-state.
3

Drift detection

If a human changed the same entity since the agent acted, the modal shows “Manual change detected — review before undoing” with a three-way diff. You can proceed anyway or cancel.
Undo center

​
Drift-conflict modal

When current ≠ after, the runtime returns MERGE_CONFLICT (HTTP 409) from the undo endpoint. The UI surfaces:
  • Snapshot’s before state
  • Snapshot’s recorded after state
  • Current actual state
  • A two-button choice: Proceed anyway (apply before-state, drop intermediate change) or Cancel.
Choosing Proceed anyway logs an AGENT_UNDO_APPLIED audit entry with the mergeConflict=true flag.

​
Authorization

RoleCan undo?
OWNER, ADMINYes.
MEMBERNo — read-only on the undo center.

​
Snapshot retention

AgentUndoSnapshotPurger runs daily and drops snapshots where expires_at < now(). The corresponding audit entries remain — only the snapshot payload is purged.

​
API

GET  /api/v1/workspaces/{wid}/agent-undo
POST /api/v1/workspaces/{wid}/agent-undo/{snapId}/undo
Response codes for POST .../undo:
  • 200 — applied cleanly.
  • 409 — MERGE_CONFLICT (use ?force=true to override).
  • 410 — snapshot expired (>7 days old).
  • 404 — snapshot not found / already undone.