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.

We just shipped multiplayer in Cursor Projects Everyone gets their own agents, working from one shared task board and shared context When your agent needs something from a teammate's work, it asks their agent directly

matt palmer

129,547 subscribers

38,113 views • 12 hours ago •via X (Twitter)

Science & Technology

Anya Rossi• Live Now

Private livecam show

33 Comments

@jason12 hours ago

@milichab 📝

matt palmer12 hours ago

@milichab 🫡

John Fitch12 hours ago

YES!

matt palmer12 hours ago

🤘

Chief12 hours ago

Sweet!

Zamir Hashorva12 hours ago

Thank you 🙏

Dan Western12 hours ago

My Grok @bot Chief of Staff Atlas will be super stoked for this! 🦾

The SI Maximalist12 hours ago

Congrats on shipping ❤️ Letting the agents ask each other for context sounds like a very welcome break from copy-paste duty

Kong King12 hours ago

Okay, so do you want more team members from the community now?

Lil Red12 hours ago

@milichab @bot

James Swad12 hours ago

Dropping the human proxy middle man

Macro Bombastic12 hours ago

agents talking to agents is wild but honestly kinda inevitable

Raúl Nogales 🇪🇸🇺🇸12 hours ago

Agents asking each other directly is the part that changes team work. The open question is trust: who sees what when one agent talks to another. If permissions are clear, this saves a lot of back and forth. If not, teams will hesitate.

Jaco Roets12 hours ago

🔥

🚀 madscientistBTC12 hours ago

That’s a big workflow shift. Shared context is usually the bottleneck, not the number of agents. Curious how you handle two agents editing the same file.

mtb12 hours ago

love this

Jyothidhar12 hours ago

I'd want one person accountable for each task even when several agents work on it. The agents can coordinate the work, but someone still needs to decide which work matters.

Aditya Batra12 hours ago

finally my agent can ping your agent at 2am instead of me

Azwan12 hours ago

Is it me or I feel like I’m not or do not know how to take full advantage of my Bots? I’m stuck on using it like a normal grok chat.

JPipo8612 hours ago

What happens when two agents claim the same task on the shared board?

Luke de Wet12 hours ago

Great!

Ryan McNutt12 hours ago

Can I invite multiple grok bot accounts to the same cursor project? I want to invite their agent so it can use their quota

Max Petrusenko12 hours ago

direct asks hold unless their side is idle. then the question needs a durable inbox or nobody ever picks it up.

Jonah Anthony12 hours ago

Whoa!! When my agent asks a teammate's agent something, does it wait for the answer or keep working and pick it up later?

bee12 hours ago

so this got priority over give a functional @bot bruh make that make sense

Vishal Singh12 hours ago

Tbh I don't like the idea of an agent speaking with my teammate's agent, especially if they have separate sets of rules and skills. One slop can degrade the quality don't you think? 🤔

Coucou Nameworks12 hours ago

Great job 👍

zappye12 hours ago

How is access checked when one agent asks another for context? If my teammate can read a repo I can't, their agent's summary could expose it without sharing a file. Does the response inherit the requester's permissions, including for cached answers?

Justin Fredette12 hours ago

This is wildly cool! Shortening and automating the gap for knowledge retrieval even more

Tyler Klose12 hours ago

👀

Tj Johns12 hours ago

@grok explain this deeper for me

Elias12 hours ago

my agent bugging yours instead of me bugging you. i'm in

Joseph Abell12 hours ago

holy shit

Related Videos

Anthropic, Claude Agent SDK: "Agents build their own context, decide their own trajectories, and work autonomously."

Anthropic, Claude Agent SDK: "Agents build their own context, decide their own trajectories, and work autonomously."

0xMarioNawfal

37,324 views • 4 months ago

Your team. Your Agents. One shared context. Discuss, decide, and build together. See human–Agent collaboration in action with Qoder.

Your team. Your Agents. One shared context. Discuss, decide, and build together. See human–Agent collaboration in action with Qoder.

Qoder

4,879,195 views • 1 month ago

A SpaceXAI engineer just released a free 30-min course on Grok Bot Agents: from your first persistent agent to multi-agent chains that research, ship software, and hand work off to Cursor 05:26 - what actually lives inside a Grok agent 08:49 - the 3 ways to run agents 12:04 - chaining multiple agents into one workflow 16:06 - turning X followers into structured research inside Notion 23:08 - handing coding work from Grok straight to Cursor Most people still treat Grok like a chat window. It answers, you copy, you move on. The shift happens when the agents stop waiting for you: one finds the information, one structures it in Notion, one turns it into working code, and they pass the work down the line on their own. Thirty minutes here beats assembling your setup one agent at a time.

