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.

Cloud agents keep working while you go get pizza. “It has done excellent work across six different repositories, fixing quite a big issue in our system.” Dhravya Shah from supermemory gave Vorflux three engineering tasks before heading out to eat. He came back to changes and a migration file... show more

Prasanna S

46,798 subscribers

14,827 views • 29 days ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

6 Comments

weisser29 days ago

@DhravyaShah @supermemory great video. really captured the vibe of the space!

Dhravya Shah29 days ago

@supermemory great working with you guys!

Andrei Shemet29 days ago

@DhravyaShah @supermemory The fact that it worked across six repos and still left clean changes is crazy!

aniketh29 days ago

@DhravyaShah @supermemory @DhravyaShah lessgo

dCodes29 days ago

@DhravyaShah @supermemory Crazy

Kinjal Goswami29 days ago

@DhravyaShah @supermemory coming back from lunch to a fully fixed codebase is literally the dream.....

Related Videos

Auto-review is a new mode that lets Codex work longer with fewer approvals and safer execution. It helps Codex keep moving through tests, builds, and more, including during long tasks and automations, while a separate agent checks higher-risk steps in context before they run.

Auto-review is a new mode that lets Codex work longer with fewer approvals and safer execution. It helps Codex keep moving through tests, builds, and more, including during long tasks and automations, while a separate agent checks higher-risk steps in context before they run.

OpenAI Developers

438,976 views • 6 months ago

We just launched the supermemory company brain It does everything for us. answers our questions, helps in research, and general everyday work too. You can build your own using the supermemory API, or use our pre-built slackbot. Here's exactly how we use supermemory.

We just launched the supermemory company brain It does everything for us. answers our questions, helps in research, and general everyday work too. You can build your own using the supermemory API, or use our pre-built slackbot. Here's exactly how we use supermemory.

Dhravya Shah

24,822 views • 3 months ago

Cloud agents work while you eat, sleep, and take the subway. "Every morning I'll spin up a session on the way to work." Melius is a small and nimble startup, and Devin gives them the engineering capacity of a 100-person team. That's why the fastest moving startups use Devin.

Cloud agents work while you eat, sleep, and take the subway. "Every morning I'll spin up a session on the way to work." Melius is a small and nimble startup, and Devin gives them the engineering capacity of a 100-person team. That's why the fastest moving startups use Devin.

Cognition

122,114 views • 2 months ago

You can now run supermemory locally. Introducing the supermemory local - Fully self-contained. Comes with our graph engine, embedding model, etc. - Run on any machine, with your OpenClaw🦞, hermes, claude, etc. - SDKs to add memory to your agent, or build your company brain.

You can now run supermemory locally. Introducing the supermemory local - Fully self-contained. Comes with our graph engine, embedding model, etc. - Run on any machine, with your OpenClaw🦞, hermes, claude, etc. - SDKs to add memory to your agent, or build your company brain.

Dhravya Shah

701,290 views • 4 months ago

The more agents and projects you have running, the harder it gets to keep track of everything through chat alone. This is where Hermes Kanban comes in. Here's how Hermes Kanban works, why it's worth using, and how I'd recommend setting it up: Chat is where you work with an agent. Kanban is where you manage the work across agents. Hermes Kanban gives you a visual dashboard for tracking tasks across your agents and projects. But it's much more than a task board. Here's what you can do with it: • Create tasks and assign them to specific Hermes agents. • Track what's ready, running, blocked, or completed. • Set dependencies so tasks wait for other work to finish. • Coordinate handoffs between specialized agents. • Review progress and see where something needs your attention. And with the dispatcher, Hermes can pick up tasks that are ready to run and launch the appropriate agent to handle them. Now, here's something I'd recommend: **Create a separate Kanban board for each major project.** For example: 📌 Content production Research → Drafting → Review → Assets → Done 📌 Software development Bugs → Features → Testing → Review → Done 📌 Business operations Research → Waiting → In Progress → Blocked → Done Hermes supports multiple isolated boards, so each project can have its own tasks, workspaces, logs, and agent workflows. You can also connect a board to a Hermes Project to keep the work tied to the right project context. The more work you hand off to Hermes, the more valuable this becomes. Instead of digging through conversations trying to figure out what every agent is doing, give each project its own board and manage the work from one place. 🎥 Video credit: Tom

