正在加载视频...

视频加载失败

返回首页

OpenAI wants markdown structure. Anthropic prefers XML tags. Google emphasizes few-shot examples. So I built a simple agent system that reads the official prompting docs and applies them to the given prompt. Each optimizer runs a ReAct loop: - list_provider_docs → discover available guidelines - read_provider_doc → fetch specific...

koylanai's profile picture

Muratcan Koylan

12,681 subscribers

62,021 次观看 • 6 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

You wanted shadcn — so we built the heinous infra to make it work. Introducing Agent Arena, starting with the best: Claude Code by Anthropic Codex 5 by OpenAI Cursor Agent by Cursor Devin by Cognition Gemini CLI by Google DeepMind Grok Code Fast 1 by xAI 1/ Your prompt launches a containerized agent inside a fresh GitHub repo 2/ The agent can install packages, make tool calls, and write multi-file code 3/ The repo is deployed to Vercel *by the agent*, clonable to your heart's desire
0:25

You wanted shadcn — so we built the heinous infra to make it work. Introducing Agent Arena, starting with the best: Claude Code by Anthropic Codex 5 by OpenAI Cursor Agent by Cursor Devin by Cognition Gemini CLI by Google DeepMind Grok Code Fast 1 by xAI 1/ Your prompt launches a containerized agent inside a fresh GitHub repo 2/ The agent can install packages, make tool calls, and write multi-file code 3/ The repo is deployed to Vercel *by the agent*, clonable to your heart's desire

Grace Li

168,748 次观看 • 8 个月前

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 次观看 • 15 天前

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

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

Jurij Skornik

10,936 次观看 • 24 天前

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

374,979 次观看 • 3 个月前

My brother (Daniel Cohen Hillel) and I worked on a fun project tonight, inspired by Yohei : Coding Agent that follows the Test Driven Development (TDD) methodology! You write the tests - and the agent runs in a loop until it creates the feature properly! 1/6 #buildinpublic
0:49

My brother (Daniel Cohen Hillel) and I worked on a fun project tonight, inspired by Yohei : Coding Agent that follows the Test Driven Development (TDD) methodology! You write the tests - and the agent runs in a loop until it creates the feature properly! 1/6 #buildinpublic

ADAM

384,792 次观看 • 3 年前

Here's a clip from my upcoming AI SDK tutorial: We're building what Anthropic calls an 'agent' in TypeScript. Can it react to results of tool calls, deciding when it's completed the task? It's an agent.
3:58

Here's a clip from my upcoming AI SDK tutorial: We're building what Anthropic calls an 'agent' in TypeScript. Can it react to results of tool calls, deciding when it's completed the task? It's an agent.

Matt Pocock

23,015 次观看 • 1 年前

Review code written by one agent using a different agent entirely. Here, Claude handles the task, and Gemini runs the review, leaves inline comments, and sends them back to the original agent to implement. Any combination works.
0:39

Review code written by one agent using a different agent entirely. Here, Claude handles the task, and Gemini runs the review, leaves inline comments, and sends them back to the original agent to implement. Any combination works.

Air by JetBrains

19,476,873 次观看 • 1 个月前

There are two types of engineers in 2026 The first opens his laptop in the morning, writes a prompt, waits, reads the diff, fixes it, repeats The second opens his phone, checks what shipped while he was asleep Different answer to one question: who is the loop? The first engineer is the loop, he starts the agent, reviews the output, decides what's next, the moment he steps away it stops The second engineer built the system that is the loop instead of him, PR review, flaky tests, CI triage, all running without him, he just reads the report What stops most people isn't complexity It's that they never noticed they are the bottleneck Full guide to building the system that runs without you below
1:04

There are two types of engineers in 2026 The first opens his laptop in the morning, writes a prompt, waits, reads the diff, fixes it, repeats The second opens his phone, checks what shipped while he was asleep Different answer to one question: who is the loop? The first engineer is the loop, he starts the agent, reviews the output, decides what's next, the moment he steps away it stops The second engineer built the system that is the loop instead of him, PR review, flaky tests, CI triage, all running without him, he just reads the report What stops most people isn't complexity It's that they never noticed they are the bottleneck Full guide to building the system that runs without you below

plutos

12,370 次观看 • 6 天前

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

55,472 次观看 • 14 天前

Introducing the Generative UI Research Canvas ✨ Every agent needs a powerful UI Combine LangChain, Tavily, Tako and CopilotKit🪁 and you get a LangChain-based research agent with a Generative UI-driven frontend. When agents can explore the underlying data, research becomes more trustworthy and useful. How does this work? - LangChain manages the agent workflow and tool orchestration. - Tako converts retrieved data into structured, visual components - Tavily provides agentic search - CopilotKit renders those components in the UI and keeps the user in the loop while the agent is working So instead of a boring and static report, the output is an interactive research canvas that evolves as the agent runs. 2026 is the year where users want to see the output, not read it... Generative UI makes this possible for agentic applications. Tutorial: Open-Source Repo: Docs:
0:36

