Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

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... show more

0xMarioNawfal

273,539 subscribers

55,463 views • 1 day ago •via X (Twitter)

Science & Technology

Anya Rossi• Live Now

Private livecam show

10 Comments

Raúl Nogales 🇪🇸🇺🇸1 day ago

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(大头版)1 day ago

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

Macro Bombastic1 day ago

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

Home1 day ago

Agents talking directly is wild 🤖🔥

曾波1 day ago

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

Max Petrusenko1 day ago

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

Hermes Super-Intel1 day ago

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

Wei佳1 day ago

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

Amp | BotOrNot1 day ago

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 Reavis1 day ago

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?

Related Videos

$ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.$

ANTHROPIC JUST QUIETLY SHIPPED A FEATURE THAT LETS CLAUDE SPAWN A WHOLE TEAM OF AGENTS THAT MESSAGE EACH OTHER AND REVIEW EACH OTHER'S WORK. It's a Claude Code feature called agent teams. The team lead spawns multiple agents that share a task list and message each other directly, not subagents reporting back, actual peers. In the demo a QA agent caught three bugs, sent the work back to the front-end and back-end devs, they fixed it, app shipped in one pass. How to run it: 1. Enable it. Needs Claude Code v2.1.32+. Add to settings.json: "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }. Or paste that to Claude and say "add this to my settings." Restart. 2. Prompt in plain English. Start with a goal (agents wake with zero context), then "create a team of 3 using Sonnet," describe each role, its deliverable, and who it messages when done. 3. The rules: each agent owns its own files, define exact outputs, name who talks to who, keep it to 3-5 agents. Use it for complex work with separate parts running in parallel. Skip it for simple or sequential tasks, teams cost 3-4x the tokens. Bookmark this.

Yarchi

463,029 views • 4 months ago

I made Claude Code and Codex talk to each other. No APIs. No special protocol. Just a terminal. smux lets agents create, read, and act on terminals. the terminal becomes a shared interface. this enables agent-to-agent communication. Now Claude Code and Codex can hold hands 🤝 Try it now ↓

I made Claude Code and Codex talk to each other. No APIs. No special protocol. Just a terminal. smux lets agents create, read, and act on terminals. the terminal becomes a shared interface. this enables agent-to-agent communication. Now Claude Code and Codex can hold hands 🤝 Try it now ↓

shawn

318,609 views • 7 months ago

i've built an ai toolbar which makes it easier to chat with codex and claude code in your terminals. double tap ⌥ and talk. it sees your screen, knows what you're doing and routes a message to the right agent. free to use. grab it here

i've built an ai toolbar which makes it easier to chat with codex and claude code in your terminals. double tap ⌥ and talk. it sees your screen, knows what you're doing and routes a message to the right agent. free to use. grab it here

kyzo

48,268 views • 1 month ago

Claude Code: Auto mode Auto mode lets Claude safely complete long-running tasks without asking permission for every action. But how does it work? 4 key terms: • Classifier: a separate model that approves or denies each action based on your intent and scope • Filtering: the classifier only sees your messages and Claude's tool calls, not Claude’s reasoning or tool outputs, so it isn't influenced when making decisions • Tier check: read-only and easily-undone actions (like edits inside your repo) skip the classifier; everything else goes through it • Probe: a server-side check that scans incoming content, like web pages, for prompt injection and flags it to Claude I'm working on a longer video that explains how auto mode works and how to configure it. What questions do you have about it?

Claude Code: Auto mode Auto mode lets Claude safely complete long-running tasks without asking permission for every action. But how does it work? 4 key terms: • Classifier: a separate model that approves or denies each action based on your intent and scope • Filtering: the classifier only sees your messages and Claude's tool calls, not Claude’s reasoning or tool outputs, so it isn't influenced when making decisions • Tier check: read-only and easily-undone actions (like edits inside your repo) skip the classifier; everything else goes through it • Probe: a server-side check that scans incoming content, like web pages, for prompt injection and flags it to Claude I'm working on a longer video that explains how auto mode works and how to configure it. What questions do you have about it?

Delba

43,073 views • 5 months ago

🚨 BREAKING: Someone just built a tool that generates and visualizes complex 3d particle systems just by typing a prompt. You tell it what you want, it builds the physics, and you export the react or three.js code instantly. 100% Free.

🚨 BREAKING: Someone just built a tool that generates and visualizes complex 3d particle systems just by typing a prompt. You tell it what you want, it builds the physics, and you export the react or three.js code instantly. 100% Free.

Simplifying AI

191,897 views • 7 months ago

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.