The more agents and projects you have running, the harder it gets to keep track of everything through chat alone. This is where Hermes Kanban comes in. Here's how Hermes Kanban works, why it's worth using, and how I'd recommend setting it up: Chat is where you work with an agent. Kanban is where you manage the work across agents. Hermes Kanban gives you a visual dashboard for tracking tasks across your agents and projects. But it's much more than a task board. Here's what you can do with it: • Create tasks and assign them to specific Hermes agents. • Track what's ready, running, blocked, or completed. • Set dependencies so tasks wait for other work to finish. • Coordinate handoffs between specialized agents. • Review progress and see where something needs your attention. And with the dispatcher, Hermes can pick up tasks that are ready to run and launch the appropriate agent to handle them. Now, here's something I'd recommend: Create a separate Kanban board for each major project. For example: 📌 Content production Research → Drafting → Review → Assets → Done 📌 Software development Bugs → Features → Testing → Review → Done 📌 Business operations Research → Waiting → In Progress → Blocked → Done Hermes supports multiple isolated boards, so each project can have its own tasks, workspaces, logs, and agent workflows. You can also connect a board to a Hermes Project to keep the work tied to the right project context. The more work you hand off to Hermes, the more valuable this becomes. Instead of digging through conversations trying to figure out what every agent is doing, give each project its own board and manage the work from one place. 🎥 Video credit: Tom

Hermes Release Watch

27,640 views • 18 days 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,335 views • 1 month ago

Interestingly, as we have AI agents that run in the background, the speed of AI becomes incrementally less important than the core underlying capability level. When you could only give AI small bits of work, then the speed of response mattered a ton. The rate at which you can go back and forth with AI in real-time was the determining factor on how useful it is. But as AI agents can perform more complex and useful tasks in parallel behind the scenes, you can much more easily afford to wait longer for work to get done assuming it’s valuable. Now the focus becomes more on how you review and orchestrate the agents’ work. And the main factor is just how useful and usable is the output that the agent came back with.

Interestingly, as we have AI agents that run in the background, the speed of AI becomes incrementally less important than the core underlying capability level. When you could only give AI small bits of work, then the speed of response mattered a ton. The rate at which you can go back and forth with AI in real-time was the determining factor on how useful it is. But as AI agents can perform more complex and useful tasks in parallel behind the scenes, you can much more easily afford to wait longer for work to get done assuming it’s valuable. Now the focus becomes more on how you review and orchestrate the agents’ work. And the main factor is just how useful and usable is the output that the agent came back with.

Aaron Levie

103,880 views • 1 year ago

Google just dropped a 1-hour course on AI engineering — from building your first agent to creating autonomous systems. 7:02 — Build your first agent 13:34 — What agents can actually do 23:08 — Context engineering 32:56 — Graph engineering 54:11 — Build a fully autonomous system One agent can save you hours. A thousand agents can transform how a team works. Prompts → Agents → Loops → Graphs Most people will stop halfway through and think they understand AI engineering. But the real value comes in the second half — where you learn to build systems that keep working as AI evolves. Same model. Same tokens. Completely different results. Watch it today. The full guide to loops and graphs is below. Bookmark it before you forget ↓

