The portal’s content is edited by the managing agent — through a separate service address, not through a browser. There is no editor in the interface at all: neither visual nor text-based — and the “Edit with agent” button merely opens the chat and fills in the context, while the agent makes the actual edit. This order is chosen for cleanliness: every change passes through one place, and the edit history stays readable.
The management key
A key opens access to management. The server settings store not the key itself but its fingerprint — a SHA-256 hash from which the key cannot be recovered. The agent sends the key in a service request header (X-API-Key), and the portal compares the fingerprints. When no management key is set at all, management is disabled: every request to it is declined. That means only someone who knows the key can open editing.
Hence an important rule: the management key is as secret as the administrator’s password. It is not published and not handed to outsiders.
What the agent can do
- Read and save a page — fetch the current description, edit it and write it back.
- Rename, move, copy, delete — put the page tree in order.
- Write a text file and upload a picture — add block texts and images (png, jpg, webp, svg, gif up to 10 megabytes).
- Check the structure — run a page through the checks and see the errors and hints (see Page Validation).
- Run a script and install libraries — debug a calculation script and add what it lacks (see Scripts & Dependencies).
- Learn the portal’s state — the version, the content folder, whether the server is watching the files, how many pages there are, and whether Python is ready. The agent needs this to understand what it is working with before the first edit.
A ready-made guide for the agent
So that the portal does not have to be explained to the agent from scratch, a ready-made guide (a skill) ships with it: how the page tree is arranged, what each of the 27 block types can do, how address templates work, Python scripts, checks and publishing. It lives inside the portal image and updates together with it.
The guide does not need to be installed by hand: when the portal is deployed through Xedant MultiAgent, it is passed to the linked agent automatically — edits can start right away, with nothing to explain.
The portal address and the management key come to the agent from its own environment: being linked to the portal is enough, and naming these values in the conversation is unnecessary. One more convenience follows — a single agent can run several portals, and hosting the application in a subfolder changes nothing for it. And should the guide and the server ever disagree (the guide inside the image may lag slightly behind an update), the server is right: its state, check messages and readable error codes on the page matter more.
Clear rules and limits
- A free name for a copy. When you copy a page and a folder of that name already sits beside it, the portal appends a number —
news2,news3— and never overwrites the existing one. - The root page cannot be deleted. It is the portal’s home page and the whole site’s settings; it cannot be knocked out by accident.
- Address conflicts are explained. When a move touches an existing page or climbs into its own subtree, the portal answers with a clear refusal naming the reason — it never guesses.
- An exact page beats the sample. To put a separate page where an address is served by a sample, the agent first creates a page at that address explicitly — from that moment the address leads to it, and the sample keeps serving the other values.
What the server does itself
On every save the server tidies up after the agent. Large block texts are automatically moved out of the page description into separate files — the description stays short, and the edits in the version history stay readable. The modification time and the page’s version number are stamped by the server too. The agent does not have to think about any of this.
How to know it is all ready
Before saving, the agent can run the page through the checks and see whether there are errors. The check result is kept for a few minutes, so a repeated request does not recompute everything. And the portal’s state tells it whether the files are in place, whether change-watching works, and whether the script environment is ready. That is how the agent verifies the result before readers see it.
Next: how to talk to the agent about an edit — in the Chat with the AI Agent section; what exactly gets checked on a page — in Page Validation; how a page is laid out on disk — in Document Format.