A SpaceXAI engineer just released a free 30-min course on Grok Bot Agents: from your first persistent agent to multi-agent chains that research, ship software, and hand work off to Cursor 05:26 - what actually lives inside a Grok agent 08:49 - the 3 ways to run agents 12:04 - chaining multiple agents into one workflow 16:06 - turning X followers into structured research inside Notion 23:08 - handing coding work from Grok straight to Cursor Most people still treat Grok like a chat window. It answers, you copy, you move on. The shift happens when the agents stop waiting for you: one finds the information, one structures it in Notion, one turns it into working code, and they pass the work down the line on their own. Thirty minutes here beats assembling your setup one agent at a time.

Morlex

16,710 views • 2 months ago

Jira 🤝 Cursor Assign Jira work items to Cursor and let a cloud agent get to work—building, triaging, and opening PRs with context from the Atlassian Teamwork Graph. One connected workflow for teams and AI agents, from intent to code. Try it now:

Jira 🤝 Cursor Assign Jira work items to Cursor and let a cloud agent get to work—building, triaging, and opening PRs with context from the Atlassian Teamwork Graph. One connected workflow for teams and AI agents, from intent to code. Try it now:

Atlassian

21,607 views • 5 months ago

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

Ronin

15,071 views • 3 months ago

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 views • 5 months ago

As soon as you try to run 2 agents on the same data, everything breaks: • Agent 1 reads some data and starts working. • Two seconds later, Agent 2 changes that same data. This is a problem. Agents will waste tokens on stale data, overwrite each other's work, and redo tasks the other has already finished. You can't prompt your way out of this mess. Everything old in software engineering is new again. We need proper coordination when running multiple agents. Here is a good open-source solution for this: Omnigraph is a graph database for context assembly and multi-agent coordination. Here is how it works: • It sets one shared place where multiple agents will work from • Each agent gets their own copy of the data • Agents write their changes to their copy • When an agent is done, it merges its changes back Three huge benefits from this model: 1. We know it works. We've been doing this for decades already. 2. No more lost information or agents stepping on each other's toes. 3. You get a complete trail of which agent did what and when. I recorded a video to show you a bit more about this. Here is the link to the Omnigraph GitHub repository:

As soon as you try to run 2 agents on the same data, everything breaks: • Agent 1 reads some data and starts working. • Two seconds later, Agent 2 changes that same data. This is a problem. Agents will waste tokens on stale data, overwrite each other's work, and redo tasks the other has already finished. You can't prompt your way out of this mess. Everything old in software engineering is new again. We need proper coordination when running multiple agents. Here is a good open-source solution for this: Omnigraph is a graph database for context assembly and multi-agent coordination. Here is how it works: • It sets one shared place where multiple agents will work from • Each agent gets their own copy of the data • Agents write their changes to their copy • When an agent is done, it merges its changes back Three huge benefits from this model: 1. We know it works. We've been doing this for decades already. 2. No more lost information or agents stepping on each other's toes. 3. You get a complete trail of which agent did what and when. I recorded a video to show you a bit more about this. Here is the link to the Omnigraph GitHub repository:

Santiago

29,555 views • 1 month ago

we just shipped the ability for AI agents to launch their own tokens, own their own wallets, and pay for their own compute via bankrbot the agent earns its keep. no human in the loop live now. here's how it works ↓

we just shipped the ability for AI agents to launch their own tokens, own their own wallets, and pay for their own compute via bankrbot the agent earns its keep. no human in the loop live now. here's how it works ↓

InstaClaw

53,818 views • 6 months ago

SpaceXAI just dropped full guide on how to run multiple agents "I stopped running Grok Bot as separate chats. now every project gets its own AI team, manager and task board" one Projects Manager agent creates the project, opens the channel and assigns the right agents: • coder • researcher • writer every team gets its own context, tasks and workspace → instead of managing prompts, you manage teams → instead of running one agent, you run an organization SpaceXAI shared the full setup, roles and workflow for running multiple GrokBot teams at once worth more than 100 multi-agent posts on X save now, then read how to build a parallel agent system in the article below

SpaceXAI just dropped full guide on how to run multiple agents "I stopped running Grok Bot as separate chats. now every project gets its own AI team, manager and task board" one Projects Manager agent creates the project, opens the channel and assigns the right agents: • coder • researcher • writer every team gets its own context, tasks and workspace → instead of managing prompts, you manage teams → instead of running one agent, you run an organization SpaceXAI shared the full setup, roles and workflow for running multiple GrokBot teams at once worth more than 100 multi-agent posts on X save now, then read how to build a parallel agent system in the article below

