<img src="documentation/images/logo-icon.svg" width="28" align="absmiddle" alt="Codeflare logo"> Codeflare

An ephemeral IDE where AI coding agents reach their full potential. Fully autonomous, no boundaries, zero risk. Every session runs in an isolated container on Cloudflare's edge. Your files persist. Your bad decisions don't.

It runs wherever you happen to find yourself - on the Cloudflare edge that spans the planet, accessible from anything with a browser. Your phone, your tablet, your partner's laptop while they're not looking. Because the best commits in history were made from places without desks.

Ideas don't care where you are. Any screen with a browser, zero setup. No installs, no configuration, no asking for permission. Open the link and start building.

Every session comes pre-loaded with your choice of AI coding agent:

| Agent | Description | |---|---| | Claude Code | Anthropic's agentic CLI (uses claude-unleashed behind the scenes for root permission bypass and controlled updates) | | Codex | OpenAI's coding agent | | Gemini CLI | Google's terminal agent | | GitHub Copilot | GitHub's AI coding agent | | OpenCode | Open-source coding agent | | Bash | For the purists |

Pro mode features (knowledge graph, curated skills, advanced workflows) are primarily designed for Claude Code. Other agents receive rules and agent definitions but may not support all Pro capabilities.

<details> <summary><strong>Why Claude Unleashed under the hood?</strong></summary> <a id="why-claude-unleashed"></a>

Cloudflare Containers run as root. Claude Code refuses to run with --dangerously-skip-permissions as root - even inside an ephemeral container where the root check is protecting a filesystem that won't exist in 30 seconds. Heroic. Claude Unleashed is a wrapper that politely disagrees with this decision, patching around the restriction at source level. Handles root detection, auto-updates, and mode switching. Pre-installed in every Codeflare container because arguing with your tools is not a productive use of compute. In the UI, it shows up as "Claude Code" - because that's what it is, just without the unnecessary guardrails.

</details>

Codeflare is an ephemeral cloud IDE that runs entirely in your browser. Every session spins up an isolated container on Cloudflare, pre-loads your AI agent of choice, and tears itself down when you're done. Your files persist in R2 storage. The containers don't. Nothing touches your local machine.

Swipe up/down with the keyboard open to navigate like arrow keys. Swipe left/right to scroll terminal text horizontally.

It's strongly optimized for mobile - because the best ideas hit while rewatching your favorite show for the 15th time, and your PC is just too far away.

Try it: codeflare.ch

From idea to live in minutes

Codeflare is built for Cloudflare. Not adapted, not ported - built on it, for it.

• Native GitHub integration - connect your GitHub account once. Every session gets automatic git push, gh CLI, and CI/CD access. No SSH keys, no token juggling, no manual auth per session.
• Native Cloudflare integration - connect your Cloudflare account once. Deploy Workers, manage D1 databases, R2 storage, KV namespaces, and DNS - all from the terminal, already authenticated.
• Specialized skills for build, push, and deploy - pre-loaded agent skills know how to create Cloudflare Workers projects, configure wrangler.toml, push to GitHub, set up CI workflows, and deploy to production. Tell the agent what you want. It builds, pushes, and deploys.
• Guided onboarding - new users get walked through connecting GitHub, Cloudflare, and choosing a coding agent. No prior Cloudflare knowledge required.

Connect your accounts and pick a coding agent. No prior Cloudflare or GitHub knowledge required.

• Go from idea to live on Cloudflare in minutes - describe what you want, the agent builds it, pushes to GitHub, deploys to Cloudflare Workers. You get a live URL. The whole loop happens in one terminal session on your phone or anywhere else.

What you get

Manage sessions, browse persistent storage, and monitor live resource usage - all from one view.

