Administrator, Editor · 1 min

What did your assistant change? TYPO3 History and Log, and how to put it back

When an AI assistant writes to TYPO3, you want to know afterwards what it changed and how to take it back. TYPO3 already keeps that record: History/Undo per record and the Administration log. Writes through AI Foundation's MCP go through TYPO3's DataHandler, so they show there like any editor's change, and the assistant can take its own batch back.

The prompts

  • On our Mustermann Outdoor site, give the Events page the subtitle "Dates coming soon".
    A small change you can see
  • Where can I see in TYPO3 what you just changed, and how would I put it back? Then put it back, please.
    Where TYPO3 records it, and the undo

What does the assistant do?

  1. Ask for a small change. Claude asks before it writes, and you approve.
  2. On our demo it sets the subtitle of the Events page and clears that page's cache.
  3. Ask where to see the change and to put it back. The assistant runs the undo as a dry run first, then for real.
  4. History/Undo of the page shows two entries: the change and the undo, each with its own rollback button.
  5. Administration, Log with the channel content shows both writes under the backend user the assistant signs in as.

Shown in Claude; other MCP assistants work too.

How do I check it and put it back?

Open the page in the backend and choose History/Undo: the entries show old and new values. Administration, Log lists every write. To put a change back by hand, use the rollback button of the entry; to undo through the assistant, ask for records_undo with the batch ID it reported.

What do I need?

AI Foundation with its MCP server switched on, and an MCP-capable assistant; AI Foundation is free.

What can the assistant not do for you?

  • History/Undo and the log show record changes made through TYPO3's DataHandler. Files, file metadata written by other tools and cache clears are not record history: check them where they live.
  • The undo takes back a whole batch of records_apply, as the AI Foundation 2.0 release notes describe it. It refuses when someone changed one of those records afterwards; then roll back in History/Undo, field by field.
  • Writes from tools that return no batch ID, such as the alt text tool, cannot be taken back with records_undo. Ask the assistant to note the old value first.
  • The log names the backend user the assistant signs in as. Give the assistant its own backend user, so its changes are easy to tell apart.
  • On Live, every approved write is live at once. AI Foundation can also hold changes in a TYPO3 draft workspace for review.

Questions about this episode

What does this video show?

Two requests in Claude on our demo install: a change to one page field, then where TYPO3 records it and the undo. Then History/Undo of the page and the Administration log in the TYPO3 backend, and the page on the website.

Do changes made through MCP show in TYPO3's history?

Yes, on our demo: writes through records_apply ran through TYPO3's DataHandler and appeared in History/Undo and in the Administration log under the backend user the assistant signed in as.

Can I roll back in the backend instead of asking the assistant?

Yes. Each History/Undo entry has its own rollback button, as for any editor's change.

In this video
Transcript of the video
  1. 0:00MCP in Practice for TYPO3 · Episode 24: What did your assistant change? TYPO3 History and Log, and how to put it back
  2. 0:03First request: give the Events page the subtitle Dates coming soon. Claude asks before it writes, and you approve.
  3. 0:05Done: one field on one page, saved on Live, and the page cache cleared.
  4. 0:07Second request: where can I see this in TYPO3, and put it back. Claude runs the undo as a dry run first.
  5. 0:09The dry run is clean, so it takes the change back for real.
  6. 0:11It points to History/Undo of the page, where both entries show, and names the batch it took back.
  7. 0:14Now check it in TYPO3.
  8. 0:16History/Undo of the Events page: the change to the subtitle, then the undo. Each entry has its own rollback button.
  9. 0:28Administration log, channel content: both writes, under the backend user the assistant signs in as.
  10. 0:40On the website: the Events page, back as it was.
  11. 0:50A change, checked and put back, with every write approved in the chat.
  12. 0:52All episodes: t3planet.de/en/blog/typo3-mcp-in-practice/

All episodes

Sovereign TYPO3 AI

AI Foundation for TYPO3T3AF

The base every extension runs on. Manage providers, prompts, permissions and costs in one place.

Install free
AI FoundationAI AssistantAI ChatbotAI SearchAI AccessibilityAI LocalizationAI BuilderExplore TYPO3 AI