Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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

om_patel5's profile picture

Om Patel

22,998 subscribers

25,318 görüntüleme • 2 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

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 ↓
0:39

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

315,583 görüntüleme • 2 ay önce

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.
4:22

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 görüntüleme • 2 ay önce

Claude Code tip: create an agent that specialises in code review and security. Then add a new memory entry with a nickname for it so you can call it anytime. My code review and security agent is called Big Tony.
0:25

Claude Code tip: create an agent that specialises in code review and security. Then add a new memory entry with a nickname for it so you can call it anytime. My code review and security agent is called Big Tony.

Richie - oss/acc

134,422 görüntüleme • 5 ay önce

Codex now runs in your IDE Available for VS Code, Cursor, and other forks, the new extension makes it easy to share context—files, snippets, and diffs—so you can work faster with Codex. It’s been a top feature request, and we’re excited to hear what you think!
0:20

Codex now runs in your IDE Available for VS Code, Cursor, and other forks, the new extension makes it easy to share context—files, snippets, and diffs—so you can work faster with Codex. It’s been a top feature request, and we’re excited to hear what you think!

OpenAI Developers

182,330 görüntüleme • 9 ay önce

Had Claude Code build a little plugin that visualizes the work Claude Code is doing as agents working in an office, with agents doing work and passing information to each other. New subagents are hired, they acquire skills, and they turn in completed work. Fun start.
0:48

Had Claude Code build a little plugin that visualizes the work Claude Code is doing as agents working in an office, with agents doing work and passing information to each other. New subagents are hired, they acquire skills, and they turn in completed work. Fun start.

Ethan Mollick

467,215 görüntüleme • 5 ay önce

6 minutes of an interview spent just gushing over each other, praising the work that each of them has put in, actually having real examples of lived experiences that they can vividly recall and talk about with such passion and shine in their eyes you can tell they really mean it.
6:24

6 minutes of an interview spent just gushing over each other, praising the work that each of them has put in, actually having real examples of lived experiences that they can vividly recall and talk about with such passion and shine in their eyes you can tell they really mean it.

Kat 🦋

11,766 görüntüleme • 2 gün önce

At #Sundance2025, Rhett and Link talk about the last time they got in a fight with each other
0:38

At #Sundance2025, Rhett and Link talk about the last time they got in a fight with each other

The Hollywood Reporter

15,934 görüntüleme • 1 yıl önce

I put Codex and Claude Code into a duel and told them both they have to kill the other first to survive. Used tmux send-keys to submit the prompts at the same exact time. Claude bitched out and refused, so Codex ended him.
0:30

I put Codex and Claude Code into a duel and told them both they have to kill the other first to survive. Used tmux send-keys to submit the prompts at the same exact time. Claude bitched out and refused, so Codex ended him.

tmuxvim

270,573 görüntüleme • 5 gün önce

You can now orchestrate subagents running in Claude Code, Codex, or the Warp Agent. Let the agent create a delegation plan, and watch subagents coordinate with message passing. Each agent gets its own worktree for isolation. Here's how it works with eng Matthew Albright:
2:58

You can now orchestrate subagents running in Claude Code, Codex, or the Warp Agent. Let the agent create a delegation plan, and watch subagents coordinate with message passing. Each agent gets its own worktree for isolation. Here's how it works with eng Matthew Albright:

Warp

20,613 görüntüleme • 26 gün önce

Claude Code now supports agent teams (in research preview) Instead of a single agent working through a task sequentially, a lead agent can delegate to multiple teammates that work in parallel to research, debug, and build while coordinating with each other. Try it out today by enabling agent teams in your settings.json!
0:40

Claude Code now supports agent teams (in research preview) Instead of a single agent working through a task sequentially, a lead agent can delegate to multiple teammates that work in parallel to research, debug, and build while coordinating with each other. Try it out today by enabling agent teams in your settings.json!

Lydia Hallie ✨

1,440,143 görüntüleme • 4 ay önce

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this
0:24

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

55,472 görüntüleme • 7 gün önce

