Quickstart

Before you start

• A machine that stays on while the agent works — a laptop, a workstation, or a VPS.
• Docker — installed automatically if missing (you're asked first). See Docker setup.
• A Google account to sign in. No card, no repo permissions, no code upload.

1 · Sign in

Open app.intentic.dev and sign in with Google. The platform stores your identity and, in a moment, your sandbox's URL — nothing else. It never sees your code or your keys.

2 · Name your sandbox

Give the sandbox a name and intentic prepares a private tunnel for it under its own domain — no Cloudflare account required. Prefer your own zone? Paste a Cloudflare token; it's used once to list your zones and is never stored.

3 · Run the one-liner

Setup shows a personalized command with your connect code. Run it on the machine that should host the sandbox — the connect code binds that machine to your account on first use.

curl -fsSL https://intentic.dev/connect | sh -s -- <CONNECT_CODE>

# Windows (PowerShell) — Setup shows your exact one-liner
irm https://intentic.dev/connect.ps1 | iex

Docker is installed if it's missing, after it asks. To skip the prompt in an unattended setup, set INSTALL_DOCKER=1 in the environment before running the command.

What happens next

The one-liner starts two containers on your machine and nothing else:

• the sandbox — the daemon, your agent, and your workspace;
• a cloudflared sidecar that dials out to establish the private tunnel.

Both are outbound-only — no port is opened on your machine. Your browser probes the sandbox directly until it reports healthy, then the workspace opens on its own. From here you're talking to the daemon over its tunnel; the platform is out of the loop.

Managing sandboxes

On Pro you can run several sandboxes at once — one per agent — and they coexist on the same machine without stepping on each other. The Docker setup page covers updating, rebuilding, and removing them with the /update, /rebuild, and /cleanup helpers.