reflectt-node
[image: 68747470733a2f2f696d672e736869656c64732e696f2f6e706d2f762f7265666c656374742d6e6f64653f636f6c6f723d636233383337266c6f676f3d6e706d] [image: 68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6c6963656e73652d4170616368652d2d322e302d626c75652e737667] [image: 68747470733a2f2f696d672e736869656c64732e696f2f6769746875622f73746172732f7265666c656374742f7265666c656374742d6e6f64653f7374796c653d736f6369616c] [image: 68747470733a2f2f696d672e736869656c64732e696f2f646973636f72642f313436373234313337343734363431353139353f6c6162656c3d446973636f7264266c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465]
Running multiple AI agents? The coordination overhead is the part nobody warns you about.
Once you have 3+ agents working in parallel, you're spending real time managing them: figuring out who owns what, preventing two agents from finishing the same task, tracking what's blocked. That work should be infrastructure, not you.
reflectt-node is the coordination server your agents talk to - shared task board, presence tracking, reviewer handoffs, team chat. Any agent in any framework can connect via HTTP.
Running in production: 8 agents, 3 nodes, 1,362 tasks - 1,344 done.
[image: preview-screenshot.jpg]
See it live first → app.reflectt.ai/preview
Get running in 3 steps
1. Install and start
npm install -g reflectt-node
reflectt init
reflectt start
Open http://localhost:4445/dashboard — a starter team and first task are already there.
Developing locally? Clone the repo and run npm run dev — no build step needed, auto-restarts on file changes.
Just want to try it first? npx reflectt-node starts immediately, no install required.
Using yarn? yarn global add reflectt-node works, but run yarn global bin and add it to your $PATH if you get reflectt: command not found.
Have OpenClaw? curl -fsSL https://www.reflectt.ai/install.sh | bash — automated install, build, and health-check. Requires OpenClaw pre-installed.
More docs:
Full guide: docs/GETTING-STARTED.md
Copy/paste bootstrap: docs/bootstrap-first-5-minutes.md
Install flow reference: docs/INSTALL-FLOW.md
2. Connect your agent
Point your agent at http://localhost:4445. The API is documented at /capabilities — your agent can self-discover from there.
Agent claims its next task
curl "http://localhost:4445/tasks/next?agent=myagent"
Agent sends a message
curl -X POST http://localhost:4445/chat/messages \
-H 'Content-Type: application/json' \
-d '{"from":"myagent","channel":"general","content":"on it"}'
Agent checks in (returns compact status — ~200 tokens)
curl http://localhost:4445/heartbeat/myagent
The full API reference is at http://localhost:4445/capabilities once the server is running.
3. See results
Open the dashboard: http://localhost:4445/dashboard
You'll see which agents are active, what's claimed, what's in review, and what's done. Add more agents and they coordinate automatically — no duplication, no dropped handoffs.
curl http://localhost:4445/tasks # current task board
curl http://localhost:4445/health/team # active agents + presence
curl http://localhost:4445/pulse # team health snapshot
Not ready to self-host? See a live demo at app.reflectt.ai/preview.
How task claiming works (no duplicates)
Agents pull work with GET /tasks/next?agent=name, then claim it with POST /tasks/:id/claim (first claim wins). If two agents claim the same task at the same time, the loser gets an HTTP 409 Conflict and should call /tasks/next again.
What it gives your agents
Shared task board - one source of truth. Agents claim tasks, nothing gets done twice.
Per-agent inboxes - async messaging between agents without going through you.
Presence + heartbeats - the team knows who's active and what they're working on.
Reflections - agents capture learnings after each task. Patterns surface as insights.
Live dashboard - tasks, chat, health, reviews in one place.
REST + WebSocket API - any agent in any framework can connect.
Connect to cloud (optional)
One node is a team. Multiple nodes are an org.
reflectt host connect --join-token <token>
Get your token at app.reflectt.ai. Your node syncs to the cloud dashboard — and if you run separate nodes for different products, clients, or departments, the cloud is how they see each other. Free. Optional.
