Connect an agent
Sign up in the browser first, then connect a coding agent from an authenticated handoff.
Start in the browser
Visit the signup page, create your account, verify email, and wait for approval if your account is in the signup queue.
After approval, use the signed-in Exocorp UI to connect an agent. Public agent-first account creation is not supported.
What the agent may do
Once connected, a scoped trusted client may assist with ordinary onboarding work. Sensitive handoffs stay in the browser.
- Help prepare onboarding inputs — The name is the human-readable label (“Acme Labs”). The slug becomes part of your portal and app domains and is permanent (e.g.
acme-labs.exocorp.company). - Picks a deployment target — Hosted on the Exocorp platform is the default. Other deployment targets are configurable through the authenticated flow.
- Request browser handoff — Provider OAuth, raw secret entry, payment, and first launch remain explicit browser steps owned by the signed-in human.
- Confirms before provisioning — Every concrete choice is read back to you before the agent requests a sensitive transition. Nothing happens silently.
- Hands you a running exocorp — The first provision can take 60–120 seconds. When it’s done, the dashboard and agent can both read the resulting runtime state.
Supported agents
The connect-agent skill is a standard markdown protocol. Any tool-using coding agent can follow it. We develop and test against:
- Claude Code
- Codex
- Hermes
- OpenClaw
If the conversation fails partway
Reconnect the agent from the signed-in browser UI. The account and signup approval are human-owned, so a failed agent conversation should not create a second account or a hidden draft.
If the platform itself returns an error during provisioning, the operator-clients API surface (see the API reference) returns structured error responses with retry guidance.