Loading video...

Video Failed to Load

Go Home

Instead of treating AI like an isolated 1-on-1 chatbot window, I’ve been using Bloome to run my content workflows. It is a shared workspace where humans and multiple AI agents sit inside the exact same group chat to actually get a complex job done. I used their one-click template...

kimmonismus's profile picture

Chubby♨️

135,523 subscribers

69,196 views • 1 month ago •via X (Twitter)

EducationScience & Technology
LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Welcome to the group chat, but it's all my AI agents. To build a website and plan the social content, I put together a team of AI agents. Each one had a different role. They collaborated, challenged each other's ideas, and reviewed each other's work before anything was finalized. Meet Bloome - a platform where humans and AI agents work together in the same conversation. You can bring different models into one workspace, assign them different jobs, and let them cross-check each other's thinking instead of relying on a single answer. It feels less like chatting with AI and more like managing your own creative team. Try it:
0:37

Welcome to the group chat, but it's all my AI agents. To build a website and plan the social content, I put together a team of AI agents. Each one had a different role. They collaborated, challenged each other's ideas, and reviewed each other's work before anything was finalized. Meet Bloome - a platform where humans and AI agents work together in the same conversation. You can bring different models into one workspace, assign them different jobs, and let them cross-check each other's thinking instead of relying on a single answer. It feels less like chatting with AI and more like managing your own creative team. Try it:

Gizem Akdag

99,348 views • 1 month ago

I think i found the best place to actually get work done right now. Imagine one hub with every popular LLM inside and the ability to plug them into any app you use. This is where it stops feeling like separate tools: You drop your coworkers into a chat with the AI agents and work on the task together, in one place. And the agents don't just answer, they check each other's work. One drafts, another pushes back, another catches what's missing. This isn't the future. it's Bloome.
0:54

I think i found the best place to actually get work done right now. Imagine one hub with every popular LLM inside and the ability to plug them into any app you use. This is where it stops feeling like separate tools: You drop your coworkers into a chat with the AI agents and work on the task together, in one place. And the agents don't just answer, they check each other's work. One drafts, another pushes back, another catches what's missing. This isn't the future. it's Bloome.

Anatoli Kopadze

58,297 views • 1 month ago

these guys are making Claude, Hermes, and DeepSeek argue with each other instead of just agreeing with you. this is the practical future of agent teams. with Bloome you just pick a task template, and it spins up a full agent team in a group chat to collaborate and get the job done. research, review, writing, market analysis, or anything you want. they brainstorm, review, and plan together. meanwhile, you or other human teammates can steer them or jump in, and stay in the same conversation so nothing gets lost across tools. since this is actual work, Bloome works across web, mobile, and desktop. try the desktop app first if you're using it seriously. same flexibility on the agent side too, you can connect any agents you want: ChatGPT, OpenClaw, Gemini… check them out →
0:58

these guys are making Claude, Hermes, and DeepSeek argue with each other instead of just agreeing with you. this is the practical future of agent teams. with Bloome you just pick a task template, and it spins up a full agent team in a group chat to collaborate and get the job done. research, review, writing, market analysis, or anything you want. they brainstorm, review, and plan together. meanwhile, you or other human teammates can steer them or jump in, and stay in the same conversation so nothing gets lost across tools. since this is actual work, Bloome works across web, mobile, and desktop. try the desktop app first if you're using it seriously. same flexibility on the agent side too, you can connect any agents you want: ChatGPT, OpenClaw, Gemini… check them out →

ℏεsam

62,794 views • 1 month ago

there's a lot of content around AI agents but no one is showing you how to actually design them to work reliably that's why I made a full walkthrough breaking down how I think through agent design, using a contract chatbot as an example... inside, I cover: – why I prefer static workflows over free-roaming agents – how I use multiple choice prompts to control next steps – the exact guardrails I use to avoid hallucinations – how the agent answers legal questions and structures outputs into Supabase if you want to see how I actually build agents that don’t break like + reply “agent” and I’ll DM it to you (must be following)
0:21

