Run your flows
from Claude.

Connect Claude to Lithnode. It builds a team of agents, runs it on your folder and reads back the result, while you watch every step live.

Connect Claude See it work
01

Get Lithnode

Lithnode runs your agent teams on your own computer, on the Claude, Codex, Cursor or Antigravity plan you already have, local models with Ollama, or your own API key. Connecting Claude needs version 0.1.30 or newer. If you have an older one, the app updates in one click.

Download Lithnode
02

Connect Claude

Pick where you use Claude. Lithnode has to be open while Claude works, because every run happens there.

Claude Code one click

Lithnode adds itself to Claude Code for every project. That covers the terminal and the Claude desktop app's Code tab.

  1. In Lithnode, open Settings (the cog, or Ctrl+,).
  2. Under Connect Claude, click Add to Claude Code.
  3. Start a new Claude Code session. Type /mcp to see lithnode connected.
03

Ask for a team

Say it the way you'd brief a person. Claude picks or builds a flow, runs it in your folder and checks on it until it's done. Tap one to copy it.

04

Watch it run

Claude calls Lithnode's tools. Lithnode runs the agents. Steps that need your sign-off still wait for you in the app.

Review this repo with Lithnode and fix anything serious.
Found your flowsQuick code review: 3 reviewers, 1 summary
list_flows
Started the runin ~/my-app, on your Claude plan
run_flow
Reviewers working3 agents reading, 41k tokens so far
get_run
Read the final report2 bugs, 1 security note
get_run

Done. The reviewers found an off-by-one in parse.py and an unchecked input in the upload route. Want me to run your Build and deploy flow to fix both?

05

What Claude can do

Nine tools, all on your computer. Nothing goes through lithnode.com.

lithnode_status

Is Lithnode open, and which engines are signed in.

list_flows

Your flows and the templates to start from.

get_flow

A flow's steps in order, with each team's engine and model.

create_flow

A new flow from a description or a template.

run_flow

Start a flow on a task, in a folder.

get_run

Each step's state, files changed and the final report.

list_runs

Recent runs, newest first.

decide

Answer an approval step, when you say so.

stop_run

Stop a run. Finished work is kept.

Claude asks before it uses a tool unless you've allowed it. Runs use your own plans and keys, so they count toward your usage like any run you start in Lithnode.