Loading video...

Video Failed to Load

Go Home

The next big thing is Asynchronous Coding Agents. Such Agents change our role as engineers from Conductor (directing one agent at a time) to Orchestrator (defining tasks for a "fleet" of agents working in parallel), for very well-defined tasks with human review. GitHub's Copilot Agent, as covered at #githubuniverse,...

addyosmani's profile picture

Addy Osmani

389,702 subscribers

17,433 views • 8 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!
44:33

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 views • 1 year ago

I am hooked on Dynamic Workflows! The idea of generating harnesses on the fly is so compelling that I reverse-engineered it for my agent orchestrator. And then I built a monitoring dashboard (as an HTML artifact) to track tasks, metrics, and reports. I can now use and monitor dynamic workflows in my agent orchestrator with coding agents like Claude Code, Codex, Pi, and even my own custom-built DAIR.AI agent. This is clearly the future of working with agents to accomplish complex, long-running tasks. Some use cases I'm having success with: - Branching deep research tasks (with verification) - Parallel deep research tasks - Session mining of all my agent sessions - Bug hunting - Triaging - Fact-checking - LLM councils - AI simulations - Data synthesis - Evals generation ... and many others Dynamic workflows, like agent skills, feel like an important primitive to not only get the most out of agents but also incorporate dynamic behaviors and important components like cooperation and verification. There is so much exploration ground here. The exciting part is that this is not limited to coding tasks; it extends to business use cases and many other technical domains like science and research.
0:25

I am hooked on Dynamic Workflows! The idea of generating harnesses on the fly is so compelling that I reverse-engineered it for my agent orchestrator. And then I built a monitoring dashboard (as an HTML artifact) to track tasks, metrics, and reports. I can now use and monitor dynamic workflows in my agent orchestrator with coding agents like Claude Code, Codex, Pi, and even my own custom-built DAIR.AI agent. This is clearly the future of working with agents to accomplish complex, long-running tasks. Some use cases I'm having success with: - Branching deep research tasks (with verification) - Parallel deep research tasks - Session mining of all my agent sessions - Bug hunting - Triaging - Fact-checking - LLM councils - AI simulations - Data synthesis - Evals generation ... and many others Dynamic workflows, like agent skills, feel like an important primitive to not only get the most out of agents but also incorporate dynamic behaviors and important components like cooperation and verification. There is so much exploration ground here. The exciting part is that this is not limited to coding tasks; it extends to business use cases and many other technical domains like science and research.

elvis

102,878 views • 1 month ago

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering
0:56

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

159,179 views • 3 months ago

Bash is all you need! Which is why I'm introducing my holiday project: just-bash just-bash is a pretty complete implementation of bash in TypeScript designed to be used as a bash tool by AI agents. Because it turns out agents love exploring data via shell scripts, even beyond coding. It comes with grep, sed, awk and the 99th percentile features that an agent like Claude Code or Cursor would use. In fact, Claude Code can use it for secure bash execution. In the package - A bash-tool for AI SDK - A binary for use by yourself or your coding agents - An overlay filesystem to feed files to your agent securely - A Vercel Sandbox compatible API, so you can quickly upgrade to a real VM if you need to run binaries - An example AI agent that explores the just-bash code base using just-bash - I imported the Oils shell bash compatibility suite and just-bash passes a very good chunk What is interesting about this codebase: It was essentially entirely written by Opus 4.5. Coding agents love bash and they are good at reproducing it. They are also great at text-book recursive descent parsers and AST tweet-walk interpreters. That said, it is, like, a lot of code and I didn't read it all 😅. This is very much a hack, but it also seems to be _really_ useful. I haven't really found anything agents want to use that it doesn't support and it's fast and secure (caveats apply). It doesn't have write access to your computer and the filesystem is given a root that the agent cannot escape from. Find it at Related: Our recent blog post how we migrated our data analysis agent to bash tools and achieved incredible quality improvements The video shows the example agent investigating the just-bash code base
1:47

Bash is all you need! Which is why I'm introducing my holiday project: just-bash just-bash is a pretty complete implementation of bash in TypeScript designed to be used as a bash tool by AI agents. Because it turns out agents love exploring data via shell scripts, even beyond coding. It comes with grep, sed, awk and the 99th percentile features that an agent like Claude Code or Cursor would use. In fact, Claude Code can use it for secure bash execution. In the package - A bash-tool for AI SDK - A binary for use by yourself or your coding agents - An overlay filesystem to feed files to your agent securely - A Vercel Sandbox compatible API, so you can quickly upgrade to a real VM if you need to run binaries - An example AI agent that explores the just-bash code base using just-bash - I imported the Oils shell bash compatibility suite and just-bash passes a very good chunk What is interesting about this codebase: It was essentially entirely written by Opus 4.5. Coding agents love bash and they are good at reproducing it. They are also great at text-book recursive descent parsers and AST tweet-walk interpreters. That said, it is, like, a lot of code and I didn't read it all 😅. This is very much a hack, but it also seems to be _really_ useful. I haven't really found anything agents want to use that it doesn't support and it's fast and secure (caveats apply). It doesn't have write access to your computer and the filesystem is given a root that the agent cannot escape from. Find it at Related: Our recent blog post how we migrated our data analysis agent to bash tools and achieved incredible quality improvements The video shows the example agent investigating the just-bash code base