• Browser-native terminal with 6 tabs per session and tiling mode - view 2-4 terminals side by side. Once you tile, you don't go back.
• One isolated container per session - agents can't escape their sandbox (I checked)
• Persistent R2 storage with bisync every 60s - even if a session dies before you git push, R2 has got your back. Sync conflicts? Cleaned up automatically next cycle.
• Pre-warmed terminals - the agent is already loaded when you open the tab, not staring at a blank screen wondering if something broke
• Fast Start - auto-updates disabled by default across all 6 tools for instant agent startup. Toggle it in Settings if you prefer bleeding edge over fast boot.
• Set your API key once. It syncs across sessions forever. (It's rclone, but magic sounds better.)
• Push & Deploy - connect your GitHub and Cloudflare accounts once in Settings. Every session gets automatic auth. No more pasting tokens into terminals like it's 2019.
• Dashboard for managing sessions, browsing files, and inviting users (or revoking them when they get too creative). Live CPU/memory/disk metrics per session. Three-color status: green (active), yellow (idle but alive), gray (stopped).
• Usage dashboard - track daily and monthly compute hours, see quota remaining, per-user Timekeeper Durable Object accumulates seconds and flushes to KV every 5 minutes.
• Configurable auto-sleep - containers stop after a period of inactivity (no terminal input). Choose 5m, 15m, 30m, 1h, or 2h in Settings. Free tier is locked to 5m. Sleep is input-aware: the timer only resets when you actually type something, not on WebSocket reconnects or background polls.
• CPU cost scales to zero when idle. You pay for what you use. Nothing when you don't.

Architecture

Six terminal tabs, split tiling, and your favorite dev tools - running in a disposable container you didn't have to configure.

flowchart LR
    A[Browser] --> B["Cloudflare Worker
    Hono router + SolidJS static UI"]
    B --> C["Container DO
    session lifecycle + hibernation"]
    C --> D["Cloudflare Container
    isolated per session, pre-warmed PTY"]
    D --> E["R2
    per-user storage, bisync every 60s"]
    C -. "ping every 60s" .-> G["Timekeeper DO
    per-user usage + quota"]
    G --> H["KV
    usage records, flush every 5m"]
    D -. "idle after sleepAfter
    (no terminal input)" .-> F["Hibernated
    zero cost"]

Containers scale to zero when idle (no sessions = no bill). Storage persists. A per-user Timekeeper Durable Object tracks compute usage and enforces monthly quotas. Auth is handled by Cloudflare Access or GitHub OIDC (SaaS mode) — one-click login, automatic user provisioning, and admin approval workflow.

Setup

Four steps. Shorter than most cookie consent forms.

1. Fork this repo

You know how.

2. Set secrets

In your fork: Settings > Secrets and variables > Actions > New repository secret

Secrets (required):

• CLOUDFLARE_API_TOKEN - see token scopes below
• CLOUDFLARE_ACCOUNT_ID - find it on any zone's overview page in the Cloudflare dashboard

Add each as a separate secret. Name goes in the Name field, value in Secret. Click Add secret after each one.

3. Deploy

Go to your fork: Actions > Deploy > Run workflow > Branch: main > Run workflow. GitHub Actions builds, tests, and deploys to Cloudflare Workers. Takes about 2 minutes - go grab a coffee.

Future deploys are automatic on every push to main.

4. Run the setup wizard

Find your worker URL: dash.cloudflare.com > Compute > Workers & Pages > your worker name (default: codeflare). If you didn't set CLOUDFLARE_WORKER_NAME, your URL is codeflare.<your-user>.workers.dev. Open it - the onboarding wizard takes over and walks you through:

• Verifying your token and account access
• Configuring a custom domain and allowed users
• Setting up authentication (Cloudflare Access for all modes; SaaS mode can use GitHub OAuth instead)

That's it. You're live. No Kubernetes. No Terraform. No existential crisis. You'll need an active subscription to at least one of the supported coding agents - log in directly from the terminal.

<details> <summary><strong>API token scopes</strong></summary> <a id="api-token-scopes"></a>

Go to dash.cloudflare.com/profile/api-tokens and create a custom token. Yes, it's a lot of scopes. No, I'm not mining crypto with them (or am I?).

Required

The minimum permissions for Codeflare to deploy and run. Every scope earns its keep:

| Scope | Permission | Access | Why | |---|---|---|---| | Account | Account Settings | Read | Setup wizard reads account metadata | | Account | Workers Scripts | Edit | Deploys the Worker | | Account | Workers KV Storage | Edit | Session metadata and configuration | | Account | Workers R2 Storage | Edit | Per-user persistent file storage | | Account | Containers | Edit | Manages ephemeral session containers | | Account | Access: Apps and Policies | Edit | Creates the Acces