Portal pages are edited in words — through the chat with the agent. But sometimes it is easier not to describe an edit in the chat but to show it right on the page: select the phrase that is not right and leave a remark on it. For that, portal pages have comments — a working conversation between the administrator and the agent right on the page.
Why it matters
An edit usually starts in the chat: you describe what to change, and the agent gets to work. But when a remark concerns a particular place on the page — “this number is out of date”, “shorten this paragraph” — it is easier to point at it than to explain in words where it is. A comment remembers both the selected piece of text and the place it was, so the agent does not have to look for anything.
That is how a simple work queue grows out of the remarks: the administrator leaves what to fix, and the agent edits the page according to those remarks. Until a remark is handled it stays on the page and is not lost.
Leaving a remark
Select the text you need with the mouse on an open page — right inside the blocks. As soon as the selection is made, a bar with the Selected text mark and an input field appears at the bottom of the page. The field is built like the chat input: the model and the skill are chosen on the left, and there are two buttons on the right. The bar shows which piece you have selected — that piece becomes the hook for the agent. A long piece can be expanded in full by clicking on it.
- Comment — the orange button on the left. It leaves the remark: the remark lands in the comment thread at the bottom of the page, and the agent works through it on its next pass.
- Send — the button on the right. When what to fix is clear, the portal opens a separate conversation with the agent at once: both the selected piece and your instruction go into it, and the conversation appears in the chat list. The chat panel does not open — the page stays in front of you.
- The model and skill choice is shared with the chat panel: what you pick in one place is what applies in the other. Without a connected agent only the Comment button remains.
- Enter sends, Shift+Enter breaks the line, Escape closes the bar without saving anything.
- If the sending failed, the text and the selection stay in place — you can try again without retyping anything. The reason is shown above the field.
A comment can cover several blocks at once — what matters is only that the selection begins and ends inside the page’s blocks. A selection in the window header or in the tree on the left does not become a comment.
The thread at the bottom of the page
All of a page’s comments are gathered at the bottom, under the content, in a Comments section — with their number next to it. The order is simple: the oldest first, the newest last. Each comment is shown the way it is most convenient to return to: first the selected piece of the page, then the comment itself.
- The author — a remark from a person carries the Admin mark, a comment from the agent carries Agent (such a comment appears only when you have explicitly asked the agent to write one).
- The time — when the comment was written. If it was edited afterwards, an Edited mark appears next to the time.
Editing and deleting
Hovering over a comment reveals two actions: Edit — edits the text in place, and Delete — removes the comment after a confirmation. That way you can add a clarification to your own remark or remove one that has lost its point.
Who can see it
Comments are an internal working tool. Administrators see them, and only inside the portal itself: neither the thread nor the field for a new remark is shown to employees after sign-in or to visitors of the public site. The remarks never go outside — the public site stays as it was.
Ordinary pages only
Only ordinary pages have comments. A template page, which serves many addresses at once, has no folder of its own — one shared sample would be shared by every address, and the remarks would get mixed up. So such pages never have comments, and an attempt to leave a remark is politely refused: reading answers an empty list, and writing is rejected as an invalid request.
Live updates
A new remark appears on an open page by itself, with no reload — both for whoever left it and for every other administrator who has that page open. Comments do not count as a content edit: the page is not marked unread, and neither the tree nor the search index is recounted. A remark is a conversation, not a change of the text.
The list of a page’s comments is part of the page’s answer, and it is returned to administrators and to the management address only — ordinary readers simply get no list at all.
How it works with the agent
The administrator’s remarks are tasks for the managing agent. Having read a comment, the agent treats the selected piece as an instruction: it edits the page the way it was asked, looking exactly at the place in question. A convenient way of working: leave the remarks on the page, send the agent the task “work through the comments” — and come back to a clean page. And when the edit can be described at once, a remark is not even needed: the Send button in the selection bar is enough — the portal opens the conversation with the agent itself.
When the edit is done, the agent removes the remark it has handled — the thread works as a queue to be worked through, not as a log. Its answer the agent leaves not here but in the chat: comments are a one-way channel of requests, and the agent does not write into them on its own. A comment from the agent appears in one case only — when you have explicitly asked it to reply. What else the agent does through its service address is described in the Agent Management section.
Where the comments live
As with everything in the portal, comments are stored in an ordinary file: a file with the remarks lies next to the page’s description. Each remark holds the comment itself (up to 4000 characters), the selected piece of text (up to 2000 characters), the blocks the selection touched, the author (admin or agent), and the time it was created and edited. The file appears only when there are comments, and it disappears together with the last one.
That also means the history of the remarks is visible in the version history, and the agent works with them as with files — reading them and removing the handled ones, while its answers go to the chat. If the file is damaged by accident, the page does not suffer for it: the thread simply renders empty until the file is fixed, and the page itself works as usual.
Next: how a page is arranged on disk — in the Document Format section; how to talk to the agent about an edit — in Chat with the AI Agent; what the agent controls through its service address — in Agent Management.