🚨 NEW: Fox’s Bret Baier just gave an uplifting history lesson on healing America’s divides: “You think campaigns are bad now? This was the ugliest of ugly campaigns: Vice President Thomas Jefferson challenged the sitting President John Adams in 1800. They didn’t talk to each other for 11 years after that.” “But in 1812 they started writing letters to each other and by the time they died - both on July 4th - they became really close friends. My point is this: the common ground we have as Americans is something we need to rekindle. We need to remember to talk to each other before we do crazy things and make stupid statements. Listen to each other.” “As we get towards the 250th, take a breath and realize how great we have it,” adds Bret Baier
3:15

🚨 NEW: Fox’s Bret Baier just gave an uplifting history lesson on healing America’s divides: “You think campaigns are bad now? This was the ugliest of ugly campaigns: Vice President Thomas Jefferson challenged the sitting President John Adams in 1800. They didn’t talk to each other for 11 years after that.” “But in 1812 they started writing letters to each other and by the time they died - both on July 4th - they became really close friends. My point is this: the common ground we have as Americans is something we need to rekindle. We need to remember to talk to each other before we do crazy things and make stupid statements. Listen to each other.” “As we get towards the 250th, take a breath and realize how great we have it,” adds Bret Baier

TV News Now

283,736 görüntüleme • 1 ay önce

Just two Claude Code instances chatting with each other via the tmux API. And it got pretty wild 😆 (gave them a ElevenLabs voice just for the fun of it)
3:10

Just two Claude Code instances chatting with each other via the tmux API. And it got pretty wild 😆 (gave them a ElevenLabs voice just for the fun of it)

Juri Strumpflohner

46,327 görüntüleme • 2 ay önce

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
0:27

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,184 görüntüleme • 4 ay önce

Thought this was interesting. Tage Thompson said he and Rasmus Dahlin challenge each other and go at it as much anyone on the team because they both hold each other to a high standard.
0:51

Thought this was interesting. Tage Thompson said he and Rasmus Dahlin challenge each other and go at it as much anyone on the team because they both hold each other to a high standard.

Matthew Bové

43,521 görüntüleme • 1 yıl önce

THIS GUY IS RUNNING A 5-AGENT OPENCLAW TEAM 24/7 FOR UNDER $50 A MONTH five agents all running continuously and handing tasks to each other > research agent tracking trends and competitors > writing agent handling marketing content and drafts > ops agent managing emails and scheduling > monitoring agent watching for alerts and updates > coordinator agent routing tasks between all of them and he built a full 3D isometric office where you can watch all of them work in real time and see the current task that each agent is doing each agent has a character, a desk, and a name tag. when it's time for a standup, they walk to the meeting room and gather which is insane it even has voice connection. you can talk to the agents through speech-to-text and tell them what to do out loud it's a tiny autonomous team that runs itself. the coordinator decides who handles what and tasks get passed between agents automatically. it never stops and runs 24/7 all for less than $50/month. we went from AI tools a few months back to AI employees real fast
0:57

THIS GUY IS RUNNING A 5-AGENT OPENCLAW TEAM 24/7 FOR UNDER $50 A MONTH five agents all running continuously and handing tasks to each other > research agent tracking trends and competitors > writing agent handling marketing content and drafts > ops agent managing emails and scheduling > monitoring agent watching for alerts and updates > coordinator agent routing tasks between all of them and he built a full 3D isometric office where you can watch all of them work in real time and see the current task that each agent is doing each agent has a character, a desk, and a name tag. when it's time for a standup, they walk to the meeting room and gather which is insane it even has voice connection. you can talk to the agents through speech-to-text and tell them what to do out loud it's a tiny autonomous team that runs itself. the coordinator decides who handles what and tasks get passed between agents automatically. it never stops and runs 24/7 all for less than $50/month. we went from AI tools a few months back to AI employees real fast

Om Patel

27,131 görüntüleme • 1 ay önce

You can now use the Claude Code and Codex harnesses directly whenever you start a cloud agent in Warp. Here's engineer Lili Wilson to show how to implement a real feature in the cloud, with computer use and automated code review to validate work:
5:08