Malte Ubl

124,713 views • 6 months ago

How many AI agents work at your company? We now have over 3,258 agents working alongside 1,300 humans. The crazy part is these agents were created by EVERY EMPLOYEE at our company... sales reps, marketers, customer support, product, eng. Literally EVERYONE. BUT I'm most surprised by the adoption and value that MANAGERS are getting from agents. I used to think that every IC would become a manager of agents. Now I think that managers will very likely manage WAY more agents than their ICs combined. And managers' agents will manage their ICs' agents - overseeing them for human-in-the-loop interactions. When creating agents, we use 100% context from all of your activity, files edited, tasks and projects worked on, hierarchy, skills, and role information. We build a user-based context model to make agents as relatable as possible to the specific human that we're building for. This means they truly understand the nuances of the work and what "great" looks like - because great is very much in the eye of the beholder. Great is by definition, subjective. This is also why the human ENGAGEMENT loops are SO vital to agent value. The iteration AFTER the agent is onboarded is where the MAGIC happens. This is just like a manager managing an IC in real life... you're giving feedback. In this case, though, agents learn INSTANTLY, and they retain the knowledge perfectly and indefinitely. Even though I've been pushing AI for years now to everyone in our company, this was the first time we had truly end-to-end AI adoption and retention. This kind of AI adoption is wild. But the value we're realizing is truly INSANE. Super Agents outnumber our humans nearly 3 to 1. What if you could 3X your workforce overnight? Watch this video to see how 👇
0:59

How many AI agents work at your company? We now have over 3,258 agents working alongside 1,300 humans. The crazy part is these agents were created by EVERY EMPLOYEE at our company... sales reps, marketers, customer support, product, eng. Literally EVERYONE. BUT I'm most surprised by the adoption and value that MANAGERS are getting from agents. I used to think that every IC would become a manager of agents. Now I think that managers will very likely manage WAY more agents than their ICs combined. And managers' agents will manage their ICs' agents - overseeing them for human-in-the-loop interactions. When creating agents, we use 100% context from all of your activity, files edited, tasks and projects worked on, hierarchy, skills, and role information. We build a user-based context model to make agents as relatable as possible to the specific human that we're building for. This means they truly understand the nuances of the work and what "great" looks like - because great is very much in the eye of the beholder. Great is by definition, subjective. This is also why the human ENGAGEMENT loops are SO vital to agent value. The iteration AFTER the agent is onboarded is where the MAGIC happens. This is just like a manager managing an IC in real life... you're giving feedback. In this case, though, agents learn INSTANTLY, and they retain the knowledge perfectly and indefinitely. Even though I've been pushing AI for years now to everyone in our company, this was the first time we had truly end-to-end AI adoption and retention. This kind of AI adoption is wild. But the value we're realizing is truly INSANE. Super Agents outnumber our humans nearly 3 to 1. What if you could 3X your workforce overnight? Watch this video to see how 👇

Zeb Evans

425,244 views • 5 months ago

new codex app first impressions! - pros: reliably coding in swift 🤍, a nice UI for kicking off concurrent threads/alerts, clearly there is a lot to unpack across automations/skills - asks: would love to see more killer use cases for automations, perhaps broken down by product type (iOS, web, electron); had some wrangling on chat context & a feature I expected to be more straightforward overall: I am bought in that a clean/beautiful UI for coordinating many agents (some with long running tasks) is powerful; I sense there's a lot more to unlock with time. I still want the ability to quickly switch between codex and claude code, as they seem to excel in different (+ complementary) dev tasks
7:58

new codex app first impressions! - pros: reliably coding in swift 🤍, a nice UI for kicking off concurrent threads/alerts, clearly there is a lot to unpack across automations/skills - asks: would love to see more killer use cases for automations, perhaps broken down by product type (iOS, web, electron); had some wrangling on chat context & a feature I expected to be more straightforward overall: I am bought in that a clean/beautiful UI for coordinating many agents (some with long running tasks) is powerful; I sense there's a lot more to unlock with time. I still want the ability to quickly switch between codex and claude code, as they seem to excel in different (+ complementary) dev tasks

ashe

13,440 views • 5 months ago

Codex team is back in the kitchen with a really nice quality of life upgrade for subagents. With the advent of custom roles, they have also upgraded the TUI experience in two really meaningful ways. > All agents now get a name for better readability > Additionally, the agent role is declared. > Subagent name, role, and status are now color coded. > Subagent rendering was also optimized for readability > /agents slash command shows all agents, even 2+ layers deep. And here's the biggest and most important change. Subagent injection. Before, sometimes the orchestration agent would continue work and lose track of the work of a subagent. Now, when a subagent is blocked or completed, it injects a message back up the chain to ensure that the parent sees the message. This is a really big improvement overall, and leads to much more reliable inter-agent communication, reliability, and DX. In this example, I used the parent agent to spin up a worker agent, which then spawned two more "Spark" agents a second layer deep. I was able to easily tell them apart, switch between the threads, and see exactly what they were prompted. All of this will be available in update 0.105.0 I don't know who JIF is at OpenAI, but they are truly a legend.
0:35

