qaml-ai/camelAI

camelAI — an AI coding assistant platform built on Cloudflare Workers and Durable Objects

camelAI – Persistent AI‑powered coding workspaces

What it is – camelAI is a full‑stack web platform that lets a team chat with an AI coding assistant. Each chat thread runs its own “coding agent” inside a Cloudflare Durable Object, giving the assistant a persistent workspace (files, history, secrets) that survives across sessions.

Key capabilities

  • Persistent chat & project files – conversations and source files are stored in a Durable‑Object‑backed SQLite database (small files) and Cloudflare R2 (large files).
  • Workspace‑aware coding agent – the agent can read/write the project’s files, run JavaScript tools, and execute code in short‑lived V8 isolates or sandbox containers.
  • Integrations – built‑in connectors for APIs, databases, email, Slack, Discord, etc., which the agent can call from the chat.
  • Build & deploy – projects can be built in a Docker‑backed sandbox and published as Cloudflare Workers for Platforms, with a dispatcher worker routing live traffic.
  • Admin features – org‑level authentication, billing, usage quotas, and app‑cost‑control policies.

How it works

  1. Front‑end – a React‑Router SPA rendered with SSR, served by a Cloudflare Worker.
  2. Main Worker – hosts the ChatThreadDO Durable Object that runs the agent loop (built on the pi agent framework).
  3. Workspace DO – stores the project’s filesystem (SQLite + R2).
  4. Sandbox workers – V8 isolates for “Code Mode” and separate Cloudflare sandbox containers for builds, notebook analysis, and SQL queries.
  5. Dispatcher – routes requests to user‑published apps once they’re deployed.

Getting started

  • Requires Node 22+, Bun, a Cloudflare account, and Docker (for sandbox features).
  • Clone, install with bun install, copy the example secrets file, add your Cloudflare AI Gateway token (or configure Anthropic/OpenAI/etc. later), then run bun run dev:local-auth for a quick local dev user or bun run dev for the full OAuth flow.

Self‑hosting

  • A single‑machine Docker‑Compose setup can run the whole stack privately (web UI, auth, model providers, Durable Objects, builds, notebooks, SQL, etc.).
  • Email verification is deliberately omitted; the target is internal or evaluation use.

Who it’s for

  • Development teams that want an AI‑assisted coding environment with persistent state and the ability to ship the generated code as serverless apps without leaving the platform.

License – MIT.


All details are taken directly from the repository’s README.

Related

  • Project
  • Project
  • Project
  • Project
  • Dispatch