CClaudnodebeta

Docs

Build node-based automations. Claude Code runs on your machine, so there are no server costs and your credentials never leave your laptop.

1. Install the bridge

The claudnode CLI is a small Node.js program that listens for jobs from the web UI and runs Claude Code in a directory you authorize.

$ npm install -g claudnode

Requires Node.js 20+ and a working claude CLI (Claude Code) in your PATH.

2. Sign in

Authenticate the bridge with the same Google account you use on the website. A browser window opens for login and then closes by itself.

$ claudnode login

3. Register a project directory

From any project folder you want automations to run in:

$ cd C:\path\to\your-project
$ claudnode init

You can repeat this in as many folders as you like. The bridge will only touch directories you have explicitly registered.

4. Start the bridge

$ claudnode start

Keep the terminal open while you work. The bridge polls for new jobs every 2 seconds and sends heartbeats so the web UI knows it is online. Scheduled workflows are tracked in the same loop — each one prints once when first seen and again only after it runs.

5. Build a workflow

  1. Open Dashboard → New workflow.
  2. In the header, pick the working directory (cwd). Only registered dirs appear in the dropdown.
  3. Right-click the canvas to add nodes. Connect them by dragging from a handle to another node.
  4. Click Save to persist, then Run ▶ to execute.

Node types

Start

The manual starting point of a workflow. Clicking Run begins here.

Schedule Trigger

Runs the workflow automatically on a schedule. Two modes:

  • Every… — fires every N minutes/hours (5min to 24h).
  • Daily at… — fires once per day at HH:MM.

Scheduling only runs while the bridge is active on your machine. The schedule starts when you click Save.

Claude Task

Runs a Claude Code prompt as an independent job. At the end, Claude answers YES or NO to its own prompt; the output branches to the YES or NO handle accordingly.

Continue

Like Claude Task, but the previous node's output is automatically prepended as context. Use this when you want Claude to build on prior work instead of starting fresh.

YES / NO branching

Every Claude Task and Continue node has two output handles:

  • YES — taken when Claude finishes successfully and judges the task done.
  • NO — taken on failure or when Claude judges the task incomplete.

This means you can branch to retry, fallback, or escalate paths without a separate condition node — Claude Code judges itself.

Troubleshooting

Bridge shows offline in the header
The browser can't see a recent heartbeat. Make sure claudnode start is still running and that you logged in with the same Google account as the website.
Run fails with 'Working directory (cwd) is required'
Set cwd in the workflow header. It must be a directory you previously registered with claudnode init.
Schedule doesn't fire
The bridge must be running at the time the schedule is due. When a workflow is first picked up, the terminal prints schedule: ... — next in Ns. It only reprints when the next run time changes (i.e. after a run). If you see nothing, re-save the workflow so the bridge reloads it.
Google login popup blocked
Allow popups for the site, or sign in once on the Dashboard page before starting the bridge.
`claudnode login` opens http://localhost:3000
You have an old build. Upgrade to 0.1.2 or newer: npm install -g claudnode@latest. Versions before 0.1.2 defaulted to a local dev URL instead of claudnode.com.

Beta

Claudnode is in closed beta. Report issues or request access by emailing onevibe1234@gmail.com.