Codex team is back in the kitchen with a really nice quality of life upgrade for subagents. With the advent of custom roles, they have also upgraded the TUI experience in two really meaningful ways. > All agents now get a name for better readability > Additionally, the agent role is declared. > Subagent name, role, and status are now color coded. > Subagent rendering was also optimized for readability > /agents slash command shows all agents, even 2+ layers deep. And here's the biggest and most important change. Subagent injection. Before, sometimes the orchestration agent would continue work and lose track of the work of a subagent. Now, when a subagent is blocked or completed, it injects a message back up the chain to ensure that the parent sees the message. This is a really big improvement overall, and leads to much more reliable inter-agent communication, reliability, and DX. In this example, I used the parent agent to spin up a worker agent, which then spawned two more "Spark" agents a second layer deep. I was able to easily tell them apart, switch between the threads, and see exactly what they were prompted. All of this will be available in update 0.105.0 I don't know who JIF is at OpenAI, but they are truly a legend.

am.will

78,267 views • 4 months ago

✨New demo: what if vibe coding felt more visual? Brian Lovin Mary Rose Cook and I did a game jam using Notion as our "IDE": launching Cursor agents from a task board, and making a custom image for each task 😎 The demo shows 3 ideas for the future of agents: 1) Agents should collaborate across apps. Each app has its focus--Notion AI is good at drafting specs and organizing tasks; Cursor is good at coding. So let them specialize! Today we're launching a new integration where Notion AI can kick off Cursor Cloud Agents to do coding tasks. The Cursor API accepts natural language prompts, so I think of this as "cross-app sub-agents" -- it's kinda cute how it resembles humans hiring outside contractors 😊 BTW: the parallelism of cloud agents is incredibly freeing for creativity, but it also creates a new problem: sooo much work to keep track of! Which brings us to the next idea... 2) Agent orchestration is a data visualization problem. A powerful frame for designing agent UIs is to think of the chat transcripts as the "raw data" and ask: what visual projections might help people make sense of this data at scale? We need to engage our human GPUs -- our visual processing -- to understand what the computer GPUs are doing for us! One thing we can do is use AI to populate traditional UIs like progress bars and status updates. But there are also new possibilities now... For example: when you have a lot going on, it can be hard to identify tasks just by text titles. So we tried generating an AI image for each task -- turns out this helps a lot by giving it a unique visual identity! And of course, it also just makes it super fun to build with friends 😃 Speaking of friends... 3) The future of coding is collaborative. Sometimes it feels like IC engineers are being reduced to middle managers: shuffling information between the team's context and the coding agents that they individually manage. The solution: bring all the people and agents into one shared space, with shared context and visibility! In the video you can get a glimpse of how this feels. Mary, Brian and I record ourselves chatting about ideas, and then we use AI to turn that conversation into a list of tasks on a shared board. As the ideas get built in parallel, we can all monitor progress and review the work together, nothing is siloed. My main takeaway from this game jam was: damn, creativity with friends, at the speed of conversation, is incredibly fun. --- Our goal here is to let anyone use Notion as a fun and creative "software factory" to build software together with your team. Give the Cursor integration a shot and let us know what you think! (AI Image gen in Notion isn't GA yet, but coming soon and already out to some users) And let me know if you'd want a template or more detailed instructions on the setup we showed in this demo...
12:37

✨New demo: what if vibe coding felt more visual? Brian Lovin Mary Rose Cook and I did a game jam using Notion as our "IDE": launching Cursor agents from a task board, and making a custom image for each task 😎 The demo shows 3 ideas for the future of agents: 1) Agents should collaborate across apps. Each app has its focus--Notion AI is good at drafting specs and organizing tasks; Cursor is good at coding. So let them specialize! Today we're launching a new integration where Notion AI can kick off Cursor Cloud Agents to do coding tasks. The Cursor API accepts natural language prompts, so I think of this as "cross-app sub-agents" -- it's kinda cute how it resembles humans hiring outside contractors 😊 BTW: the parallelism of cloud agents is incredibly freeing for creativity, but it also creates a new problem: sooo much work to keep track of! Which brings us to the next idea... 2) Agent orchestration is a data visualization problem. A powerful frame for designing agent UIs is to think of the chat transcripts as the "raw data" and ask: what visual projections might help people make sense of this data at scale? We need to engage our human GPUs -- our visual processing -- to understand what the computer GPUs are doing for us! One thing we can do is use AI to populate traditional UIs like progress bars and status updates. But there are also new possibilities now... For example: when you have a lot going on, it can be hard to identify tasks just by text titles. So we tried generating an AI image for each task -- turns out this helps a lot by giving it a unique visual identity! And of course, it also just makes it super fun to build with friends 😃 Speaking of friends... 3) The future of coding is collaborative. Sometimes it feels like IC engineers are being reduced to middle managers: shuffling information between the team's context and the coding agents that they individually manage. The solution: bring all the people and agents into one shared space, with shared context and visibility! In the video you can get a glimpse of how this feels. Mary, Brian and I record ourselves chatting about ideas, and then we use AI to turn that conversation into a list of tasks on a shared board. As the ideas get built in parallel, we can all monitor progress and review the work together, nothing is siloed. My main takeaway from this game jam was: damn, creativity with friends, at the speed of conversation, is incredibly fun. --- Our goal here is to let anyone use Notion as a fun and creative "software factory" to build software together with your team. Give the Cursor integration a shot and let us know what you think! (AI Image gen in Notion isn't GA yet, but coming soon and already out to some users) And let me know if you'd want a template or more detailed instructions on the setup we showed in this demo...