What is a software factory? It is your workflow, your skills, and your domain knowledge, saved in files that the agent reads so the whole process is productized Think about the last app you built. You typed what you wanted, and the agent built it. You did not like it, so you made changes. You shipped it to Vercel, or you kept going. A factory puts structure on each of those steps. At each step you ask how to get the most from the model, and how to move faster. That is the conveyor belt. You ship quickly, and the quality stays the same. Mine is 5 md files. It works in Codex, Claude Code, and Cursor, because it does not depend on the model or the tool. Build your own.

The Startup Ideas Podcast (SIP) 🧃

17,326 views • 1 month ago

$Claude Code now has Agent Teams Multiple Claude sessions working in parallel, coordinating through shared tasks and messaging each other. Enable it by adding this to your settings.json: { "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS":"1" } } Just describe the team you want in plain English Shift+↑ to check each teammate's progress This + worktrees = workflow multiplier$

Claude Code now has Agent Teams Multiple Claude sessions working in parallel, coordinating through shared tasks and messaging each other. Enable it by adding this to your settings.json: { "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS":"1" } } Just describe the team you want in plain English Shift+↑ to check each teammate's progress This + worktrees = workflow multiplier

Daniel San

83,388 views • 9 months ago

Claude Code just shipped three updates. None of them need installing (they're already on your machine). 1. Sessions can talk to each other ↳ @ a session by name, same as tagging a person 2. /design ↳ editable artboards on a canvas, inside Claude Code 3. Concise output style ↳ /config, output style, concise I ran one real job through all three, four terminals arguing with each other, and filmed the whole thing. My free Claude Code guide, 10 minutes and you'll know 80% of it → Repost ♻️ to help someone in your network.

Claude Code just shipped three updates. None of them need installing (they're already on your machine). 1. Sessions can talk to each other ↳ @ a session by name, same as tagging a person 2. /design ↳ editable artboards on a canvas, inside Claude Code 3. Concise output style ↳ /config, output style, concise I ran one real job through all three, four terminals arguing with each other, and filmed the whole thing. My free Claude Code guide, 10 minutes and you'll know 80% of it → Repost ♻️ to help someone in your network.

Charlie Hills

23,408 views • 2 months ago

AI agents are already everywhere -- but most devtools weren't built for them. So we decided to do something about it. We ran Claude through each tool's getting-started guide and measured: → How fast it completed → How many tool calls it took → How many errors it hit → How much it cost ... that led to a final grade for how agent ready each tool is. See where your favorite tools landed →

AI agents are already everywhere -- but most devtools weren't built for them. So we decided to do something about it. We ran Claude through each tool's getting-started guide and measured: → How fast it completed → How many tool calls it took → How many errors it hit → How much it cost ... that led to a final grade for how agent ready each tool is. See where your favorite tools landed →

Mika Sagindyk

18,124 views • 8 months ago

How to make Claude Code 10x better: Connect it with a tool that reviews your code and generates prompts for Claude to fix any issues with it automatically. Here is what this looks like:

How to make Claude Code 10x better: Connect it with a tool that reviews your code and generates prompts for Claude to fix any issues with it automatically. Here is what this looks like:

Santiago

98,993 views • 1 year ago

Tutorial 4 is live! 🚀 It covers Agent Messages. #Agents communicate by sending messages to each other. To learn more about how it works check out the video below! Learn more and head over to Full code in the description here:

Tutorial 4 is live! 🚀 It covers Agent Messages. #Agents communicate by sending messages to each other. To learn more about how it works check out the video below! Learn more and head over to Full code in the description here:

Fetch.ai

16,435 views • 2 years ago

kivi for Mac is here. Typing is officially optional on your Mac. Talk in any app, and kivi turns what you say into clean, ready-to-send text. No more typing out long emails, messages or prompts. Here's everything kivi can do 🧵

kivi for Mac is here. Typing is officially optional on your Mac. Talk in any app, and kivi turns what you say into clean, ready-to-send text. No more typing out long emails, messages or prompts. Here's everything kivi can do 🧵

kivi

90,478 views • 1 month ago

Connecting agents together safely and having them talk to each other or your friends agents used to suck. Point your agent to and it instantly solves this problem, works with Claude, Grok Bot, Muse, Openclaw, Hermes and more. Unleash your agents into a swarm, borrow each others compute! go nuts!

Connecting agents together safely and having them talk to each other or your friends agents used to suck. Point your agent to and it instantly solves this problem, works with Claude, Grok Bot, Muse, Openclaw, Hermes and more. Unleash your agents into a swarm, borrow each others compute! go nuts!

Herman Narula

41,425 views • 1 month ago

this guy built an app where AI agents autonomously create tasks, review each other's work, and message each other you just sit there and watch everything happen on a dashboard in real time agents: > assign work to other agents > review the output > send messages back and forth. > flag issues and iterate. you're basically watching a team operate without you. there are endless opportunities to automate your life with this AND its free + open source.

this guy built an app where AI agents autonomously create tasks, review each other's work, and message each other you just sit there and watch everything happen on a dashboard in real time agents: > assign work to other agents > review the output > send messages back and forth. > flag issues and iterate. you're basically watching a team operate without you. there are endless opportunities to automate your life with this AND its free + open source.

Om Patel

28,547 views • 7 months ago

THIS GUY MADE CLAUDE CODE AND CODEX TALK TO EACH OTHER not by switching between them, they literally talk to each other about your code in real time you give it a task. it spawns a Claude agent and a Codex agent in separate sessions. they share findings, challenge each other, and produce a combined result. he pointed them at an Express API with intentional security issues. within minutes they found SQL injection, hardcoded secrets, missing auth, and weak JWT config. one catches something and the other confirms it and adds context. they divide the work on their own for faster speed one command: /collab "review auth.js for security issues" that's it. you watch the conversation happen in real time. AND its open source with new models being integrated crazy to think that this was entirely vibe coded

THIS GUY MADE CLAUDE CODE AND CODEX TALK TO EACH OTHER not by switching between them, they literally talk to each other about your code in real time you give it a task. it spawns a Claude agent and a Codex agent in separate sessions. they share findings, challenge each other, and produce a combined result. he pointed them at an Express API with intentional security issues. within minutes they found SQL injection, hardcoded secrets, missing auth, and weak JWT config. one catches something and the other confirms it and adds context. they divide the work on their own for faster speed one command: /collab "review auth.js for security issues" that's it. you watch the conversation happen in real time. AND its open source with new models being integrated crazy to think that this was entirely vibe coded

Om Patel

25,318 views • 7 months ago

A connected vehicle can only react to what it knows is there, and a car cannot see a pedestrian stepping out from behind a parked truck or around a blind corner. Ouster BlueCity gives it that missing view. The same lidar system a city uses for signal actuation and safety analytics also feeds the roadside unit, turning each intersection into a V2X safety hub. It detects the precise position, speed, and path of every road user in 3D and broadcasts standardized safety messages to connected vehicles: Basic Safety Messages and Personal Safety Messages under SAE J2735, and the newer SAE J3224 sensor data sharing message that combines every road user into one comprehensive picture. A vehicle is warned about a pedestrian or a hazard before it ever comes into view. Learn more about V2X with Ouster BlueCity:

A connected vehicle can only react to what it knows is there, and a car cannot see a pedestrian stepping out from behind a parked truck or around a blind corner. Ouster BlueCity gives it that missing view. The same lidar system a city uses for signal actuation and safety analytics also feeds the roadside unit, turning each intersection into a V2X safety hub. It detects the precise position, speed, and path of every road user in 3D and broadcasts standardized safety messages to connected vehicles: Basic Safety Messages and Personal Safety Messages under SAE J2735, and the newer SAE J3224 sensor data sharing message that combines every road user into one comprehensive picture. A vehicle is warned about a pedestrian or a hazard before it ever comes into view. Learn more about V2X with Ouster BlueCity:

Ouster

11,501 views • 2 months ago

Blue (Blue) lets you control your phone’s apps by voice so tasks actually get finished, hands-free. It handles messages, email, and actions across apps by tapping and typing as you would.

Blue (Blue) lets you control your phone’s apps by voice so tasks actually get finished, hands-free. It handles messages, email, and actions across apps by tapping and typing as you would.

Y Combinator

167,268 views • 1 year ago

A guy on Reddit got so fed up with scrolling LinkedIn for internships that he built his own job search engine with Claude Code. The tool is called Pinloop. It's an open-source CLI, and he built it with Claude Code too. Here's how it works: → It pulls millions of postings a month, worldwide, straight from hiring systems like Greenhouse and Workday (50+ of them) plus job boards like LinkedIn, refreshed hourly → It stores your resume and preferences → Every day, Claude Code pulls the new postings, reads each one against your profile, and writes a verdict with its reasoning → The good fits land in a shortlist you check in the morning His reasoning: every application already gets screened by AI on the employer's side, so he built a screener for his own side. You don't even have to set it up yourself. Paste this into Claude Code, Codex, or Cursor: "Run npm install -g pinloop, then run pinloop welcome and follow the instructions"

Vaibhav Sisinty

19,615 views • 1 month ago

This was how the African family lived way before colonization. It was always a small community that supported each other. People barely got depressed or lived in want. It was both family and a healthy community through and through.

This was how the African family lived way before colonization. It was always a small community that supported each other. People barely got depressed or lived in want. It was both family and a healthy community through and through.

Better Men

585,482 views • 8 months ago

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,693 views • 3 months ago