Introducing the Generative UI Research Canvas ✨ Every agent needs a powerful UI Combine LangChain, Tavily, Tako and CopilotKit🪁 and you get a LangChain-based research agent with a Generative UI-driven frontend. When agents can explore the underlying data, research becomes more trustworthy and useful. How does this work? - LangChain manages the agent workflow and tool orchestration. - Tako converts retrieved data into structured, visual components - Tavily provides agentic search - CopilotKit renders those components in the UI and keeps the user in the loop while the agent is working So instead of a boring and static report, the output is an interactive research canvas that evolves as the agent runs. 2026 is the year where users want to see the output, not read it... Generative UI makes this possible for agentic applications. Tutorial: Open-Source Repo: Docs:

Atai Barkai

11,997 次观看 • 4 个月前

I built a multimodal AI Coding Agent team with multi-agents. It has 3 AI agents working together as a team to generate and execute the code: 1. Coding Agent using o-3 mini 2. Vision Agent using Gemini 3. Code Execution Agent using o-3 mini and E2B 100% Opensource Code.
1:36

I built a multimodal AI Coding Agent team with multi-agents. It has 3 AI agents working together as a team to generate and execute the code: 1. Coding Agent using o-3 mini 2. Vision Agent using Gemini 3. Code Execution Agent using o-3 mini and E2B 100% Opensource Code.

Shubham Saboo

42,269 次观看 • 1 年前

THIS GUY IS RUNNING A 5-AGENT OPENCLAW TEAM 24/7 FOR UNDER $50 A MONTH five agents all running continuously and handing tasks to each other > research agent tracking trends and competitors > writing agent handling marketing content and drafts > ops agent managing emails and scheduling > monitoring agent watching for alerts and updates > coordinator agent routing tasks between all of them and he built a full 3D isometric office where you can watch all of them work in real time and see the current task that each agent is doing each agent has a character, a desk, and a name tag. when it's time for a standup, they walk to the meeting room and gather which is insane it even has voice connection. you can talk to the agents through speech-to-text and tell them what to do out loud it's a tiny autonomous team that runs itself. the coordinator decides who handles what and tasks get passed between agents automatically. it never stops and runs 24/7 all for less than $50/month. we went from AI tools a few months back to AI employees real fast
0:57

THIS GUY IS RUNNING A 5-AGENT OPENCLAW TEAM 24/7 FOR UNDER $50 A MONTH five agents all running continuously and handing tasks to each other > research agent tracking trends and competitors > writing agent handling marketing content and drafts > ops agent managing emails and scheduling > monitoring agent watching for alerts and updates > coordinator agent routing tasks between all of them and he built a full 3D isometric office where you can watch all of them work in real time and see the current task that each agent is doing each agent has a character, a desk, and a name tag. when it's time for a standup, they walk to the meeting room and gather which is insane it even has voice connection. you can talk to the agents through speech-to-text and tell them what to do out loud it's a tiny autonomous team that runs itself. the coordinator decides who handles what and tasks get passed between agents automatically. it never stops and runs 24/7 all for less than $50/month. we went from AI tools a few months back to AI employees real fast

Om Patel

27,131 次观看 • 2 个月前

boris cherny shipped 259 PRs in 30 days and typed none of them. claude code wrote every line. peter steinberger said the same idea this week and it hit 2.2M views. one built claude code at anthropic. one built openclaw and joined openai. opposite labs, one conclusion: stop prompting agents, write the loops that prompt them. the replies are still arguing about what a loop even looks like in practice. i went looking for the built version. it's a multi-agent workspace manager called gas town: a coordinator agent runs 20-30 workers and a merge queue gates every change before it hits main. the philosophy fit in two tweets. the implementation has 15k stars.
0:55

boris cherny shipped 259 PRs in 30 days and typed none of them. claude code wrote every line. peter steinberger said the same idea this week and it hit 2.2M views. one built claude code at anthropic. one built openclaw and joined openai. opposite labs, one conclusion: stop prompting agents, write the loops that prompt them. the replies are still arguing about what a loop even looks like in practice. i went looking for the built version. it's a multi-agent workspace manager called gas town: a coordinator agent runs 20-30 workers and a merge queue gates every change before it hits main. the philosophy fit in two tweets. the implementation has 15k stars.

Rohit

30,131 次观看 • 12 天前

