Overview
“Who changed the pricing page?” is one of the most expensive questions in a business. Not because the answer is complicated, but because finding it usually means asking six people, checking a CMS revision history that only shows the last edit, and eventually giving up.
Every action the agent takes is logged with who asked for it, what changed, and when. Export the history for compliance or roll back any change in one click. The log is complete, attributed and searchable in plain language — ask what changed on a page last week and you get the answer, with diffs, rather than a trail to follow.
This is what makes delegating website changes safe. Reversibility and attribution turn a scary change into a cheap one, because the worst case is a single click back to where you were.
How it works
- Ask a question about the history — by page, by person or by date range.
- The agent searches the audit log and lists the matching changes.
- Each entry shows a before-and-after diff, the requester and the approver.
- Roll back any change, or any whole bulk operation, in one click.
- Export the log as CSV when compliance or a client asks for it.
What every entry records
- The person who asked — and the approver, where an approval was required.
- A timestamp, and the environment the change was made in.
- The exact before-and-after values, field by field, or the code diff.
- How the request arrived — the portal, or an external client marked “via MCP”.
- Whether it was published, scheduled, reverted or left as a draft.
Why teams use it
- Who, what, when — every action attributed and timestamped.
- One-click rollback — undo any change instantly, including bulk edits.
- Exportable — hand the log to compliance as CSV without assembling anything by hand.
- Faster incident response — when a page looks wrong, you know what changed in seconds.
Staying in control
The audit log is append-only. Nobody — including administrators and including the agent — can edit or delete an entry, because a log you can quietly tidy up is not a log. Deleting a conversation does not remove the record of what it changed.
Rollback is itself a recorded action, so reverting a change adds to the history rather than erasing it. You can always reconstruct exactly what your site looked like and why.
Availability
The audit log is included on every plan and kept even when conversation history is purged.
Frequently asked questions
How long is the history kept?
For the life of your account, and it survives conversation deletion — clearing a chat does not remove the record of what that chat changed. Enterprise customers can set a longer retention period or export on a schedule to their own storage.
Can an administrator delete entries to hide something?
No. The log is append-only for everyone, administrators included. That is deliberate — an audit trail that privileged users can edit provides no assurance to an auditor, a client or a regulator.
Does it record changes made outside the agent?
It records everything the agent does in full detail. Edits made directly in your CMS or pushed to your repository by a developer are captured by those systems’ own histories, and the agent can read them when you ask what changed on a page — so you still get one joined-up answer.
What exactly does rollback restore?
The precise before-state of that change: field values for content, the previous commit for code. A bulk operation rolls back as a single unit, so undoing a price change across two hundred pages is one action rather than two hundred.
Is the log useful for ISO or SOC 2 evidence?
Yes — this is a common reason teams adopt it. Attributed, timestamped, immutable change records with named approvers are exactly what change-management controls ask for, and CSV export means you can hand over evidence without building a report by hand.
