RegionClaw

Run the app locally with:

npx regionclaw

Optional flags:

npx regionclaw --dev
npx regionclaw --port 3000
npx regionclaw --host 127.0.0.1 --port 3000
regionclaw start
regionclaw restart
regionclaw --foreground
regionclaw status
regionclaw stop
regionclaw update
regionclaw update status

npx regionclaw automatically:

• creates ~/.regionclaw/regionclaw.json on first run
• generates and stores a NEXTAUTH_SECRET there if you did not provide one
• uses ~/.regionclaw/auth.db as the default local auth database

You do not need to run prisma generate at runtime in production. The published npm package should already include the generated Prisma client and the packaged Next.js production build.

For local development inside the repo, use:

pnpm regionclaw:dev
pnpm regionclaw:prod

pnpm regionclaw:dev starts Next.js in development mode through the RegionClaw CLI. pnpm regionclaw:prod automatically runs pnpm build first, then starts the production server.

To prepare and publish the npm package:

pnpm install
npm login
npm publish

npm publish runs prepack, which generates Prisma client code, builds the Next.js app, and copies the production build into dist/ui for the npm tarball.

If you want a single command that bumps the version and publishes:

pnpm release:patch
pnpm release:minor
pnpm release:major
pnpm release:dry-run

For installed copies, RegionClaw can also check for npm updates:

regionclaw update status
regionclaw update

If you are running via npx, use:

npx --yes regionclaw@latest

By default RegionClaw stores local state in:

• ~/.regionclaw/regionclaw.json
• ~/.regionclaw/auth.db

When RegionClaw is installed globally with npm install -g regionclaw, running regionclaw starts the production server in the background by default. Useful related commands:

• regionclaw start
• regionclaw restart
• regionclaw status
• regionclaw stop
• regionclaw --foreground

The background runtime metadata and log file live in:

• ~/.regionclaw/runtime.json
• ~/.regionclaw/regionclaw.log