Google just dropped a 1-hour course on AI engineering — from building your first agent to creating autonomous systems. 7:02 — Build your first agent 13:34 — What agents can actually do 23:08 — Context engineering 32:56 — Graph engineering 54:11 — Build a fully autonomous system One agent can save you hours. A thousand agents can transform how a team works. Prompts → Agents → Loops → Graphs Most people will stop halfway through and think they understand AI engineering. But the real value comes in the second half — where you learn to build systems that keep working as AI evolves. Same model. Same tokens. Completely different results. Watch it today. The full guide to loops and graphs is below. Bookmark it before you forget ↓

ZaraAI

28,680 views • 19 days ago

THIS GUY BUILT A 24/7 AI COMPANY WITH 7 AGENTS THAT CHECKS 48 TIMES A DAY, PICKS ITS OWN TASKS AND KEEPS WORKING WHILE HE SLEEPS 00:05 the map shows agents moving between the marketplace, research lab and command center, with each one handling a different job inside the same shared system the setup runs on 4 core layers: automatic triggers, shared memory, connected tools and an isolated verifier that checks every result before the next step starts each cycle reads the last 10 log entries, updates open tasks, saves new signals and passes the context forward, so the next agent never starts from zero one agent researches, two execute, another monitors outcomes and a read-only checker reviews the work independently, allowing several workflows to run in parallel without breaking the system bookmark this before everyone stops prompting one agent at a time and starts building AI teams that work, learn and improve around the clock

THIS GUY BUILT A 24/7 AI COMPANY WITH 7 AGENTS THAT CHECKS 48 TIMES A DAY, PICKS ITS OWN TASKS AND KEEPS WORKING WHILE HE SLEEPS 00:05 the map shows agents moving between the marketplace, research lab and command center, with each one handling a different job inside the same shared system the setup runs on 4 core layers: automatic triggers, shared memory, connected tools and an isolated verifier that checks every result before the next step starts each cycle reads the last 10 log entries, updates open tasks, saves new signals and passes the context forward, so the next agent never starts from zero one agent researches, two execute, another monitors outcomes and a read-only checker reviews the work independently, allowing several workflows to run in parallel without breaking the system bookmark this before everyone stops prompting one agent at a time and starts building AI teams that work, learn and improve around the clock

Gipp 🦅

19,071 views • 3 months ago

Tried out stripe projects this week! built a customer support bot with hermes from Nous Research + supermemory. bot remembers every customer across sessions. the piece worth highlighting, Stripe projects ships a hermes skill that lets the agent auto-provision supermemory itself. ask hermes to build the bot, it runs stripe projects add supermemory/memory. stripe creates the supermemory account, syncs the api key to .env, and bills it on your stripe invoice. and supermemory is one of 30+ providers. databases ( Neon Postgres, Supabase), hosting ( Vercel , Cloudflare), auth ( Clerk), search ( Exa), analytics ( PostHog). one CLI for the whole stack.

Tried out stripe projects this week! built a customer support bot with hermes from Nous Research + supermemory. bot remembers every customer across sessions. the piece worth highlighting, Stripe projects ships a hermes skill that lets the agent auto-provision supermemory itself. ask hermes to build the bot, it runs stripe projects add supermemory/memory. stripe creates the supermemory account, syncs the api key to .env, and bills it on your stripe invoice. and supermemory is one of 30+ providers. databases ( Neon Postgres, Supabase), hosting ( Vercel , Cloudflare), auth ( Clerk), search ( Exa), analytics ( PostHog). one CLI for the whole stack.

Muskan Jain

20,335 views • 4 months ago

Career update: i'm joining supermemory to lead Dev GTM. supermemory is the memory layer for AI products, we got the best public results on AI memory by a wide margin, 95% on the leading benchmarks. my role will be to make it easy for everyone to use. demos, walkthroughs, educational content, and the cleanest possible path from "i need memory in my agent" to shipping. pumped to be working with the coolest team oh, and the team just shipped supermemory local. fully self-contained, open source, runs on any machine in a minute!!