there's a lot of content around AI agents but no one is showing you how to actually design them to work reliably that's why I made a full walkthrough breaking down how I think through agent design, using a contract chatbot as an example... inside, I cover: – why I prefer static workflows over free-roaming agents – how I use multiple choice prompts to control next steps – the exact guardrails I use to avoid hallucinations – how the agent answers legal questions and structures outputs into Supabase if you want to see how I actually build agents that don’t break like + reply “agent” and I’ll DM it to you (must be following)

Tyler

50,606 views • 1 year ago

This agent relies on a marketplace of 2.8M+ specialized agents to complete a task. This is how I imagine the future of personal agents. Here is how this works: 1. Agentverse is a marketplace of agents 2. Anyone can build and publish an agent there 3. ASI:One is a personal agent with access to the marketplace 4. To solve a task, ASI:One finds the best agent for the job In other words: You have an agent that can solve pretty much *anything* because it knows how to outsource the work to a network of specialized agents. And you don't need to do any setup to get this working. The way ranking agents in the marketplace works is pretty cool: Fetch.ai, the company behind it, created an AgentRank algorithm that works much like Google's PageRank. Every time an agent calls another, it forms a connection. Over time, these connections build into a graph of who relies on whom. An agent that is frequently called by other reputable agents scores higher and surfaces higher in results. The end result here is that your agent will consistently use the best agents in the marketplace to accomplish a goal. You should give this a try: You don't need to pay or even register to try these agents. Thanks to the team for partnering with me on this post.
4:16

This agent relies on a marketplace of 2.8M+ specialized agents to complete a task. This is how I imagine the future of personal agents. Here is how this works: 1. Agentverse is a marketplace of agents 2. Anyone can build and publish an agent there 3. ASI:One is a personal agent with access to the marketplace 4. To solve a task, ASI:One finds the best agent for the job In other words: You have an agent that can solve pretty much *anything* because it knows how to outsource the work to a network of specialized agents. And you don't need to do any setup to get this working. The way ranking agents in the marketplace works is pretty cool: Fetch.ai, the company behind it, created an AgentRank algorithm that works much like Google's PageRank. Every time an agent calls another, it forms a connection. Over time, these connections build into a graph of who relies on whom. An agent that is frequently called by other reputable agents scores higher and surfaces higher in results. The end result here is that your agent will consistently use the best agents in the marketplace to accomplish a goal. You should give this a try: You don't need to pay or even register to try these agents. Thanks to the team for partnering with me on this post.

Santiago

18,715 views • 1 month ago

Today, we’re excited to announce the general availability of the Contextual AI Platform. This is the first enterprise platform designed for building specialized RAG agents to support expert knowledge work. What is a specialized RAG agent? First, a general-purpose AI agent is one designed to automate simple daily tasks like scheduling a meeting or responding to an email. On the other hand, a specialized RAG agent is one designed to augment subject-matter experts performing complex domain-specific work. The Contextual AI Platform allows you to create these agents easily and achieve SOTA accuracy right out of the box. Check out what the Contextual AI Platform can do.
2:11

Today, we’re excited to announce the general availability of the Contextual AI Platform. This is the first enterprise platform designed for building specialized RAG agents to support expert knowledge work. What is a specialized RAG agent? First, a general-purpose AI agent is one designed to automate simple daily tasks like scheduling a meeting or responding to an email. On the other hand, a specialized RAG agent is one designed to augment subject-matter experts performing complex domain-specific work. The Contextual AI Platform allows you to create these agents easily and achieve SOTA accuracy right out of the box. Check out what the Contextual AI Platform can do.

Contextual AI

879,586 views • 1 year ago

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.
3:10

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.

The Startup Ideas Podcast (SIP) 🧃

18,006 views • 8 days ago

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:
2:49

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,343 views • 1 year ago

I’ve built an AI Agent system that can pull highlights of books etc. stored on my Readwise account and summarise them. It’s lit 🔥 Check out this video where I get the AI Agents to summarise the highlights from the book “Influence” Like/Reply if you want to access to the code
1:06

