Flarebot #

A persistent personal agent in your own Cloudflare account. The v0.1 client uses OctaneJS and the Octane port of Kumo. The runtime uses Cloudflare Agents, Think, Workers AI, durable storage, browser tools and scheduled execution.

Development #

Use Node 24 (see .node-version) and the pnpm version in package.json.

pnpm install --frozen-lockfile
pnpm dev

Vite serves the frontend and Octane server routes with hot reload. To run the production frontend and Worker together in the local Cloudflare runtime:

cp .dev.vars.example .dev.vars
pnpm dev:worker

Wrangler serves the application at http://localhost:8787. Rebuild after source changes. Local Worker state is stored in .wrangler/. Open /auth/login once to create the development owner session; this shortcut is restricted to an explicit development environment on a loopback runtime origin.

Kumo is installed from a pinned commit of the separate octane-kumo repository. A sibling checkout is not required. Work on that port belongs in its repository. The published sidebar currently requires browser APIs, so the shell uses TanStack Router's ClientOnly boundary with server-rendered navigation and page content until hydration.

Validation #

pnpm typecheck
pnpm test:config
pnpm build:release
pnpm test:worker
pnpm test:deployment
pnpm test:settings
pnpm test:app-shell

The Worker smoke test checks rendered navigation, client assets and HTTP 404s using the local Cloudflare runtime. CI runs these checks for every pull request, including PRs based on another issue branch. Deployment is a separate, explicit pnpm deploy command.

The Worker requires typed installation settings and an independent session secret. See configuration and secrets for production setup, local overrides and the customer/control-plane boundary. .dev.vars and its environment variants are ignored; only the placeholder example is committed. Vite alone is a frontend preview and does not validate Worker bindings. Never put secrets in client source, Vite environment variables or wrangler.jsonc.

The customer deployment contract documents required resources, stable identities, account boundaries and the versioned dist/release artifact.

The v0.1 golden-path gate connects native installation, owner login, memory, research, shell execution and unattended scheduled work.

See the application shell for navigation, authenticated connection behavior, and the boundary between shell metadata and native conversations.