Geoffrey Litt

88,919 views • 4 months ago

I have built a Windows x64 sampling profiler for native code+C# to be used by coding agents. Why? Because it is irresponsible to let computers write code but give them no tools to evaluate the performance of their code. Stop guessing, start measuring. -> How does it work? Just point your agent to the profiler and let them measure and optimize. Or record a trace yourself and let the agent interpret the results for you. Works with Claude Code, Codex, pi, etc. The profiler also has a couple of neat features by itself like giving you estimates for how much time your code is spending on memory stalls and annotating disassembly with inlining information. Take a look and try it for free!
12:40

I have built a Windows x64 sampling profiler for native code+C# to be used by coding agents. Why? Because it is irresponsible to let computers write code but give them no tools to evaluate the performance of their code. Stop guessing, start measuring. -> How does it work? Just point your agent to the profiler and let them measure and optimize. Or record a trace yourself and let the agent interpret the results for you. Works with Claude Code, Codex, pi, etc. The profiler also has a couple of neat features by itself like giving you estimates for how much time your code is spending on memory stalls and annotating disassembly with inlining information. Take a look and try it for free!

Sebastian Schöner

12,969 views • 2 months ago

a16z a16z speedrun 🧊 request for startups: GUIs for Agents we’re still in the MS-DOS era of agents today - CLI, terminal sessions, file directories deleted by openclaw etc. while a small slice of silicon valley are power users, we're SO early for the rest of the world at Speedrun, we’re looking for bold founders excited to bring the power of agents to normies everywhere. there's a whole slew of products to be built here - from agent builders to marketplaces to managed infrastructure one broad idea we’re excited about are visual abstraction layers for agents. if you don't know exactly what you want, a command line / chat interface is paralyzing - you need to see options 1 example - think of a GUI or visual command center inspired by strategy games (ex. Factorio) where agents and workflows are represented graphically. skills, tools, MCP connections, background processes, etc could all be configured and shown visually in a workspace on UX, strategy games have long perfected agent management. zoom to get a birds-eye view of your agents, batch and queue orders via shortcuts, assign agents in multiplayer etc. a well-designed agent command center would make multi-agent orchestration for normies feel easy & intuitive most folks today still haven't moved beyond ChatGPT. the potential is enormous - just as Windows unlocked mass-market use of personal computers, the right visual abstraction layer could unlock agentic work for everyone - from individuals to enterprise teams if you share our vision, we'd love to chat!
1:41

a16z a16z speedrun 🧊 request for startups: GUIs for Agents we’re still in the MS-DOS era of agents today - CLI, terminal sessions, file directories deleted by openclaw etc. while a small slice of silicon valley are power users, we're SO early for the rest of the world at Speedrun, we’re looking for bold founders excited to bring the power of agents to normies everywhere. there's a whole slew of products to be built here - from agent builders to marketplaces to managed infrastructure one broad idea we’re excited about are visual abstraction layers for agents. if you don't know exactly what you want, a command line / chat interface is paralyzing - you need to see options 1 example - think of a GUI or visual command center inspired by strategy games (ex. Factorio) where agents and workflows are represented graphically. skills, tools, MCP connections, background processes, etc could all be configured and shown visually in a workspace on UX, strategy games have long perfected agent management. zoom to get a birds-eye view of your agents, batch and queue orders via shortcuts, assign agents in multiplayer etc. a well-designed agent command center would make multi-agent orchestration for normies feel easy & intuitive most folks today still haven't moved beyond ChatGPT. the potential is enormous - just as Windows unlocked mass-market use of personal computers, the right visual abstraction layer could unlock agentic work for everyone - from individuals to enterprise teams if you share our vision, we'd love to chat!

Jon Lai

198,846 views • 2 months ago

I've been building a "front page" for Toad (my terminal UI for agentic coding). This will the first page the user will see if they run "toad" from the command line without additional arguments. For here they can browse / search for agents and install directly from the command line. There are 10 agent supported so far, with more being added all the time. I also see this is a place to install other more specialized AI tools in addition to agentic coding. Check out the video! #toad #AI
1:24

I've been building a "front page" for Toad (my terminal UI for agentic coding). This will the first page the user will see if they run "toad" from the command line without additional arguments. For here they can browse / search for agents and install directly from the command line. There are 10 agent supported so far, with more being added all the time. I also see this is a place to install other more specialized AI tools in addition to agentic coding. Check out the video! #toad #AI

