Comment

Comment by maorbril

I run Claude Code in two terminals - one in /backend, one in /frontend. They had no idea what the other was doing.

When my backend agent finished an API endpoint, I'd have to manually tell the frontend agent. Copy-paste the schema. Explain the types. Re-establish context. Every. Single. Time.

So I built Clauder. Run `clauder wrap` instead of `claude` and your instances discover each other automatically.

The killer feature: real-time messaging between agents. Backend finishes an endpoint, sends "GET /users ready, returns paginated JSON" - frontend agent gets notified instantly and starts building the React Query hook. No copy-paste. They just coordinate.

How it works: - MCP server that runs locally - Agents auto-register when they start - Messages delivered in real-time via polling - Also has persistent memory (facts survive across sessions)

Quick start:

  curl -sSL https://raw.githubusercontent.com/MaorBril/clauder/main/install.sh | sh
  clauder setup
  clauder wrap  # instead of 'claude'
Works with Claude Code, Cursor, Windsurf, Codex CLI, Gemini CLI.

All local, SQLite storage, MIT licensed.

What multi-agent workflows would you use this for?

parent maorbril 9 months ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton