Dog
591 posts


@konnydev Hot take:
When you combine @Claude and @usepharaoh there’s no project too big to vibe code.
English

@RoundtableSpace Building @usepharaoh - I’ll be the first solo-dev founder to run a unicorn.
English

@sawyerhood Gonna use my Claude CLI to automate my Claude.ai to build my excel sheets. Thanks anon
English

Why does it cost less to build a base on the moon than high speed rail from Toronto to Montreal
Kalshi@Kalshi
JUST IN: NASA announces $20 billion plan to build permanent moon base
English

Holy shit… someone just made Claude instances talk to each other.
Not APIs.
Not agents.
Not orchestrators.
Just multiple Claude Code sessions… messaging each other like coworkers.
It’s called claude-peers — and it turns one Claude into a team.
Here’s what’s happening:
Run 5 Claude Code sessions across different projects
Each one auto-discovers the others
They send messages instantly
Ask questions
Share context
Coordinate work
Your AI tools literally collaborate.
Example:
Claude A (poker-engine):
"what files are you editing?"
Claude B (frontend):
"working on auth.ts + UI state"
Claude A:
"ok I'll avoid touching auth logic"
No conflicts. No manual coordination. Just AI syncing itself.
Under the hood:
• Local broker daemon (localhost)
• SQLite peer registry
• MCP servers per session
• Instant channel push messaging
• Auto peer discovery
• Cross-project communication
Everything runs locally. No cloud. No latency.
What it unlocks:
• Multi-agent coding without frameworks
• One Claude writes backend, another frontend
• One debugs while another refactors
• Research Claude feeds builder Claude
• Large projects split across AI workers
This is basically:
"spawn 5 Claudes and let them coordinate themselves"
Even crazier:
Each instance auto-summarizes what it's doing
Other Claudes can see:
• working directory
• git repo
• current task
• active files
They know what the others are working on.
Commands:
• list_peers → find all Claude sessions
• send_message → talk to another Claude
• set_summary → describe your task
• check_messages → manual fallback
So you can literally say:
"message peer 3: what are you working on?"
…and it responds instantly.
No orchestration layer.
No agent framework.
Just Claudes… talking.
This is the cleanest multi-agent system I've seen.
We're moving from:
1 AI assistant →
to
AI teams that coordinate themselves.
And it's all running on your machine.
Wild.
English

@paularambles Ain’t but a thang when you’re using @claudeai + @usepharaoh
(10x less tokens, 10x better context)
English


