Will McGugan

35,626 views • 8 months ago

$SERV is the Fiverr/Shopify for AI agents. OpenServ provides a platform and marketplace to create, find, and employ AI agents. Here's why it can be a leading Agent marketplace and is undervalued compared to where it can go. ———————————————————— To put this in perspective, we will take this from the top down. Let's look at the valuation mismatch. → Shopify: $140B → Fiverr: $1.2B → $SERV: $37M AI agent platforms can completely replace these businesses. Why? → Can automate operations (i.e. store setup, inventory management, and customer support autonomously, etc.) → Agents can hyper-personalize the shopping experience → Store owners can own their data and have more control → Marketplaces are a cheaper/faster solution AI agents make things more convenient by performing tasks autonomously. They are inevitable. ———————————————————— The AI Agent market is projected to reach ~$50B by 2030. So the potential is MASSIVE. What makes me so bullish on $SERV specifically? There are 3 things: 1️⃣ The Tech They are targeting Web 2 businesses. This gives the platform the most upside potential imo, both in terms of adoption and valuation. These are some noteworthy highlights: → No-code AI Agent builder (anyone can build) → Builders can generate income using agents → ANY agent can cooperate with ANY agent through SERVs platform → Offers multi-agent collaboration, while allowing for human input/customization This sets them apart from other crypto-centric AI agent marketplaces. OpenServ allows you to create a team of agents to carry out complex tasks, all while automating the process and packaging their solution for Web 2 businesses. Simple tool, easy execution, and limitless productivity. Which business/individual wouldn't want to do MORE in LESS time at a rate MUCH LESS than solutions already available? ———————————————————— 2️⃣ The Team They have a stacked team. → Founders: Experience in businesses & startups → CTO: 20+ years of experience in ML/AI → CFO: ex-JP Morgan VP → CMO: ex-IBM AI & Blockchain Marketing Director Within the last few weeks/months, they have added a UI/UX designer, 4 more devs, and more devs + a product manager coming. You could have the best tech but the team is what determines its success. In this case, the team has the knowledge/experience to see this through. They have been building for a year and the progress made is a good sign of what's to come. ———————————————————— 3️⃣ The Tokenomics A percentage of transaction volume on the platform will be used to buy back and burn the $SERV token. This creates and maintains buy-side pressure and demand. To put that in perspective, Fiverr & Upwork had a combined transaction volume of $5B. The demand for Agents wont slow down anytime soon. Demand for AI agents will translate into demand for the token. I love deflation. It's simple, clean, and effective. ———————————————————— ➡️ Final Thoughts I've held on tight to my $SERV bag because the platform is launching in Q1. This will mark the beginning of their journey to the top. Agents are inevitable. Integration with Web 2 businesses is inevitable. And the platform launch is coming as alt szn is kicking off. The stars are aligning. At the same time, AI companies are already showing interest in the platform. Developers lead to more users, bringing monetization opportunities, which brings more developers, and so on. A powerfully designed flywheel. This is a new and exciting sector. I expect interest and liquidity to be focused on AI Agents and the infrastructure around them. Max opportunity is right here in this sector.
2:59

$SERV is the Fiverr/Shopify for AI agents. OpenServ provides a platform and marketplace to create, find, and employ AI agents. Here's why it can be a leading Agent marketplace and is undervalued compared to where it can go. ———————————————————— To put this in perspective, we will take this from the top down. Let's look at the valuation mismatch. → Shopify: $140B → Fiverr: $1.2B → $SERV: $37M AI agent platforms can completely replace these businesses. Why? → Can automate operations (i.e. store setup, inventory management, and customer support autonomously, etc.) → Agents can hyper-personalize the shopping experience → Store owners can own their data and have more control → Marketplaces are a cheaper/faster solution AI agents make things more convenient by performing tasks autonomously. They are inevitable. ———————————————————— The AI Agent market is projected to reach ~$50B by 2030. So the potential is MASSIVE. What makes me so bullish on $SERV specifically? There are 3 things: 1️⃣ The Tech They are targeting Web 2 businesses. This gives the platform the most upside potential imo, both in terms of adoption and valuation. These are some noteworthy highlights: → No-code AI Agent builder (anyone can build) → Builders can generate income using agents → ANY agent can cooperate with ANY agent through SERVs platform → Offers multi-agent collaboration, while allowing for human input/customization This sets them apart from other crypto-centric AI agent marketplaces. OpenServ allows you to create a team of agents to carry out complex tasks, all while automating the process and packaging their solution for Web 2 businesses. Simple tool, easy execution, and limitless productivity. Which business/individual wouldn't want to do MORE in LESS time at a rate MUCH LESS than solutions already available? ———————————————————— 2️⃣ The Team They have a stacked team. → Founders: Experience in businesses & startups → CTO: 20+ years of experience in ML/AI → CFO: ex-JP Morgan VP → CMO: ex-IBM AI & Blockchain Marketing Director Within the last few weeks/months, they have added a UI/UX designer, 4 more devs, and more devs + a product manager coming. You could have the best tech but the team is what determines its success. In this case, the team has the knowledge/experience to see this through. They have been building for a year and the progress made is a good sign of what's to come. ———————————————————— 3️⃣ The Tokenomics A percentage of transaction volume on the platform will be used to buy back and burn the $SERV token. This creates and maintains buy-side pressure and demand. To put that in perspective, Fiverr & Upwork had a combined transaction volume of $5B. The demand for Agents wont slow down anytime soon. Demand for AI agents will translate into demand for the token. I love deflation. It's simple, clean, and effective. ———————————————————— ➡️ Final Thoughts I've held on tight to my $SERV bag because the platform is launching in Q1. This will mark the beginning of their journey to the top. Agents are inevitable. Integration with Web 2 businesses is inevitable. And the platform launch is coming as alt szn is kicking off. The stars are aligning. At the same time, AI companies are already showing interest in the platform. Developers lead to more users, bringing monetization opportunities, which brings more developers, and so on. A powerfully designed flywheel. This is a new and exciting sector. I expect interest and liquidity to be focused on AI Agents and the infrastructure around them. Max opportunity is right here in this sector.