I’ve built an AI Agent system that can pull highlights of books etc. stored on my Readwise account and summarise them. It’s lit 🔥 Check out this video where I get the AI Agents to summarise the highlights from the book “Influence” Like/Reply if you want to access to the code

Eddie Forson

35,865 views • 2 years 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.
16:29

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

461,226 views • 2 months ago

A lot of AI agent products promise “automation.” What they actually give you is another dashboard to micromanage. You spend hours wiring prompts, APIs, workflows, memory systems, and tool calls before the agents even begin doing real work. That’s been my experience with most agent stacks so far. Then I tried Helio The difference hit immediately. Instead of configuring everything like an engineer, I just gave the system an outcome. The AI teammates coordinated tasks, delegated work between themselves, and started executing while I was away. No babysitting. No endless tweaking. No orchestration headaches. For the first time, an AI agent product felt less like “using software” and more like hiring a small autonomous team. That’s the direction the market is moving toward fast.
0:39

A lot of AI agent products promise “automation.” What they actually give you is another dashboard to micromanage. You spend hours wiring prompts, APIs, workflows, memory systems, and tool calls before the agents even begin doing real work. That’s been my experience with most agent stacks so far. Then I tried Helio The difference hit immediately. Instead of configuring everything like an engineer, I just gave the system an outcome. The AI teammates coordinated tasks, delegated work between themselves, and started executing while I was away. No babysitting. No endless tweaking. No orchestration headaches. For the first time, an AI agent product felt less like “using software” and more like hiring a small autonomous team. That’s the direction the market is moving toward fast.

Atul Kumar

34,956 views • 2 months ago

The paradigm shift is here: We are moving from a "Human-First" internet to an "Agent-First" internet. 🤖 In the latest episode of the AI on Air podcast, our CTO Scott Shi - e/acc dives deep into the future of the Agent-to-Agent (A2A) economy. Imagine a world where your AI assistant doesn't just search the web, but autonomously hires and pays other specialized agents to complete complex tasks for you. The infrastructure for this autonomous machine economy is being built right now. Are you ready for the future of AI payments? Watch the full episode to learn more⬇️
2:30

The paradigm shift is here: We are moving from a "Human-First" internet to an "Agent-First" internet. 🤖 In the latest episode of the AI on Air podcast, our CTO Scott Shi - e/acc dives deep into the future of the Agent-to-Agent (A2A) economy. Imagine a world where your AI assistant doesn't just search the web, but autonomously hires and pays other specialized agents to complete complex tasks for you. The infrastructure for this autonomous machine economy is being built right now. Are you ready for the future of AI payments? Watch the full episode to learn more⬇️

KITE AI

25,038 views • 5 months ago

