Kaleta 2.15.0

Kaleta 2.15 lets Claude work as the site's operator: staff ask, Claude does it as drafts, a person publishes – within limits you set.

Requests for Claude

• Staff write requests in the administration (Requests): a title, the text, the page or item it is about, and up to five attachments, which go to Media.
• Administrators get an e-mail about each new request.
• Claude reads requests over its connection (list_requests, and the prompt work_requests). It does the work as drafts and answers with a note and links to the drafts (update_request).
• When a request is marked done, the requester gets an e-mail with the note.
• Requests are treated as data, never as permission to publish or to skip a confirmation.

Comments on drafts

• A shared draft preview can allow comments. The client clicks an element and writes a comment – no account needed, the link is the permission.
• Comments show in the builder and are resolved with one click. Claude can use list_draft_comments and resolve_draft_comment.

Every change says why

• Every tool that changes the site takes an optional reason, such as the request it answers or what the user asked for.
• The change log shows the reason next to the change, and list_changes returns it.

Guardrails for Claude

Settings → Extensions → Guardrails for Claude hold for every connection, on top of its access:

• at most a set number of changes per connection and hour (off by default);
• no deleting, trashing or discarding through Claude;
• protected pages that Claude must not change.

When Claude hits a guardrail, it is told why, so it can tell you.

Agent notebook

• The site keeps notes for whoever works on it next: decisions, wording rules, photo credits, the history of a redesign, and to-dos.
• Notes are kept in the admin (Notebook) and over MCP (read_notebook, write_notebook). Pinned notes show in site_info.
• Claude is asked to read the notebook before larger changes.
• Notes travel with a site export.

Not in this release

Undoing a whole agent session and scheduled agent runs move to a later release. Until then, single changes can be undone with the version history of builds, pages, news and collection items.

Updating

Update from Settings → Backups and updates. It works from every earlier release. The update adds:

• tables for requests, draft comments and the notebook;
• the reason column of the change log.