Chill

34,174 views • 1 year ago

The #1 problem with coding agents right now: Ask them to solve one problem, and they will make 10 other changes you didn't want. This happens to me every day. It happens to everyone I talk to as well. We have a solution for this now. The team Augment Code released a "Task List" feature for their coding assistant that solves this problem. Augment Code is partnering with me on this post. In case you haven't used them before: • Augment Code is a fully-fledged coding assistant • Their specialty are large projects • Fastest coding indexing I've seen • Has a free forever community edition Now, you can ask their coding agent to generate a Task List before doing anything. This will give you a plan you can review, edit, and augment if you need to. You can export this plan, load it on a different session, or even share it across projects. It makes a huge difference: The task list constrains the agent so you won't get any "unintended" changes anymore. It also puts you in control of everything the agent does. Check the video to see the agent working through a task list. You can also try this 100% free: (By the way, they also have support for remote agents. You can basically have those agents write your code while you are sleeping.)
3:06

The #1 problem with coding agents right now: Ask them to solve one problem, and they will make 10 other changes you didn't want. This happens to me every day. It happens to everyone I talk to as well. We have a solution for this now. The team Augment Code released a "Task List" feature for their coding assistant that solves this problem. Augment Code is partnering with me on this post. In case you haven't used them before: • Augment Code is a fully-fledged coding assistant • Their specialty are large projects • Fastest coding indexing I've seen • Has a free forever community edition Now, you can ask their coding agent to generate a Task List before doing anything. This will give you a plan you can review, edit, and augment if you need to. You can export this plan, load it on a different session, or even share it across projects. It makes a huge difference: The task list constrains the agent so you won't get any "unintended" changes anymore. It also puts you in control of everything the agent does. Check the video to see the agent working through a task list. You can also try this 100% free: (By the way, they also have support for remote agents. You can basically have those agents write your code while you are sleeping.)

Santiago

41,738 views • 11 months ago

Just gave a demo at Every 📧's Vibe Code Camp showing how I use a kanban board to stay sane while overseeing Claude Code agents😎 Here's a quick recap video showing the whole flow: 1) Monitor progress on all tasks in one view 2) See when Claude is blocked, and respond in context 3) Read Claude's plans with nice formatting, not raw Markdown 4) Use AI to process voice notes into structured tasks 5) Get explanations of code changes... with an interactive quiz to check if you understood 🙃 I've had mixed feelings about kanban workflows in the past, but as the agents get stronger I'm warming up to them—especially for churning through small well-specified tasks. In that context, it feels like the challenge is managing my working memory for what's going on. And having a stable "zoomed-out map" of all the tasks really helps me with offloading some of that cognitive load to a visualization of everything that's going on!
7:47

Just gave a demo at Every 📧's Vibe Code Camp showing how I use a kanban board to stay sane while overseeing Claude Code agents😎 Here's a quick recap video showing the whole flow: 1) Monitor progress on all tasks in one view 2) See when Claude is blocked, and respond in context 3) Read Claude's plans with nice formatting, not raw Markdown 4) Use AI to process voice notes into structured tasks 5) Get explanations of code changes... with an interactive quiz to check if you understood 🙃 I've had mixed feelings about kanban workflows in the past, but as the agents get stronger I'm warming up to them—especially for churning through small well-specified tasks. In that context, it feels like the challenge is managing my working memory for what's going on. And having a stable "zoomed-out map" of all the tasks really helps me with offloading some of that cognitive load to a visualization of everything that's going on!

Geoffrey Litt

78,178 views • 5 months ago

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11
43:20

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

Dan Shipper 📧

66,339 views • 2 months ago

