Last updated: 2026-01-01
~/.coderclaw/workspace (workspace) + ~/.coderclaw/coderclaw.json (config).pnpm gateway:watch, then let the macOS app attach in Local mode.>=22pnpmIf you want “100% tailored to me” and easy updates, keep your customization in:
~/.coderclaw/coderclaw.json (JSON/JSON5-ish)~/.coderclaw/workspace (skills, prompts, memories; make it a private git repo)Bootstrap once:
coderclaw setup
From inside this repo, use the local CLI entry:
coderclaw setup
If you don’t have a global install yet, run it via pnpm coderclaw setup.
After pnpm build, you can run the packaged CLI directly:
node coderclaw.mjs gateway --port 18789 --verbose
coderclaw channels login
coderclaw health
If onboarding is not available in your build:
coderclaw setup, then coderclaw channels login, then start the Gateway manually (coderclaw gateway).Goal: work on the TypeScript Gateway, get hot reload, keep the macOS app UI attached.
If you also want the macOS app on the bleeding edge:
./scripts/restart-mac.sh
pnpm install
pnpm gateway:watch
gateway:watch runs the gateway in watch mode and reloads on TypeScript changes.
In CoderClaw.app:
coderclaw health
ws://127.0.0.1:18789; keep app + CLI on the same port.~/.coderclaw/credentials/~/.coderclaw/agents/<agentId>/sessions//tmp/coderclaw/Use this when debugging auth or deciding what to back up:
~/.coderclaw/credentials/whatsapp/<accountId>/creds.jsonchannels.telegram.tokenFilechannels.slack.*)~/.coderclaw/credentials/<channel>-allowFrom.json~/.coderclaw/agents/<agentId>/agent/auth-profiles.json~/.coderclaw/credentials/oauth.json
More detail: Security.~/.coderclaw/workspace and ~/.coderclaw/ as “your stuff”; don’t put personal prompts/config into the coderclaw repo.git pull + pnpm install (when lockfile changed) + keep using pnpm gateway:watch.Linux installs use a systemd user service. By default, systemd stops user services on logout/idle, which kills the Gateway. Onboarding attempts to enable lingering for you (may prompt for sudo). If it’s still off, run:
sudo loginctl enable-linger $USER
For always-on or multi-user servers, consider a system service instead of a user service (no lingering needed). See Gateway runbook for the systemd notes.