Undo and the change log

Every change is recorded

Every write to a venue, menu, section or item goes through one path that logs who made it, a plain-language summary, and the exact rows changed — before and after. The actor is either you (or a teammate) or the specific agent tool call that made it, so nothing is ever ambiguous about who did what, or when.

Where to see it in the dashboard

/app/activity lists changes newest first, filterable by time range (7, 30 or 90 days) and by who made them — everyone, agents only, or people only. Opening a row shows its full before-and-after detail, down to the individual column.

Undo

Most rows carry an Undo button: one click reverts exactly that change by replaying its recorded inverse, and the undo itself is logged as a new entry (“Undo: …”). A row that’s already been reverted shows a disabled “Undone” button instead of Undo. A few changes carry no inverse at all and show no Undo button — most notably a slug change: moving your address from oldname.qaema.ai to a new one is recorded like anything else, but it’s locked out of undo from the moment it’s made, not just discouraged.

With your agent

What did the import change in the last hour, and can you undo the price updates?

Your agent reads the log with get_change_log — by time range or a row limit, up to 200 at once — to find the change, then reverts one with undo_change, which also accepts dry_run to show what it would restore before actually applying it.