Career update: i'm joining supermemory to lead Dev GTM. supermemory is the memory layer for AI products, we got the best public results on AI memory by a wide margin, 95% on the leading benchmarks. my role will be to make it easy for everyone to use. demos, walkthroughs, educational content, and the cleanest possible path from "i need memory in my agent" to shipping. pumped to be working with the coolest team oh, and the team just shipped supermemory local. fully self-contained, open source, runs on any machine in a minute!!

Muskan Jain

113,703 views • 4 months ago

🎉 supermemory plugins are now FREE TO USE! Magical unified memory that is automatic, that works across agents and teams. just do `npx supermemory plugin` to set up. This is powered by a new engine we're working on and many breakthroughs in making the plugins feel magical.

🎉 supermemory plugins are now FREE TO USE! Magical unified memory that is automatic, that works across agents and teams. just do `npx supermemory plugin` to set up. This is powered by a new engine we're working on and many breakthroughs in making the plugins feel magical.

Dhravya Shah

34,545 views • 2 months ago

With ChatGPT Work, you can kick off cloud tasks directly from the desktop or mobile app. It can use your configured plugins to work across your repos, docs, Slack, and the other tools you already use. I use it constantly from my phone: hand off a task, let it run asynchronously in the cloud, and come back when the work is done.

With ChatGPT Work, you can kick off cloud tasks directly from the desktop or mobile app. It can use your configured plugins to work across your repos, docs, Slack, and the other tools you already use. I use it constantly from my phone: hand off a task, let it run asynchronously in the cloud, and come back when the work is done.

Vaibhav (VB) Srivastav

37,684 views • 3 months ago

The CTO of a $1.5B agent-native software company says we're moving towards a world where the entire team builds the product engineering system that powers your product instead of directly working on the product. They will modify the agents and the constitution of the agents to help them prioritize tasks per Eno Reyes. They will also modify the review system so that it reviews more accurately. It will be akin to a dark factory where the lights are off because it's all robots with no humans inside. In that world, there will be way more things for humans to be involved in because the debates around prioritization/product will be harder and require stronger judgment.

The CTO of a $1.5B agent-native software company says we're moving towards a world where the entire team builds the product engineering system that powers your product instead of directly working on the product. They will modify the agents and the constitution of the agents to help them prioritize tasks per Eno Reyes. They will also modify the review system so that it reviews more accurately. It will be akin to a dark factory where the lights are off because it's all robots with no humans inside. In that world, there will be way more things for humans to be involved in because the debates around prioritization/product will be harder and require stronger judgment.

Ivan Burazin

64,568 views • 6 months ago

I’ve been waiting for something like this. Using multiple AI agents sounds great until you have to keep giving each one the same context. Jarvix Jarvix is built to solve that： It carries your selected context across the AI tools you already use and brings everything together in one place. #JarvixOS You can use Jarvix Home to see your context and connections, Jarvix Search to find past information without remembering exact file names, and Self Reflection to spot patterns in the way you work. There’s also Jarvix Radio for personalized content discovery and Next Move to surface a useful direction based on your context. And the part I find most interesting: Agent Team Mode. Give Jarvix one goal, choose the agents you want to use, and it divides the work while keeping everyone on the same project context. You can watch the progress, review the result, and approve what happens next. No need to keep briefing every agent from scratch. One goal. Shared context. Multiple agents. You stay in control. That’s a much cleaner way to work with AI.

I’ve been waiting for something like this. Using multiple AI agents sounds great until you have to keep giving each one the same context. Jarvix Jarvix is built to solve that： It carries your selected context across the AI tools you already use and brings everything together in one place. #JarvixOS You can use Jarvix Home to see your context and connections, Jarvix Search to find past information without remembering exact file names, and Self Reflection to spot patterns in the way you work. There’s also Jarvix Radio for personalized content discovery and Next Move to surface a useful direction based on your context. And the part I find most interesting: Agent Team Mode. Give Jarvix one goal, choose the agents you want to use, and it divides the work while keeping everyone on the same project context. You can watch the progress, review the result, and approve what happens next. No need to keep briefing every agent from scratch. One goal. Shared context. Multiple agents. You stay in control. That’s a much cleaner way to work with AI.

