claudnode

CLI bridge for Claudnode — connects your local claude CLI to the Claudnode web canvas.

Install

npm i -g claudnode

Quick start

claudnode doctor              # verify environment
claudnode login               # sign in with Google (opens browser)
cd ~/projects/my-app
claudnode init                # register this directory
claudnode start               # connect and wait for jobs

Commands

• claudnode doctor — check Node, Claude Code CLI, and login state.
• claudnode login — opens a browser, signs in with Google, stores a refresh token at ~/.claudnode/config.json.
• claudnode logout — remove stored credentials.
• claudnode init — register the current directory as an allowed working directory. Run this in every project folder you want to automate.
• claudnode status — show login + registered directories.
• claudnode start — connect and wait for workflow runs. Only directories registered via init (or passed with --dir) are allowed to execute Claude Code.

How it works

1. The web app writes a command document to Firestore (runs/{runId}/commands/{cmdId}).
2. Your bridge, subscribed via collectionGroup("commands"), picks it up.
3. It spawns claude -p "<prompt>" in the directory you whitelisted.
4. stdout/stderr are batched and streamed back to runs/{runId}/logs.

The bridge never runs code outside --dir folders.

License

MIT