How you manage your site

You change your site by asking. There is no editor and no panel: you tell your agent what you want — “change the opening hours on the contact page” — and it does the work on your site’s files.

Your agent is the interface

An agent is an AI assistant that can act, not only answer. CTXR is built for Claude first: connect your site once, from the app you already use, and manage it in conversation. Other assistants that speak the same protocol (MCP) work under the same rules.

/admin on your domain holds no login form but an explanation written for agents: what this site is, how to connect, what the rules are. To set up a new assistant, hand it that address. It ends with a Discover list — the machine views of the site (llms.txt, the index of the content as data and as a list, the sitemap, the feed, the graph) as plain links, in the order an assistant reads them.

Nothing goes live by accident

Every change is a draft first, staged next to the live site. You get a preview link for the whole site as it would look, and you decide: publish or drop. Before publishing, the site checks itself — links resolve, required fields are filled. If the check fails, the draft stays a draft and you are told why. The check is the same for everyone, so you can delegate freely.

Regret a publish? Your agent takes it back to draft; every earlier version is in history. See Drafts and going live and History and undo.

What an agent can and cannot do

An agent acts with a key, which carries rights: what it may read, write or remove, and whether it may publish. A copywriter’s key may stage drafts but not publish; an intern’s may write to one folder and read nothing else. A request outside those rights is refused, and the site names the missing right.

Keys are handed out by the owner, or by someone the owner allowed to, and nobody can give away more than they hold. There are no accounts, passwords or login sessions. See Who can do what.

What you see, what the agent sees

You see the rendered site and its previews; the agent sees the files: structured content (Schema.org), templates, images. It does not guess where a title or a price lives, and because it works on the files that render the site, there is no second copy that can drift.

Every change leaves a line in the site’s journal: who made it, what was done, what was touched — and what you asked, in your words, when your agent passes that along with the change. Ask “what changed last week?” and you get a plain answer.