Your first ten minutes
The other guides go deep on each step. This page is the narrow path through all of them: deploy, log in, connect an agent, and give it something to do.
1. Deploy (about 3 minutes)
Section titled “1. Deploy (about 3 minutes)”Click Deploy to Cloudflare in the deploy repo: it clones into your account, auto-provisions D1, KV, and R2, and ships. Fill in your admin email on the setup page. Full detail, including the one-command and manual/CI paths, is in the self-hosting guide.
2. Front it with Cloudflare Access and log in (about 3 minutes)
Section titled “2. Front it with Cloudflare Access and log in (about 3 minutes)”The Worker is live but nobody can reach it yet - Cloudflare Access has to sit in
front before login works (a *.workers.dev toggle, or a custom domain). Turn that on,
then log in with any address in ADMIN_EMAILS: the first one to log in creates the
default workspace and becomes its owner automatically. Step-by-step:
CONFIGURE.md.
3. Connect an agent (about 2 minutes)
Section titled “3. Connect an agent (about 2 minutes)”In the UI, go to Settings → Tokens → New token, then paste the ready-to-run
claude mcp add command it shows you. That’s it - the agent now has the same access
a browser user has. Other agents, other connection modes (dev bootstrap, the Claude
app, CI): Connect an agent.
4. Give it something to do
Section titled “4. Give it something to do”Try one of these directly in your agent’s chat:
“Create an issue: ‘Set up CI’ with high priority.”
“Show me the highest-priority open issues in this project.”
“Write a wiki page describing this project, and link it from the homepage.”
If the agent can do all three, the connection is working end to end. From here:
- Understand why it’s built this way: Agentic workflows
- See every tool it has: MCP tool catalog
- Run a fleet of agents on one repo: Contributor conventions