I'm proud to present this video created with Grok. Here are the main steps in the making of this video: 1. I wrote a draft script by hand. 2. I reworked the script with Grok to eliminate inconsistencies and add technical details (what I have them say about the Apollo missions and the stones is accurate). 3. Grok broke it down into scenes. 4. I switched to Grok Imagine's Agent mode: transforming each scene into a prompt. 5. I animated each scene in Agent mode using video, as well as cropping and image selection. 6. I edited it. Here's the result; it's hard to call it AI. I look forward to reading your comments. Grok Imagine Elon Musk
2:42

I'm proud to present this video created with Grok. Here are the main steps in the making of this video: 1. I wrote a draft script by hand. 2. I reworked the script with Grok to eliminate inconsistencies and add technical details (what I have them say about the Apollo missions and the stones is accurate). 3. Grok broke it down into scenes. 4. I switched to Grok Imagine's Agent mode: transforming each scene into a prompt. 5. I animated each scene in Agent mode using video, as well as cropping and image selection. 6. I edited it. Here's the result; it's hard to call it AI. I look forward to reading your comments. Grok Imagine Elon Musk

Déborah

67,972 次观看 • 13 天前

soon you're going to be able to have AI autonomously build apps for you, with no human in the loop. me, someone who can't code, can make an app with - Claude Computer Agent, that controls Cursor - clones a github repo - opens composer in agent mode - and prompts it with an app idea - and then waits for the Cursor Agent to finish Then I prompted that agent to test the app! (template @senior_swc)
1:34

soon you're going to be able to have AI autonomously build apps for you, with no human in the loop. me, someone who can't code, can make an app with - Claude Computer Agent, that controls Cursor - clones a github repo - opens composer in agent mode - and prompts it with an app idea - and then waits for the Cursor Agent to finish Then I prompted that agent to test the app! (template @senior_swc)

Riley Brown

48,960 次观看 • 1 年前

9 out of 10 multi-agent projects never leave demo mode Not because the model is bad. Because the structure is missing. Most people who try to build [ a team of AI agents ] end up with one agent talking to itself in five tabs. The agents don't share context → Don't divide work → Don't know what the others are doing. > stage 1: if your agent doesn't have a real loop, observe, act, iterate, you have a long prompt, not an agent > stage 2: subagents need isolated context, the orchestrator never reads their raw transcript, only the summary > stage 3: the orchestrator plans and delegates, the moment it executes, it drowns in details that belong inside subagents > stage 4: without a shared task list it's not a team, it's five agents duplicating each other's work in parallel > stage 5: a permissions file is what lets you sleep, the model cannot bypass it because the rule lives outside the model a team of AI agents is not more model, it is more structure the most ignored stage in every demo that died: - durability... when a 50-step task crashes at step 47 and starts from zero, that's not a model failure. that's a missing write-to-disk call
1:07

9 out of 10 multi-agent projects never leave demo mode Not because the model is bad. Because the structure is missing. Most people who try to build [ a team of AI agents ] end up with one agent talking to itself in five tabs. The agents don't share context → Don't divide work → Don't know what the others are doing. > stage 1: if your agent doesn't have a real loop, observe, act, iterate, you have a long prompt, not an agent > stage 2: subagents need isolated context, the orchestrator never reads their raw transcript, only the summary > stage 3: the orchestrator plans and delegates, the moment it executes, it drowns in details that belong inside subagents > stage 4: without a shared task list it's not a team, it's five agents duplicating each other's work in parallel > stage 5: a permissions file is what lets you sleep, the model cannot bypass it because the rule lives outside the model a team of AI agents is not more model, it is more structure the most ignored stage in every demo that died: - durability... when a 50-step task crashes at step 47 and starts from zero, that's not a model failure. that's a missing write-to-disk call

Shadow Nick

14,501 次观看 • 20 天前

I built a multi-agent Deep Research team using Qwen 3 that can generate consulting style reports as Google docs. It has 3 AI Agents working together as a team: 1. Research Question Agent 2. Web Search Agent 3. Google Docs Compilation Agent 100% Opensource Code.
0:54

I built a multi-agent Deep Research team using Qwen 3 that can generate consulting style reports as Google docs. It has 3 AI Agents working together as a team: 1. Research Question Agent 2. Web Search Agent 3. Google Docs Compilation Agent 100% Opensource Code.

Shubham Saboo

25,071 次观看 • 1 年前

📚 Build Deep Research Agent: From Question to Insight Complex research rarely fits in one search box. The Deep Research workflow built with Dify Iterates, reasons, and sources until the answer is complete. 💡 Key workflow nodes include: 1) Start: capture the research topic and the loop budget 2) Exa Answer: gather background terminology 3) Intent LLM: clarify the real research goal 4) Loop: drive the iterative cycles 5) Reasoning LLM: frame better follow-up questions 6) Agent: execute searches, extract content, and reflect 7) Variable Assigner: update the state after each pass 8) Final Summary: synthesize a Markdown report with citations Teams using this template cut research time dramatically and surface insights competitors miss. Learn to implement this workflow:
0:24

