For developers and agencies
The control panel you'd otherwise build for every client.
Connect a Next.js site with three environment variables. Your client gets a dashboard. You get agents that follow the rules already in your repo.
How it connects
You
Update content, answer leads, ask for changes. Never touch code.
Your developer
Builds the site their way. Reviews what goes live.
xTerminal
Handles the everyday work and sends the rest to your developer.
Two ways to start
Connect a site you built
Any Next.js site. Add three environment variables, run the setup wizard, invite your client.
- Shared API base URL, server-to-server contact endpoint, and a per-site slug
- Contact forms proxy server-side; no database keys in the client deploy
- Your repo, your GitHub org, your Vercel project, or your client's
- Add a README and design rules if the repo doesn't have them; the agents read those first
Start from the template
A Next.js starter with blocks, admin wiring, and the rules files already in place.
- The block registry is the contract: the admin generates edit forms from your field definitions
- Restyle any block freely; the admin never imports your components
- Pages come from site.config.ts; the admin sidebar follows it automatically
- README, CLAUDE.md, and design rules ship with the template
AI agents that follow your rules
Knows your rules. Carries them forward. You review the pull request.
Works with ChatGPT, Claude, and Grok.
Knows your rules
README, CLAUDE.md, design rules. If you built on the template, these are already there. If not, add them once.
Carries them forward
Copy, images, sections, pages, layout, CSS, site.config.ts. Never dependencies, environment, secrets, or API routes.
Protects the repo
In your repo, on a branch, one attempt per request. You review and merge. Nothing reaches production without you.
Comes to you for the rest
Handle it, add the rule, and the next one doesn't need you.
The review is the product. Other tools hand your client the steering wheel. xTerminal keeps a developer between the client and the code, and makes the job easier with AI agent native connections.
What stays yours
Design authority.
Agents don't make design decisions; they apply yours.
The repo, the hosting, the domain.
Built in your client's accounts or yours. You decide.
The relationship.
Your client can still call you. Requests are a paved road, not a gate.
The choice.
Connect one site or all of them. It's still your Next.js site either way.
Your review
Merged
The client's thread flips to Live. They never saw the repo.