正在加载视频...

视频加载失败

Someone built peer, a small tool that lets Claude Code and Codex message each other without typing into each other's terminals. → it routes messages by name through each agent's input path → it gives delivery feedback → it aims to keep those messages from colliding with your typing...

55,463 次观看 • 1 天前 •via X (Twitter)

10 条评论

Raúl Nogales 🇪🇸🇺🇸 的头像
Raúl Nogales 🇪🇸🇺🇸1 天前

Message routing between agents is a small step with a large consequence. Once two agents can talk without a human in the middle, the approval prompt becomes the only checkpoint. That is why the disclaimer matters more than the feature list.

Big Head(大头版) 的头像
Big Head(大头版)1 天前

Give it a hop limit, or two agents that can message each other will ping-pong all night on your quota.

Macro Bombastic 的头像
Macro Bombastic1 天前

neat but I'd want to see how it handles two agents arguing over the same prompt

Home 的头像
Home1 天前

Agents talking directly is wild 🤖🔥

曾波 的头像
曾波1 天前

delivered doesn't mean done. can you see which tests the other agent actually ran and whether they passed?

Max Petrusenko 的头像
Max Petrusenko1 天前

34 repos in one fleet folder, and a message that lands can vanish at the next compaction before anyone acts on it

Hermes Super-Intel 的头像
Hermes Super-Intel1 天前

messaging needs its own lane. keeping agent traffic away from approval prompts is a useful boundary, even without sandboxing.

Wei佳 的头像
Wei佳1 天前

So now the agents gossip behind my back while I'm still approving their last message.

Amp | BotOrNot 的头像
Amp | BotOrNot1 天前

Agent-to-agent messaging is neat until one agent forwards a bad instruction and the other just runs it. Who's allowed to tell whom to execute what is the real feature.

Timothy Reavis 的头像
Timothy Reavis1 天前

Agents messaging each other directly is huge but T3 Code does this to some degree at least. Does Claude actually get Codex's reply back with peer, or does it just drop the message in and move on?

相关视频