Загрузка видео...

Не удалось загрузить видео

На главную

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♨️

123,201 subscribers

66,106 просмотров • 2 дней назад •via X (Twitter)

ОбразованиеНаука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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,583 просмотров • 1 год назад

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 просмотров • 1 год назад

Launching AI Discovery And Communication DeepAgent discovers other AI agents and software tools on the fly and communicates with them to perform complex tasks. Here is how it works - - DeepAgent searches for other AI agents and tools - Finds the right tool for the job - Establishes contact using MCP and handles auth - Collaborates with the other tool to get the job done! - Remembers this tool for future colabs! Much like humans, it can create a team of AI agents or software tools to perform tasks. Here it is, learning about MindMaps, communicating with another server, and creating a Mindmap!!
0:31

Launching AI Discovery And Communication DeepAgent discovers other AI agents and software tools on the fly and communicates with them to perform complex tasks. Here is how it works - - DeepAgent searches for other AI agents and tools - Finds the right tool for the job - Establishes contact using MCP and handles auth - Collaborates with the other tool to get the job done! - Remembers this tool for future colabs! Much like humans, it can create a team of AI agents or software tools to perform tasks. Here it is, learning about MindMaps, communicating with another server, and creating a Mindmap!!

Bindu Reddy

13,598 просмотров • 1 год назад

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 просмотров • 1 год назад

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 просмотров • 2 лет назад

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

457,547 просмотров • 19 дней назад

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,024 просмотров • 4 месяцев назад

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,949 просмотров • 1 месяц назад

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,571 просмотров • 1 год назад

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,397 просмотров • 7 месяцев назад

Introducing SwarmLabs $LABS A swarm of specialized AI agents-set to redefine content creation. The agents work together in perfect synergy to turn complex video workflows into simplified and automated videos from concept to finish. F1HBAzQGgiuq7tRMLRr7J1vqPcc4kq3vHY9yM6zmpump
0:22

Introducing SwarmLabs $LABS A swarm of specialized AI agents-set to redefine content creation. The agents work together in perfect synergy to turn complex video workflows into simplified and automated videos from concept to finish. F1HBAzQGgiuq7tRMLRr7J1vqPcc4kq3vHY9yM6zmpump

Swarmlabs

69,354 просмотров • 1 год назад

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 🚀

118,124 просмотров • 28 дней назад

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 просмотров • 2 месяцев назад

Documents shouldn’t be static files anymore. Over the last days I’ve been testing Felo LiveDoc Felo AI (EN) – an Agent Workspace for Documents where humans and AI agents work together on one intelligent canvas. It’s quickly becoming one of the most interesting ways to run complex projects end-to-end. First, I transformed the well-known "Attention all you need" into a PowerPoint presentation:
0:49

Documents shouldn’t be static files anymore. Over the last days I’ve been testing Felo LiveDoc Felo AI (EN) – an Agent Workspace for Documents where humans and AI agents work together on one intelligent canvas. It’s quickly becoming one of the most interesting ways to run complex projects end-to-end. First, I transformed the well-known "Attention all you need" into a PowerPoint presentation:

Chubby♨️

64,425 просмотров • 7 месяцев назад

New agentic short course! Multi AI Agent Systems with crewAI, built with CrewAI's founder and CEO João Moura. In this course, you'll learn how to break down complex tasks into subtasks for multiple AI agents, each playing a specialized role, to execute. For example, to generate a research report, you might have researcher, writer, and quality assurance agents collaborate. You'll define the roles, expectations, and interactions between the agents—like a manager organizing a team. You'll work with key agentic AI techniques like role-playing, tool use, memory, guardrails, and cross-agent collaboration. And you'll build your own multi-agent systems that can tackle complex tasks. I think you'll find it both productive and fun to design agents and watch them collaborate to get things done. Let me know what you think! I believe multi-agent architectures will drive significant progress in AI systems. Please sign up here!
2:39

New agentic short course! Multi AI Agent Systems with crewAI, built with CrewAI's founder and CEO João Moura. In this course, you'll learn how to break down complex tasks into subtasks for multiple AI agents, each playing a specialized role, to execute. For example, to generate a research report, you might have researcher, writer, and quality assurance agents collaborate. You'll define the roles, expectations, and interactions between the agents—like a manager organizing a team. You'll work with key agentic AI techniques like role-playing, tool use, memory, guardrails, and cross-agent collaboration. And you'll build your own multi-agent systems that can tackle complex tasks. I think you'll find it both productive and fun to design agents and watch them collaborate to get things done. Let me know what you think! I believe multi-agent architectures will drive significant progress in AI systems. Please sign up here!

Andrew Ng

349,977 просмотров • 2 лет назад

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

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

Yarchi

57,942 просмотров • 27 дней назад

I created an AI agent arena where agents trade on 15/5-minute markets 24/7 on Polymarket. Without using OpenClaw or Claude Code > Each AI agent competes against the others using different settings to achieve the best results. It cost me $0 to build. My goal is to identify the best agents with the best strategies on the demo account and transfer them to a live account. And this is entirely feasible.
0:40

I created an AI agent arena where agents trade on 15/5-minute markets 24/7 on Polymarket. Without using OpenClaw or Claude Code > Each AI agent competes against the others using different settings to achieve the best results. It cost me $0 to build. My goal is to identify the best agents with the best strategies on the demo account and transfer them to a live account. And this is entirely feasible.

Atenov int.

18,562 просмотров • 2 месяцев назад

How I built an AI Agent team that runs 24/7 explained in 19 minutes. OpenClaw is where the squad started. Hermes is where it's evolving. YES, I use both of THEM just via Telegram. 4 things that makes my agent team work like humans: - Automated Cron: Agents run pro-actively on schedules and heartbeats - Memory: They keep context about my preferences, audience, past performance, and decisions. - Self-improving review loops: Each agent reviews its own work monthly. Monica reviews the entire squad bi-weekly and grades them. - Escalation: They do the work, but I still make the final decision. These agents manage the open-source Awesome LLM Apps repo with 115k+ GitHub stars and help me stay up-to-date with pro-active daily signals. I operate like a CEO reviewing a squad from my phone. The agents keep the work moving until I have to step in.
19:46

How I built an AI Agent team that runs 24/7 explained in 19 minutes. OpenClaw is where the squad started. Hermes is where it's evolving. YES, I use both of THEM just via Telegram. 4 things that makes my agent team work like humans: - Automated Cron: Agents run pro-actively on schedules and heartbeats - Memory: They keep context about my preferences, audience, past performance, and decisions. - Self-improving review loops: Each agent reviews its own work monthly. Monica reviews the entire squad bi-weekly and grades them. - Escalation: They do the work, but I still make the final decision. These agents manage the open-source Awesome LLM Apps repo with 115k+ GitHub stars and help me stay up-to-date with pro-active daily signals. I operate like a CEO reviewing a squad from my phone. The agents keep the work moving until I have to step in.

Shubham Saboo

128,913 просмотров • 6 дней назад

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch
58:55

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

375,365 просмотров • 3 месяцев назад