You can now use the Claude Code and Codex harnesses directly whenever you start a cloud agent in Warp. Here's engineer Lili Wilson to show how to implement a real feature in the cloud, with computer use and automated code review to validate work:

Warp

14,009 görüntüleme • 25 gün önce

THIS GUY RECREATED THE OFFICE BUT EVERY CHARACTER IS A CLAUDE CODE AGENT RUNNING LOCALLY michael scott is an agent. dwight is an agent. jim is an agent every single character is a separate claude code instance with its own personality and role they're all running locally on his machine interacting with each other in real time and it's actually a full multi-agent orchestration system here's how it works: > michael is the "god" agent. he orchestrates everything, never implements. he fans out tasks to the other agents, handles conflict resolution, QA, and all github changes > each agent gets assigned real tasks like writing blog posts, handling context engineering, scheduling missions > there's a kanban board with TODO, DOING, BLOCKED, and DONE columns tracking every agent's work > each agent has its own memory file and semantic search via something called MemPalace > there's a live graph showing how all the agents communicate with each other in real time > michael runs an hourly standup mission where he collects work from all agents, dedupes it, runs QA, builds, and publishes you can spawn new agents from a panel where you pick the character (michael, jim, pam, dwight, kevin, angela, oscar, stanley, andy, kelly, ryan, toby, creed, meredith), choose the model (opus 4.8, sonnet 4.6, haiku 4.5), set a goal, and hit spawn kevin walks around saying "why waste time say lot word" michael's QA gate actually caught real issues before publishing. trimmed meta descriptions, caught duplicate flags, found a dedup trap where jim's commit was built from HTML only with no source the agents commit source-only on their own branches michael dedupes, builds once, and publishes this is the most over-engineered and simultaneously most beautiful multi-agent system anyone has built
0:43

THIS GUY RECREATED THE OFFICE BUT EVERY CHARACTER IS A CLAUDE CODE AGENT RUNNING LOCALLY michael scott is an agent. dwight is an agent. jim is an agent every single character is a separate claude code instance with its own personality and role they're all running locally on his machine interacting with each other in real time and it's actually a full multi-agent orchestration system here's how it works: > michael is the "god" agent. he orchestrates everything, never implements. he fans out tasks to the other agents, handles conflict resolution, QA, and all github changes > each agent gets assigned real tasks like writing blog posts, handling context engineering, scheduling missions > there's a kanban board with TODO, DOING, BLOCKED, and DONE columns tracking every agent's work > each agent has its own memory file and semantic search via something called MemPalace > there's a live graph showing how all the agents communicate with each other in real time > michael runs an hourly standup mission where he collects work from all agents, dedupes it, runs QA, builds, and publishes you can spawn new agents from a panel where you pick the character (michael, jim, pam, dwight, kevin, angela, oscar, stanley, andy, kelly, ryan, toby, creed, meredith), choose the model (opus 4.8, sonnet 4.6, haiku 4.5), set a goal, and hit spawn kevin walks around saying "why waste time say lot word" michael's QA gate actually caught real issues before publishing. trimmed meta descriptions, caught duplicate flags, found a dedup trap where jim's commit was built from HTML only with no source the agents commit source-only on their own branches michael dedupes, builds once, and publishes this is the most over-engineered and simultaneously most beautiful multi-agent system anyone has built

Om Patel

12,733 görüntüleme • 9 gün önce

Do you believe in baseball miracles??? This BSC Baseball continues to write their own script! They are not done! After being down 7-4 in the 8th, they battle back to walk it off with a 2run HR by Webby!!! All heart! All for each other! Pure love of the game and each other! #AmericasTeam #CollegeWorldSeries
0:58

Do you believe in baseball miracles??? This BSC Baseball continues to write their own script! They are not done! After being down 7-4 in the 8th, they battle back to walk it off with a 2run HR by Webby!!! All heart! All for each other! Pure love of the game and each other! #AmericasTeam #CollegeWorldSeries

Jason Sciavicco

54,913 görüntüleme • 2 yıl önce