Aaliya

23,225 views • 2 months ago

How did Dhravya Shah get a Cloudflare internship at 18? "I built something, it got DDoSed, so I reverse-engineered Cloudflare to protect it — wrote a blog about it, it went viral and the CTO just said: do you want to work here?" Dhravya (now founder of supermemory) didn't apply. He just built in the open until the right person noticed. Full interview about his journey below.

How did Dhravya Shah get a Cloudflare internship at 18? "I built something, it got DDoSed, so I reverse-engineered Cloudflare to protect it — wrote a blog about it, it went viral and the CTO just said: do you want to work here?" Dhravya (now founder of supermemory) didn't apply. He just built in the open until the right person noticed. Full interview about his journey below.

Julia Fedorin

168,322 views • 6 months ago

Google just released a free 2-hour course on Graph & Loop engineering: 1 prompt → 100 agents → loops → graphs, from 0% to 100%: 0% → 0:35 - graph engineering from scratch 30% → 31:17 - build your first agent graph 45% → 43:40 - run hundreds of agents in parallel 75% → 1:04:58 - loop engineering: route, check, repeat 100% → 1:25:09 - self-improving graphs that work while you sleep taught by the people who run this in production Prompts → Agents → Loops → Graphs most people keep stuffing instructions into one agent, and the real upgrade is one layer up same model, same tokens, and the only thing that changes is the shape you run it in watch it today, then save the full graph engineering guide below

Google just released a free 2-hour course on Graph & Loop engineering: 1 prompt → 100 agents → loops → graphs, from 0% to 100%: 0% → 0:35 - graph engineering from scratch 30% → 31:17 - build your first agent graph 45% → 43:40 - run hundreds of agents in parallel 75% → 1:04:58 - loop engineering: route, check, repeat 100% → 1:25:09 - self-improving graphs that work while you sleep taught by the people who run this in production Prompts → Agents → Loops → Graphs most people keep stuffing instructions into one agent, and the real upgrade is one layer up same model, same tokens, and the only thing that changes is the shape you run it in watch it today, then save the full graph engineering guide below

Hanako

27,608 views • 1 month ago

$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

Replit Agent got even better at keeping you in your creative flow! It now suggests follow-up tasks using full context of your project to build on your ideas: • new features to build • performance improvements • user experience enhancements Review the plan, accept what you want, and let tasks run in the background while you keep building.

Replit Agent got even better at keeping you in your creative flow! It now suggests follow-up tasks using full context of your project to build on your ideas: • new features to build • performance improvements • user experience enhancements Review the plan, accept what you want, and let tasks run in the background while you keep building.

Replit ⠕

29,944 views • 6 months ago

Communities can now build with a coordinated team of AI agents. Agent execution is live on connecting community decisions to the agents that carry them out. $ZZZ brings the full workflow into one workspace: Discussion → decisions → tasks → execution. 1. Members chat and vote. An agent creates tasks from those discussions and records the decisions. 2. The lead agent prioritises tasks, clarifies the details with members and presents interactive mockups for approval. 3. The lead agent coordinates a swarm of agents to complete the tasks. Watch a community discussion become a task, then see the agents get to work.

Communities can now build with a coordinated team of AI agents. Agent execution is live on connecting community decisions to the agents that carry them out. $ZZZ brings the full workflow into one workspace: Discussion → decisions → tasks → execution. 1. Members chat and vote. An agent creates tasks from those discussions and records the decisions. 2. The lead agent prioritises tasks, clarifies the details with members and presents interactive mockups for approval. 3. The lead agent coordinates a swarm of agents to complete the tasks. Watch a community discussion become a task, then see the agents get to work.

zzz

14,690 views • 18 days ago