Settings

Connect a worker

This page talks directly to your worker URL — localhost, a Fly hostname, or a custom domain. Tokens land on that host (typically .env), not in Vercel env and not in git.

  1. 01

    Start a worker

    Run pnpm exec worker-bot run, pnpm start:worker, the desktop app, or the Fly example. Copy the one-time pairing code it prints.

  2. 02

    Allow this browser

    Remote workers need WORKER_BOT_CONTROL_HOST=0.0.0.0, HTTPS, and WORKER_BOT_CONTROL_ORIGINS set to this site origin.

  3. 03

    Pair this browser

    Paste the worker URL and pairing code. A durable control token stays in this browser's localStorage only.

  4. 04

    Push tokens

    Send Slack, LLM, GitHub, Linear, Vercel, Fly.io, Resend, SendGrid, Stripe, and sandbox fields to the worker. This site never stores those secrets.

Tomorrow's tokens

Paste Slack, LLM, GitHub, and sandbox tokens here after pairing. Use Check connection first if you want an unauthenticated GET /v1/control/health before you spend a pairing code. Prefix hints (xoxb-, sk-or-, ghp_) are warnings only — unknown valid formats still save.

FLY_API_TOKEN is a GitHub Actions secret for CI Fly deploys (repository Settings → Secrets and variables → Actions). It is not a field on this page. Do not paste a Fly deploy token into Slack, LLM, GitHub, or sandbox boxes.

Pair this browser

Step 3 of pairing. The worker URL is not this Vercel site. Secrets never leave the worker host after you push them.

Pair first. Push stays disabled until this browser holds a control token.

PersonaMissing

Coder is the only runnable persona. Coming soon roles stay visible and cannot be selected.

SlackBot token · MissingApp token · Missing
LLMAPI key · Missing
GitHubToken · Missing
LinearAPI key · Missing
Indie stackVercel · MissingFly.io · MissingResend · MissingSendGrid · MissingStripe · Missing

Connected accounts become shared context for every assistant. Deploys, campaign sends, and charges still wait for Approve.

SandboxToken · MissingTeam · MissingProject · Missing

Notifications & credits

Notifications go out through Novu (EU region). Your first 3,000 notifications are included. After that each enabled notification uses 0.1 StellarFirm credits.

Each enabled notification uses 0.1 StellarFirm credits once your 3,000 included notifications are used. Lifetime software pricing is separate and not set here.

Pair with a worker above to turn notifications on and see your balance.