Docs

How xTerminal holds the state of a custom site: who can change what, how Requests ship, and where agents work.

Popular

Basics

What xTerminal is

A control panel for a custom-built website. State, custody, and ops. Not an AI website builder.

Quick start

Create an account, verify email, then billing. Managed signup is operator-gated today.

Your first site

The dashboard is ready after billing. A developer connects the custom site. You run it from there.

Managed vs other paths

Foundation, Advanced, and Managed. Requests are a Managed capability. Prices on marketing cards are not a locked billing contract.

Roles and permissions

Owner, admin, and developer are people on the site. Workers and agents act through a key the developer mints.

The Request loop

Compose, worker, review, then Ship to live. A person stays in the loop.

Request a change vs Edit

Edit is for content already on the page. Request a change is for everything else, when Requests is on.

Delivery note / proof

The review card is the proof: headline, how to check, and what changed. Preview sits next to it.

Control panel vs developer lane

Owners run the site from the dashboard. Developers hold the repo. The client never sees GitHub.

Domains, hosting, custody

The developer lane holds the host and the domain registrar. The dashboard holds who may change the site.

What belongs in the platform

A feature belongs here if it is state, permission, or a change log. Everything else stays in the developer lane.

Agents as employees

Treat a worker like a named employee: a lane, supervision first, no brand mascot in the UI.

Agent on your site

One worker per client site for ops. Keys do not stretch across sites.

What agents may / may not do

Workers act on Requests for one site. They cannot skip review or ship without promote.