📚 Build Deep Research Agent: From Question to Insight Complex research rarely fits in one search box. The Deep Research workflow built with Dify Iterates, reasons, and sources until the answer is complete. 💡 Key workflow nodes include: 1) Start: capture the research topic and the loop budget 2) Exa Answer: gather background terminology 3) Intent LLM: clarify the real research goal 4) Loop: drive the iterative cycles 5) Reasoning LLM: frame better follow-up questions 6) Agent: execute searches, extract content, and reflect 7) Variable Assigner: update the state after each pass 8) Final Summary: synthesize a Markdown report with citations Teams using this template cut research time dramatically and surface insights competitors miss. Learn to implement this workflow:

Dify

22,470 次观看 • 1 年前

Holy Shit This is insane result 🤯 I used opus 4.6 as a reviewer/planner and 4 worker minimax M2.7 agent and this the result Voxel art of eiffel tower < loop set to 5 that means opus will tell MiniMax (official) to make it better 5 times >
0:33

Holy Shit This is insane result 🤯 I used opus 4.6 as a reviewer/planner and 4 worker minimax M2.7 agent and this the result Voxel art of eiffel tower < loop set to 5 that means opus will tell MiniMax (official) to make it better 5 times >

Chetaslua

82,988 次观看 • 3 个月前

this chinese developer making $320k/year as a solo contractor his secret: 5 AI agents running in parallel, each one a specialist architect, coder, reviewer, tester, ops they don’t share context, don’t step on each other, just ship he takes on projects meant for teams of 5-8 engineers delivers in half the time keeps the entire budget found this video on bilibili at 3am and watched it four times guy sitting at his desk, two monitors filled with code, and he’s barely touching the keyboard here’s what’s happening on his screen: > agent 1 (architect): designs system structure, breaks down features into tasks, decides what gets built first > agent 2 (coder): writes the actual implementation based on architect’s specs > agent 3 (reviewer): checks every piece of code for bugs, edge cases, security issues > agent 4 (tester): generates test cases, runs them, reports failures back > agent 5 (ops): handles deployment, monitoring, infrastructure five separate claude code instances running simultaneously each one has its own system prompt, its own context, its own specialty they communicate through a shared task queue, not through each other that’s the key insight - no shared context means no conflicts agent 2 doesn’t know what agent 3 is doing agent 4 doesn’t care what agent 1 decided they just pick up tasks, complete them, move on he showed his contract history: > 3D rendering pipeline for a gaming studio: $25k > automated trading dashboard: $33k > enterprise CRM rebuild: $44k all completed solo, all delivered early, all clients thought they were hiring a team the code on his screen is python with blender integration - complex stuff that would normally require 3-4 specialists he’s shipping it in days while the client expects weeks while he’s explaining the system to camera, commits are happening in the background, tests running, deployments going out all while he’s literally not touching the keyboard his API costs run about $2k/month his revenue averages $26k/month that’s a 13x return on his AI investment this is the new solo developer playbook don’t compete with teams become the team
1:24

this chinese developer making $320k/year as a solo contractor his secret: 5 AI agents running in parallel, each one a specialist architect, coder, reviewer, tester, ops they don’t share context, don’t step on each other, just ship he takes on projects meant for teams of 5-8 engineers delivers in half the time keeps the entire budget found this video on bilibili at 3am and watched it four times guy sitting at his desk, two monitors filled with code, and he’s barely touching the keyboard here’s what’s happening on his screen: > agent 1 (architect): designs system structure, breaks down features into tasks, decides what gets built first > agent 2 (coder): writes the actual implementation based on architect’s specs > agent 3 (reviewer): checks every piece of code for bugs, edge cases, security issues > agent 4 (tester): generates test cases, runs them, reports failures back > agent 5 (ops): handles deployment, monitoring, infrastructure five separate claude code instances running simultaneously each one has its own system prompt, its own context, its own specialty they communicate through a shared task queue, not through each other that’s the key insight - no shared context means no conflicts agent 2 doesn’t know what agent 3 is doing agent 4 doesn’t care what agent 1 decided they just pick up tasks, complete them, move on he showed his contract history: > 3D rendering pipeline for a gaming studio: $25k > automated trading dashboard: $33k > enterprise CRM rebuild: $44k all completed solo, all delivered early, all clients thought they were hiring a team the code on his screen is python with blender integration - complex stuff that would normally require 3-4 specialists he’s shipping it in days while the client expects weeks while he’s explaining the system to camera, commits are happening in the background, tests running, deployments going out all while he’s literally not touching the keyboard his API costs run about $2k/month his revenue averages $26k/month that’s a 13x return on his AI investment this is the new solo developer playbook don’t compete with teams become the team

regent0x

183,659 次观看 • 1 个月前