The future of design is… engineering. All designers at Vercel now also build, thanks to tools like v0, Claude Code, and Cursor. They've been contributing to our frontends and apps for a while now. But over the past few months, the leap they've made is engineering the design process itself by building agents. A big part of shipping is getting the word out in a compelling way, especially on the X platform, the everything app. In the past, we used to spend a bunch of time hand-crafting images and illustrations for social cards. Our design team built an internal agent and web ui using v0 and Claude Code that makes this process fully self-serve. It even includes a previewer of what the final artifact will look like on X. It's called Leap. It's probably saved us hundreds of hours of work but also massively raised our quality bar. The artifacts it produces are beautiful. If you had asked me even 12 months ago whether our design team would be building their own design tools, let alone be this good, I would call bs. There was no master plan, or God forbid, a "sprint" to make this happen. It just took a handful of prompts to build and it propagated on Slack. Leap is now one of the many agents that helps us run our company more smoothly, built and securely deployed on Vercel for our internal use.
1:08

The future of design is… engineering. All designers at Vercel now also build, thanks to tools like v0, Claude Code, and Cursor. They've been contributing to our frontends and apps for a while now. But over the past few months, the leap they've made is engineering the design process itself by building agents. A big part of shipping is getting the word out in a compelling way, especially on the X platform, the everything app. In the past, we used to spend a bunch of time hand-crafting images and illustrations for social cards. Our design team built an internal agent and web ui using v0 and Claude Code that makes this process fully self-serve. It even includes a previewer of what the final artifact will look like on X. It's called Leap. It's probably saved us hundreds of hours of work but also massively raised our quality bar. The artifacts it produces are beautiful. If you had asked me even 12 months ago whether our design team would be building their own design tools, let alone be this good, I would call bs. There was no master plan, or God forbid, a "sprint" to make this happen. It just took a handful of prompts to build and it propagated on Slack. Leap is now one of the many agents that helps us run our company more smoothly, built and securely deployed on Vercel for our internal use.

Guillermo Rauch

208,229 views • 4 months ago

Today we’re launching the first and only human-like AI agents in the world. Super Agents™ are the first agents with human‑level skills – they DM you, take @ mentions, send emails, manage docs, tasks, and more. Not just tools or API calls, but real skills fine‑tuned for how teams actually work. The first agents with 100% context – fully native in ClickUp and fully synced from other apps. Super Agents see your work the same way that humans do: tasks, docs, schedules, and conversations all in one place. The first agents that learn from human interactions automatically, without any setup or configuration – when you give feedback, they listen and improve how they work. The first agents with human‑level memory for custom agents – historical memory for every interaction, short-term working memory, and even long‑term memory stored in docs you can literally open, inspect, and edit. The first agents that are literally the same as users – our agentic user model is the same as our user data model. This gives you permissions and capabilities that you and your systems are already familiar with. The first infinite agent catalog – where anyone can create and customize agents in minutes, for literally any type of work imaginable. It's the most intuitive way to build agents on the planet. 95% of companies are failing in AI adoption. The reality is that AI isn't meant to be adopted, it's meant to be adapted – to you. Super Agents are automatically personalized to you and your company using proprietary state-of-the-art agent architecture, orchestration, and tooling. Today is the largest step forward we've ever made towards our mission of making people more productive. Maximize human productivity, with ClickUp Super Agents. Available NOW. For everyone.
5:50

Today we’re launching the first and only human-like AI agents in the world. Super Agents™ are the first agents with human‑level skills – they DM you, take @ mentions, send emails, manage docs, tasks, and more. Not just tools or API calls, but real skills fine‑tuned for how teams actually work. The first agents with 100% context – fully native in ClickUp and fully synced from other apps. Super Agents see your work the same way that humans do: tasks, docs, schedules, and conversations all in one place. The first agents that learn from human interactions automatically, without any setup or configuration – when you give feedback, they listen and improve how they work. The first agents with human‑level memory for custom agents – historical memory for every interaction, short-term working memory, and even long‑term memory stored in docs you can literally open, inspect, and edit. The first agents that are literally the same as users – our agentic user model is the same as our user data model. This gives you permissions and capabilities that you and your systems are already familiar with. The first infinite agent catalog – where anyone can create and customize agents in minutes, for literally any type of work imaginable. It's the most intuitive way to build agents on the planet. 95% of companies are failing in AI adoption. The reality is that AI isn't meant to be adopted, it's meant to be adapted – to you. Super Agents are automatically personalized to you and your company using proprietary state-of-the-art agent architecture, orchestration, and tooling. Today is the largest step forward we've ever made towards our mission of making people more productive. Maximize human productivity, with ClickUp Super Agents. Available NOW. For everyone.

Zeb Evans

320,554 views • 6 months ago

An engineer at Anthropic wrote a spec, pointed Claude at an Asana board, and went home. Claude broke the spec into tickets, spawned agents for each one, and they started building independently. When the agent is confused it runs git-blame and messages the right engineers in Slack. By Monday the agents finished the plugin feature. That's one example of how the best engineers are shipping software right now. Developers will soon orchestrate 50 AI agents in parallel and the difference between a good engineer & a great one would come down to specs. You can't write a spec that holds up at that scale without genuinely understanding what you're building at a deeper level. The next-gen developer who understands the fundamentals, can architect well and orchestrate agent is going to be a 1000x developer!
1:08

