Run nobuu on your own machine

The workspace you run locally is the same product that serves app.nobuu.io. There is no separate local interface.

Start it

Use Node 22 and run these from the repository root:

npm ci --prefix app
npm ci --prefix app/server
npm run dev --prefix app

Open http://127.0.0.1:55378/. The private API listens on port 55379. Both bind to loopback only. The launcher refuses ports that are already taken, and Ctrl-C stops everything it started.

Where your work is saved

Local work lives in ~/.nobuu/local-product/state, outside the checkout. Deleting or re-cloning the source does not touch it, and production data is kept separately. Do not delete this folder when you clean up source files.

Use the model sign-ins you already have

Set NOBUU_CLAUDE_PATH and NOBUU_CODEX_PATH to the absolute paths of your signed-in command-line tools before you start. Their credentials stay where those tools keep them. NOBUU_OWNER_EMAIL labels the local owner. This is a local identity, not a production login, and nothing syncs to production.

Code in a repository

Add a clean Git repository with the repository picker. A coding request runs in an isolated copy using the Claude or Codex login you picked. You review the resulting patch, then apply it to the repository. A repository with uncommitted changes has to be cleaned up first.

Run a second copy

NOBUU_PRODUCT_UI_PORT=5178 NOBUU_PRODUCT_API_PORT=5179 \
NOBUU_PRODUCT_STATE_ROOT=/absolute/path/to/private-state npm run dev --prefix app

Custom ports need their own state folder. A second copy does not import production state or gain hosted permissions.