Show HN: Clauder – Make your Claude Code instances talk to each other(github.com)

8 pointsby maorbril10 hours ago4 comments

smittyplusplus7 hours ago
Neat, I tried this out. Initial thoughts: it was dead simple to setup, and it seems super useful so far. It's sort of a new way of thinking about agentic coding flow (for me at least) and its fun to "discover" capabilities it unlocks. It's pretty cool to see the agents occasionally work together without direct input.
Good work.
- maorbril7 hours ago
  thank you.
  glad you enjoy it.
ShayNehmad9 hours ago
Cool stuff. Multi agent orch seems cool but isn't running the agent at the top of a monorepo a good solve?
- maorbril9 hours ago
  a. not everyone is using a monorepo :) b. It's I think the difference between 2 SME vs a Fullstack engineer.
  personally - and maybe I'm biased, I prefer the expert approach.
  - maorbril8 hours ago
    To add to this - even in a monorepo, a single agent hitting a 200k+ line codebase gets slow and loses focus.
    The multi-agent approach lets you scope each agent to what it knows best. Backend agent stays in /api, knows the DB schema cold. Frontend agent lives in /web, knows the component library.
    When they need to coordinate, they message each other with just the relevant context - not the entire codebase.
    It's also useful for parallel work. Both agents can be coding simultaneously instead of one waiting for the other.
johnaithings7 hours ago
This seems to be a great idea that solves some of my issues at work!
- maorbril7 hours ago
  great to hear. let me know your thoughts after using it a while. are there any additional features you have in mind.
maorbril10 hours ago
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?