An engineer at Anthropic wrote a spec, pointed Claude at an Asana board, and went home. Claude broke the spec into tickets, spawned agents for each one, and they started building independently. When the agent is confused it runs git-blame and messages the right engineers in Slack. By Monday the agents finished the plugin feature. That's one example of how the best engineers are shipping software right now. Developers will soon orchestrate 50 AI agents in parallel and the difference between a good engineer & a great one would come down to specs. You can't write a spec that holds up at that scale without genuinely understanding what you're building at a deeper level. The next-gen developer who understands the fundamentals, can architect well and orchestrate agent is going to be a 1000x developer!

rvivek

1,242,307 views • 4 months ago

I built an AI Factory that uses Claude Code agents to build apps while I sleep. This is an automated "assembly line" pipeline, all run by Claude Opus 4.5. Projects move through a Kanban-like system from Idea to Research, Architecture, Coding and Testing. Factory workers start with market research, searching the web and social media. Then they validate everything, checking app stores for competition and securing a domain name. (All automated by APIs and MCPs) They automatically create several rounds of app UI revisions. When I wake up, there are projects waiting for me to review: approve this design, give feedback, send that one back for improvement. Projects are actively coded and tested by the agents, while the entire process is tracked and logged (with "worker documents" that travel each step of the way, like a real factory.)
0:30

I built an AI Factory that uses Claude Code agents to build apps while I sleep. This is an automated "assembly line" pipeline, all run by Claude Opus 4.5. Projects move through a Kanban-like system from Idea to Research, Architecture, Coding and Testing. Factory workers start with market research, searching the web and social media. Then they validate everything, checking app stores for competition and securing a domain name. (All automated by APIs and MCPs) They automatically create several rounds of app UI revisions. When I wake up, there are projects waiting for me to review: approve this design, give feedback, send that one back for improvement. Projects are actively coded and tested by the agents, while the entire process is tracked and logged (with "worker documents" that travel each step of the way, like a real factory.)

Benjamin De Kraker

480,607 views • 6 months ago

This Chinese developer runs 9 agents on Claude Code under a GPT-5.5 orchestrator and they close 500 client tasks a month without a single assistant. His client work is closed without him, on a single laptop and only three subscriptions. The entire system lives on one MacBook Pro M4 with 128 GB of memory and subscriptions to Claude Code and GPT-5.5 cost him approximately $300 a month. There is no CRM, no team, no office only a terminal window with 9 parallel streams. The orchestrator works with a simple system prompt: «You are the orchestrator of a client inbox. Classify every incoming email into 4 categories: code, content, analysis, communication. Delegate to the corresponding worker agent. When the result is ready, check it for completeness, send it to the client on my behalf, and mark the task as closed. Do not ask clarifying questions.» And the orchestrator checks the inbox every 30 seconds, classifies fresh emails, and distributes them to 9 worker agents on Claude Code, each of whom is responsible for their own class of tasks. Here is an example of how one of them closes a request to refactor a client's auth module: Task: refactor user-auth module Broke the monolith into 3 files by responsibilities Added unit tests, coverage increased to 87% Renamed 4 functions to camelCase according to the style guide PR is ready for review, link below» And so about 50 cycles a day. By noon 25 tasks are closed, by dinner 50, and by the end of the month 500. On average, it takes about 7 minutes from the appearance of an email in the inbox to sending the result to the client. This is more than what a live team of 6 developers, copywriters and analysts working 8 hours a day closes. This is no longer an agency. This is a workstation where an orchestrator replaces a manager, and 9 worker agents replace the staff. The pipeline goes from inbox to closing 500 times a month without human participation at any step.
1:32

This Chinese developer runs 9 agents on Claude Code under a GPT-5.5 orchestrator and they close 500 client tasks a month without a single assistant. His client work is closed without him, on a single laptop and only three subscriptions. The entire system lives on one MacBook Pro M4 with 128 GB of memory and subscriptions to Claude Code and GPT-5.5 cost him approximately $300 a month. There is no CRM, no team, no office only a terminal window with 9 parallel streams. The orchestrator works with a simple system prompt: «You are the orchestrator of a client inbox. Classify every incoming email into 4 categories: code, content, analysis, communication. Delegate to the corresponding worker agent. When the result is ready, check it for completeness, send it to the client on my behalf, and mark the task as closed. Do not ask clarifying questions.» And the orchestrator checks the inbox every 30 seconds, classifies fresh emails, and distributes them to 9 worker agents on Claude Code, each of whom is responsible for their own class of tasks. Here is an example of how one of them closes a request to refactor a client's auth module: Task: refactor user-auth module Broke the monolith into 3 files by responsibilities Added unit tests, coverage increased to 87% Renamed 4 functions to camelCase according to the style guide PR is ready for review, link below» And so about 50 cycles a day. By noon 25 tasks are closed, by dinner 50, and by the end of the month 500. On average, it takes about 7 minutes from the appearance of an email in the inbox to sending the result to the client. This is more than what a live team of 6 developers, copywriters and analysts working 8 hours a day closes. This is no longer an agency. This is a workstation where an orchestrator replaces a manager, and 9 worker agents replace the staff. The pipeline goes from inbox to closing 500 times a month without human participation at any step.

Blaze

29,917 views • 2 months ago