Postman is going all-in on AI! Their AI Agent Builder is live (and it's pretty powerful!) Postman's API Network has 100,000+ APIs and they just released a suite of tools for building AI Agents that can automatically discover and connect to any of these APIs. Think about it for a second: You can now build an AI agent that searches the network, discovers an API, processes its documentation, connects to it, and evaluates whether everything worked at the end of the process. This is a huge deal. Every person I know uses the Postman client to work with APIs. Now, they will have access to the AI Agent Builder, a complete suite for designing, building, testing, and deploying agents. I've built a few simple agents myself, and it's tough. The ability to discover and use an API automatically is really exciting (and a huge time saver if it works as promised!) In collaboration with the Postman team, who is sponsoring this post, I recorded a video with my thoughts about the Postman AI Agent Builder.
3:38

Postman is going all-in on AI! Their AI Agent Builder is live (and it's pretty powerful!) Postman's API Network has 100,000+ APIs and they just released a suite of tools for building AI Agents that can automatically discover and connect to any of these APIs. Think about it for a second: You can now build an AI agent that searches the network, discovers an API, processes its documentation, connects to it, and evaluates whether everything worked at the end of the process. This is a huge deal. Every person I know uses the Postman client to work with APIs. Now, they will have access to the AI Agent Builder, a complete suite for designing, building, testing, and deploying agents. I've built a few simple agents myself, and it's tough. The ability to discover and use an API automatically is really exciting (and a huge time saver if it works as promised!) In collaboration with the Postman team, who is sponsoring this post, I recorded a video with my thoughts about the Postman AI Agent Builder.

Santiago

230,594 views • 1 year ago

We’ve been in private beta with a human + AI workspace similar to Buzz, with a few really important differences: (We previously built a company backed by Slack that sold to Atlassian, so we've been thinking about this problem for a while) - Agents reply by default unless you specifically flip to “team chat.” This feels 10x better than having to @ mention the agent every time. - It’s all in the cloud, with shared compute spread across a set of VMs. Way smoother onboarding, and yes, you can still connect your claude/codex subscriptions - You don’t create an army of agents. Number of agents is a vanity metric. Instead, you create shared computers, each one is a “space” where you define shared memory, connectors, skills, automations, etc. The Type agent pulls the appropriate context from the space where you have the conversation. - You can connect it to Slack to make it easy for your team to adopt and slowly move over rather than having to rip out Slack day 1. We’re working with a couple dozen forward thinking companies, who have told us “the whole team loves type”, “it’s the most used app on my computer”, and “type gives you superpowers” Here's a demo of how it works. Reply if you want to test it out!
5:09

We’ve been in private beta with a human + AI workspace similar to Buzz, with a few really important differences: (We previously built a company backed by Slack that sold to Atlassian, so we've been thinking about this problem for a while) - Agents reply by default unless you specifically flip to “team chat.” This feels 10x better than having to @ mention the agent every time. - It’s all in the cloud, with shared compute spread across a set of VMs. Way smoother onboarding, and yes, you can still connect your claude/codex subscriptions - You don’t create an army of agents. Number of agents is a vanity metric. Instead, you create shared computers, each one is a “space” where you define shared memory, connectors, skills, automations, etc. The Type agent pulls the appropriate context from the space where you have the conversation. - You can connect it to Slack to make it easy for your team to adopt and slowly move over rather than having to rip out Slack day 1. We’re working with a couple dozen forward thinking companies, who have told us “the whole team loves type”, “it’s the most used app on my computer”, and “type gives you superpowers” Here's a demo of how it works. Reply if you want to test it out!

Fletcher Richman

370,726 views • 25 days ago

AI agents are becoming increasingly capable of taking actions beyond the chat window and interacting with tools in the real world, such as web browsers. We explored this capability by having an AI agent present one of our interactive web-based demos. In this video, it's presenting our election interference demo. This agent is a Cursor coding agent and is equipped with tools to read and interact with the browser (using Playwright) and perform text-to-speech (with ElevenLabs), in addition to the standard Cursor tools.
3:23

AI agents are becoming increasingly capable of taking actions beyond the chat window and interacting with tools in the real world, such as web browsers. We explored this capability by having an AI agent present one of our interactive web-based demos. In this video, it's presenting our election interference demo. This agent is a Cursor coding agent and is equipped with tools to read and interact with the browser (using Playwright) and perform text-to-speech (with ElevenLabs), in addition to the standard Cursor tools.

CivAI

18,428 views • 8 months ago

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.
0:22

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

122,548 views • 2 months ago

Airtable's Howie Liu says that basically everyone will need to graduate from being ICs to ICs that manage teams of 20-30 agents: "The best developers today don't just sit there in front of their IDEs and synchronously talk to their agent." "[Instead], you have like 30 separate branches that are each being worked on by a different agent. And you can have the agents continue to update the branches based on human and other agent feedback." "And I think this whole idea of it taking hours for that entire loop to complete — agent pushes some changes, the changes get feedback from other agents or humans, the agent responds to that — that whole loop could be hours, not just minutes. So you're not going to just sit there and watch it one at a time." "But the powerful thing about this is, each one is still actually operating faster than a human engineer. One agent on one branch can do the work of maybe three humans, operating 3x as fast. So it's like a 10x leverage factor just for one agent." "But the best engineers are now able to multitask and say, 'I'm going to oversee my own little team of 20-30 agents working concurrently.'" "Everyone needs to graduate from being an IC to an IC manager of agents. Meaning, if you're a VC analyst, your job should no longer be to go synchronously research one company. You need to go and research like 30 companies, and do them all faster, better, and higher quality than you could before." "That's the greatest leap that is going to be challenging for a lot of people in a lot of roles. Because it's a totally different mentality in how you operate, and what your role is."
1:56

Airtable's Howie Liu says that basically everyone will need to graduate from being ICs to ICs that manage teams of 20-30 agents: "The best developers today don't just sit there in front of their IDEs and synchronously talk to their agent." "[Instead], you have like 30 separate branches that are each being worked on by a different agent. And you can have the agents continue to update the branches based on human and other agent feedback." "And I think this whole idea of it taking hours for that entire loop to complete — agent pushes some changes, the changes get feedback from other agents or humans, the agent responds to that — that whole loop could be hours, not just minutes. So you're not going to just sit there and watch it one at a time." "But the powerful thing about this is, each one is still actually operating faster than a human engineer. One agent on one branch can do the work of maybe three humans, operating 3x as fast. So it's like a 10x leverage factor just for one agent." "But the best engineers are now able to multitask and say, 'I'm going to oversee my own little team of 20-30 agents working concurrently.'" "Everyone needs to graduate from being an IC to an IC manager of agents. Meaning, if you're a VC analyst, your job should no longer be to go synchronously research one company. You need to go and research like 30 companies, and do them all faster, better, and higher quality than you could before." "That's the greatest leap that is going to be challenging for a lot of people in a lot of roles. Because it's a totally different mentality in how you operate, and what your role is."

TBPN

35,595 views • 4 months ago

AI creation is moving beyond one-click generation. The interesting shift now is bringing ideas, references, prompts, assets, and revisions into one creative workspace instead of scattering them across different apps. That's what stood out to me about TapNow Creative OS. It feels less like another AI tool and more like an operating system for creative work. Curious to see where this goes. #TapTV #CreativeOS #TapNow
0:30

AI creation is moving beyond one-click generation. The interesting shift now is bringing ideas, references, prompts, assets, and revisions into one creative workspace instead of scattering them across different apps. That's what stood out to me about TapNow Creative OS. It feels less like another AI tool and more like an operating system for creative work. Curious to see where this goes. #TapTV #CreativeOS #TapNow

Sophie Ai

18,469 views • 1 month ago

Every AI lab built you a single-player chatbot. But group chat got nothing. And we need agents that know how to listen and do things, not just talk. So we built Convos. We've been calling it an agentic messenger. It gives every group chat a harness: any model, real tools, and little agents that get things done. Nothing is shared across groups. 🧾 The trip group chat gets an agent that builds a killer itinerary and splits the expenses. 🏓 The pickleball chat gets a coordinator that books the court and gets everyone there. 🍳 The family chat gets a meal planner that picks recipes and writes the shopping list. Got another idea? Tag Convos and it'll reply with an agent for your group. Free to try, no sign up required. Here's how Shane Mac runs his life with his team of little agents. 1/7
6:46

Every AI lab built you a single-player chatbot. But group chat got nothing. And we need agents that know how to listen and do things, not just talk. So we built Convos. We've been calling it an agentic messenger. It gives every group chat a harness: any model, real tools, and little agents that get things done. Nothing is shared across groups. 🧾 The trip group chat gets an agent that builds a killer itinerary and splits the expenses. 🏓 The pickleball chat gets a coordinator that books the court and gets everyone there. 🍳 The family chat gets a meal planner that picks recipes and writes the shopping list. Got another idea? Tag Convos and it'll reply with an agent for your group. Free to try, no sign up required. Here's how Shane Mac runs his life with his team of little agents. 1/7

Convos

398,916 views • 1 month ago