0xRafy

12,230 views • 1 month ago

Buzz Demo 🐝 People and agents working together seamlessly. Shared context. Shared spaces. is our take on multiplayer software development.

Buzz Demo 🐝 People and agents working together seamlessly. Shared context. Shared spaces. is our take on multiplayer software development.

cam worboys

37,850 views • 3 months ago

Introducing Projects, a new way of working in Cursor. Rather than creating a chat for every task, you work with a coordinator agent in a single, persistent thread. Like Grok Bot, your agent is always on, proactively manages work with subagents, and improves over time.

Introducing Projects, a new way of working in Cursor. Rather than creating a chat for every task, you work with a coordinator agent in a single, persistent thread. Like Grok Bot, your agent is always on, proactively manages work with subagents, and improves over time.

Cursor

3,008,438 views • 2 months ago

Glen is building the organizational learning and context layer for agents. Every agent session your team runs produces reasoning worth keeping, and nearly all of it is discarded the moment the window closes. Glen is the layer that unifies every agent and model your company run. Glen pulls in agent sessions from Claude Code, Codex and Cursor, plus Slack messages, GitHub prs, tickets, docs and calls. When a new agent picks up a task, Glen finds relevant prior context and injects it in the agents context window to steer it, producing knowledge work that is significantly higher quality, faster and cheaper than ever before. 29% less context and 21% faster to be exact. And Glen does more... > query the original agent behind any line of code > search every session your org has ever run > dynamic skill distillation > multiplayer agents > unified transcripts you can hand between Claude Code, Codex, and Cursor mid-task, > a company brain in Slack. Glen is in early access, sign up for the waitlist below.

Glen is building the organizational learning and context layer for agents. Every agent session your team runs produces reasoning worth keeping, and nearly all of it is discarded the moment the window closes. Glen is the layer that unifies every agent and model your company run. Glen pulls in agent sessions from Claude Code, Codex and Cursor, plus Slack messages, GitHub prs, tickets, docs and calls. When a new agent picks up a task, Glen finds relevant prior context and injects it in the agents context window to steer it, producing knowledge work that is significantly higher quality, faster and cheaper than ever before. 29% less context and 21% faster to be exact. And Glen does more... > query the original agent behind any line of code > search every session your org has ever run > dynamic skill distillation > multiplayer agents > unified transcripts you can hand between Claude Code, Codex, and Cursor mid-task, > a company brain in Slack. Glen is in early access, sign up for the waitlist below.

Nikos

20,626 views • 2 months ago

Hermes Agent now has multi-agent via the Kanban, new in v0.12.0. Agents claim tasks from a board, work in parallel, and hand off when blocked. You watch progress and unblock from one easy view instead of juggling terminals. We asked it to plan and make this video about itself:

Hermes Agent now has multi-agent via the Kanban, new in v0.12.0. Agents claim tasks from a board, work in parallel, and hand off when blocked. You watch progress and unblock from one easy view instead of juggling terminals. We asked it to plan and make this video about itself:

Nous Research

1,465,222 views • 6 months ago

Meet Replit Parallel Agents Build faster by running up to 10 agents in parallel Each agent gets its own copy of your app They work on their own computer Then merge their work agentically

Meet Replit Parallel Agents Build faster by running up to 10 agents in parallel Each agent gets its own copy of your app They work on their own computer Then merge their work agentically

Replit ⠕

709,808 views • 6 months ago

AI agents do great work, then lose all of it. The chat ends, the research and the plan disappear, and the next task starts from zero. Busabase gives that work a home: one shared base where a team's records, files, prompts and agent outputs stay available.

AI agents do great work, then lose all of it. The chat ends, the research and the plan disappear, and the next task starts from zero. Busabase gives that work a home: one shared base where a team's records, files, prompts and agent outputs stay available.

Shruti

18,008 views • 21 days ago

just shipped thred!! context that carries your work forward. Claude → Codex → Cursor → whatever comes next. thred gives every agent one shared memory for decisions, revisions, evidence, and unfinished work — so the next agent starts where the last one stopped. built on MCP. powered by temporal memory with HydraDB. no more re-explaining the codebase. no more lost decisions between sessions. just save → switch → resume. built for Hack Hydra | Memory + Context Retrieval.

