robodev

DocsSign in

Guides

Local development

Work on a Robodev project on your machine. Schema and APIs stay on the hosted project; Space / Auth chat / Marketplace UI runs locally with bun.

Getting startedConnect a frontendStartersDatabaseDomainsFile-based APIsAuthEmailOrganizationsStorageSecretsPushSchedulesJobsDeployLocal developmentCLI reference

After npm i -g robodev (or npx), robodev auth and robodev create talk to hosted Robodev by default. Local work is the project folder. Do not run a control plane.

After create

terminal

robodev auth
robodev create my-app
  • auth opens hosted Robodev and stores tokens in ~/.robodev/credentials.json.
  • create makes a hosted project, copies an official starter, writes .robodev and .env (VITE_API_URL, VITE_PUBLIC_API_URL), deploys schema + APIs to https://{projectId}.robodev.povio.dev, and runs npm install at the project root.
  • Dashboard Create and deploy is the same hosted project; CLI create also copies the local tree (including apps/fe for Space / Auth chat / Marketplace).
  • Do not set control-plane URL overrides. Defaults are production.

Folder layout

  • .robodev — project id and API URLs.
  • .env — Vite API URLs written by create / link.
  • database.ts, api/, and optional jobs/ at the project root.
  • Space, Auth chat, and Marketplace add apps/fe (local SPA, not uploaded).

Local UI (Space, Auth chat, and Marketplace)

The project host is API-only. The printed App URL is APIs and Swagger (/_robodev/docs), not the SPA.

terminal

cd apps/fe
bun install
bun openapi:gen
bun dev
  • bun is required.
  • Vite default is http://localhost:3000.
  • The CLI already prints these steps.
  • create / link write env so the SPA talks to the hosted project API.

Schema and APIs

Edit database.ts, api/**, or jobs/** at the project root, then robodev deploy from the root (or dashboard Code + Save). Destructive schema changes need confirmation or --force.

terminal

robodev deploy

Deploy uploads the allowlist (database.ts, api/**/*.ts, jobs/**/*.ts, and root frontend index.html + src/** when present). It does not upload apps/fe. It does not run Vite or npm run build. See Deploy (/docs/deploy) for force, hosts, and wait-until-live.

terminal

robodev link [projectId]

Writes .robodev and Vite API env for a folder that already has the tree (including after you clone your own app repo). Omit the id to pick from a list.

Backend and Empty

No local Vite. Edit files and robodev deploy from a real terminal. Paste VITE_API_URL into Lovable, Bolt, or v0. Do not run npm run dev or npm run build in those folders. See Connect a frontend (/docs/frontend).

Hosted React at the project root

If index.html + src/ sit at the project root (not apps/fe), deploy uploads that UI and the project host serves it. That is not Space / Auth chat / Marketplace.

Local vs hosted

  • Hosted: control plane https://robodev.povio.dev; project APIs, Swagger, and storage on https://{projectId}.robodev.povio.dev.
  • Local (Space / Auth chat / Marketplace): bun Vite SPA on http://localhost:3000.
  • Local (all starters): files on disk; robodev deploy (or Code + Save) updates the hosted project.
  • Not local: running Starbase, docker compose for the control plane, or pointing the CLI at localhost control-plane ports.

Next

Getting started (/docs), Starters (/docs/starter), Deploy (/docs/deploy), Connect a frontend (/docs/frontend).

bun is required for apps/fe. The project App URL is not the SPA.