CTXR
Free sandbox

CTXR manual

Work in your own CTXR site step by step: log in with email and authenticator, create a key under Actors, the editor, drafts and publishing, rights, backups and your own AI agent.

This manual shows how to work in the management environment of your own CTXR site: logging in, creating a key, editing content and publishing safely. You manage your site in two ways, which share exactly the same rights and rules: yourself in the browser via /edit, or through your own AI agent.

1. Log in with your email address and an authenticator

Your site runs on yourname.ctxr.app. You find the management environment at yourname.ctxr.app/edit. There is no password: you log in with your email address and a code from an authenticator app (2FA).

  1. Open yourname.ctxr.app/edit and enter the email address you signed up with. Choose Next.
  2. The first time, you receive a six-digit code by email. It is valid for ten minutes and works once. Enter the code.
  3. You are now in a session where you can only read. Choose Set up 2FA, scan the QR code with an authenticator app (for example Google Authenticator) and enter the first code from that app.
  4. As soon as that first code is correct, the same session gets all your own rights: editing, publishing and managing your settings.

Next time you log in with just your email address and the code from your authenticator. No email is sent anymore. A session lasts at most eight hours and ends when you close the tab or log out.

If it does not work

  • After five wrong authenticator codes you have to wait a moment (a minute, longer if it repeats). In the meantime you receive a code by email; once that one is correct, the wait is lifted.
  • New phone or lost authenticator? Reset your authenticator in your own details under Actors. The next time you log in with a code by email and set up a new authenticator.
  • Each code by email works for ten minutes and only once. You can request a new code at most once a minute.

2. Create a key under Actors

An actor is a person (or a thing) with rights on your site. You are the first actor and, as owner, you hold all rights. A key is a long secret that belongs to an actor. One key does two things at once:

  • Log in without 2FA. On the login screen, choose Open with a key instead and paste the key. No authenticator is asked; you have your actor's rights.
  • Work agentically. Your AI agent uses the same key to connect to your site over MCP, at yourname.ctxr.app/mcp. Your agent can then read and write drafts with exactly the rights your actor has.
  1. Log in with email and authenticator (step 1). A session opened only with an email code cannot create keys yet.
  2. Open Actors in the menu bar and choose your own actor.
  3. Create a key and give it a clear label, for example claude.
  4. Copy the key right away. It is shown only once; if you lose it, you create a new one.

Good to know

  • Treat a key like a password: keep it in a password manager and never share it in chat or email.
  • You can have at most five keys per actor. If you create a key with the same label again, it replaces the old one: the old one stops working immediately.
  • Suspect a key has leaked? Replace it right away or remove it under Actors.
  • Want a colleague or an AI agent to be allowed less than you? Create a separate actor with only the rights it needs (see chapter 5).

3. Tour of the editor

A menu bar runs along the top. These are the parts:

  • Add page: create a new page or item. You choose a type and fill in the fields, in all languages of your site.
  • Look at pages: all pages of your site. Open a page to edit its fields and see next to it what the site looks like, on desktop, tablet or phone.
  • View all media: all images, videos and documents. Drag files in to add them; they arrive as drafts first. You also see where a file is used.
  • See your lists: hand-made lists, such as highlighted items. You name the list, choose which items are in it and set the order.
  • Types: the kinds of content on your site and what each type contains.
  • Browse files: all files behind your site, in four folders: data (the content, one file per thing), theme (the design, handle with care), assets (images, media, documents, fonts) and guide (the site's own rules for agents).
  • Organisation: the details of your organisation.
  • Actors: who has access and what they may do.
  • Check usage: what your plan allows and how much you use: storage, number of items and number of actors.
  • Go to… (⌘K): jump quickly to a page or section by typing.
  • Documentation: explanation of how everything works, including how to connect your own AI agent.

4. Working with drafts: change, preview, publish

Nothing you change goes live immediately. Every change starts as a draft.

  1. Change. Edit a page, text or file and save. The change is kept as a draft; visitors see nothing.
  2. Preview. Check the result in the preview of your own site.
  3. Publish. If it is right, you publish. The system checks first that everything is in order; only then does the change go live. You can publish a single change or a whole round at once.

Changed your mind? Discard the draft, or take a published file back to draft. That way you can work calmly without visitors seeing anything.

5. Rights

Rights are set per part at three levels: read, write (change in draft) and delete (discard a draft). You can set them for these parts: data, theme, assets, guide, live (publish and take back), actors, plan, journal and inbox (form submissions).

  • You never hand out more rights than you hold yourself.
  • Give read generously, write according to the role and preferably never delete by default.
  • An editor who writes texts but does not publish, for example, has data read and write and assets read. Only someone who may write live can publish.

6. Backups and journal

  • Backup. Your site is automatically saved to a private environment every fifteen minutes.
  • Restore. After a serious mistake an earlier version can be restored, back to the start of your site.
  • Journal. Every change is recorded: who, what and when.

7. Your own AI agent

You can also manage your site in plain language, with an AI agent that speaks MCP (such as Claude). The agent reads and writes your pages and data directly, works in drafts and leaves you to preview and publish. Use the key from chapter 2 for this. How to connect is explained under Documentation in the editor.

Sandbox

The free Sandbox is meant for learning and trying out and may not be used for commercial purposes. Under Check usage you can see how much space and how many items your plan allows. Want more? You can move to a paid plan later.

Questions or stuck? Email service@ctxr.app.