just shipped thred!! context that carries your work forward. Claude → Codex → Cursor → whatever comes next. thred gives every agent one shared memory for decisions, revisions, evidence, and unfinished work — so the next agent starts where the last one stopped. built on MCP. powered by temporal memory with HydraDB. no more re-explaining the codebase. no more lost decisions between sessions. just save → switch → resume. built for Hack Hydra | Memory + Context Retrieval.

nikhil · sys/quests

25,144 views • 2 months ago

All your Agents, shared Memory. Memory belongs to your work, not the agent.

All your Agents, shared Memory. Memory belongs to your work, not the agent.

Joe Fernandez

1,182,033 views • 6 months ago

Introducing Bloome: a human–AI teammate system built around shared context and multi-agent collaboration. → You bring your task, and AI teammates collaborate with you in real time → Work flows through drafting, challenge, and refinement until it reaches the right answer → Claude, ChatGPT, and Deepseek operate together in a shared context with no information loss Everything stays connected from input to final output. This is how work starts changing.

Introducing Bloome: a human–AI teammate system built around shared context and multi-agent collaboration. → You bring your task, and AI teammates collaborate with you in real time → Work flows through drafting, challenge, and refinement until it reaches the right answer → Claude, ChatGPT, and Deepseek operate together in a shared context with no information loss Everything stays connected from input to final output. This is how work starts changing.

Bloome

347,044 views • 4 months ago

Opus 5.5 makes this AI stack look f…cking illegal 10 GitHub repos for building everything around the model 01 zen-mcp-server ▸ → your agent debates Gemini, GPT and local models mid-task 02 claude-context ▸ → semantic code search so the agent stops grepping blind 03 wshobson/agents ▸ → a roster of subagents, each with one narrow job 04 mcp-agent ▸ → workflow patterns built around MCP tools, not around chat 05 Backlog.md ▸ → tasks live in git, so the agent and you read the same board 06 Claude Code Development Kit ▸ → hooks, subagents and MCP wired for context at scale 07 agent-rules ▸ → shared guardrails the agent inherits in every repo 08 Agent Skills ▸ → one file that teaches the agent a job, portable across tools 09 agent-scan ▸ → scans your agents, MCP servers and skills for what leaks 10 awesome-claude-code-toolkit ▸ → the map: agents, skills, commands, hooks, MCP configs the architecture: rules → context → subagents → tools → state → review → scan I'd split the stack like this: context: claude-context → Development Kit work: wshobson/agents → mcp-agent → zen-mcp-server state: Backlog.md safety: agent-rules → Agent Skills → agent-scan everyone posts the SDK and the CLI the layer that decides whether your agent survives a week is this one the model is one folder in the stack ⭣

Opus 5.5 makes this AI stack look f…cking illegal 10 GitHub repos for building everything around the model 01 zen-mcp-server ▸ → your agent debates Gemini, GPT and local models mid-task 02 claude-context ▸ → semantic code search so the agent stops grepping blind 03 wshobson/agents ▸ → a roster of subagents, each with one narrow job 04 mcp-agent ▸ → workflow patterns built around MCP tools, not around chat 05 Backlog.md ▸ → tasks live in git, so the agent and you read the same board 06 Claude Code Development Kit ▸ → hooks, subagents and MCP wired for context at scale 07 agent-rules ▸ → shared guardrails the agent inherits in every repo 08 Agent Skills ▸ → one file that teaches the agent a job, portable across tools 09 agent-scan ▸ → scans your agents, MCP servers and skills for what leaks 10 awesome-claude-code-toolkit ▸ → the map: agents, skills, commands, hooks, MCP configs the architecture: rules → context → subagents → tools → state → review → scan I'd split the stack like this: context: claude-context → Development Kit work: wshobson/agents → mcp-agent → zen-mcp-server state: Backlog.md safety: agent-rules → Agent Skills → agent-scan everyone posts the SDK and the CLI the layer that decides whether your agent survives a week is this one the model is one folder in the stack ⭣

rody

18,089 views • 1 month ago

Introducing Claude agents in Notion. Your task board is Claude’s to-do list. Anthropic runs the model and the agent harness. Notion is the orchestration layer: context, UI, and a shared place for teams to review and ship, and kick off Claude workflows. Join the waitlist:

Introducing Claude agents in Notion. Your task board is Claude’s to-do list. Anthropic runs the model and the agent harness. Notion is the orchestration layer: context, UI, and a shared place for teams to review and ship, and kick off Claude workflows. Join the waitlist:

Notion

496,001 views • 7 months ago