Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

A TEAM JUST DEPLOYED 15 AUTONOMOUS LOOP AGENTS FROM A SINGLE PROMPT USING APPLIED GRAPH ENGINEERING Most developers still manually hardcode multi agent systems, writing separate logic for every individual task. Graph engineering changes this by using a central topological map to spin up all 15 nodes simultaneously. A...

slash1sol's profile picture

slash1s

12,457 subscribers

302,066 görüntüleme • 1 ay önce •via X (Twitter)

Bilim & TeknolojiEğitimSağlık & İyilik
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

ANTHROPIC ENGINEER JUST SHOWS EXACTLY WHAT GRAPH ENGINEERING LOOKS LIKE WHEN A TASK RUNS THROUGH IT most people arguing about graphs online have never actually watched one execute Task → Researcher → Planner → Writer + Code Agent → Reviewer → Deploy six nodes, one shared state, graph completes itself while you watch loop mode gets disabled the second the task splits into real specialties, one agent stops trying to do everything at once reviewer catches a failure, kicks it straight back to the exact node that broke - not a full restart, no lost context the graph is not a fancier loop - it is the org chart your agents were missing bookmark this and watch it run, then read the article below to see why the timeline just found what production systems already do
0:10

ANTHROPIC ENGINEER JUST SHOWS EXACTLY WHAT GRAPH ENGINEERING LOOKS LIKE WHEN A TASK RUNS THROUGH IT most people arguing about graphs online have never actually watched one execute Task → Researcher → Planner → Writer + Code Agent → Reviewer → Deploy six nodes, one shared state, graph completes itself while you watch loop mode gets disabled the second the task splits into real specialties, one agent stops trying to do everything at once reviewer catches a failure, kicks it straight back to the exact node that broke - not a full restart, no lost context the graph is not a fancier loop - it is the org chart your agents were missing bookmark this and watch it run, then read the article below to see why the timeline just found what production systems already do

leopardracer

53,328 görüntüleme • 1 ay önce

FIVE LAYERS OF AGENT ENGINEERING, EACH ONE WRAPS THE ONE BELOW IT. IF YOU SKIP LAYER 2, YOUR LAYER 5 WILL LOOK BROKEN WHEN IT IS ACTUALLY JUST STANDING ON NOTHING. for weeks i debated harness vs loop vs graph like they were competing choices. then a stack diagram made the shape obvious. they are not choices. they are floors. 01 | prompt engineering. the message. unit of work: one input. inputs are role, instructions, examples, format. output is a single raw response. 02 | context engineering. the memory. unit of work: what stays in the window. a curator selects, compresses, and drops from query, docs, memory, prior turns, and tool outputs before the prompt runs. 03 | harness engineering. the machine. unit of work: the machine itself. gather (context + prompt) → LLM → tools or sub-agents → verifier → final response. the article calls this the operating environment. 04 | loop engineering. the system. unit of work: the run. goal + success criteria + max iterations + budget + completion check wrap around one harness pass. failed pass appends results to context and retries. 05 | graph engineering. the topology. unit of work: the graph run. goal + nodes + edges + state schema. graph routes to agent nodes, tool nodes, or human approval. a reviewer node with a different model and fresh context checks the final answer. the wrapping is the whole point. layer 5 assumes layer 4 works. layer 4 assumes layer 3 works. skip layer 2 and layer 3's verifier keeps failing without a clear reason. this is why swapping the model is a one-day project and swapping the stack is a quarter. the model is the commodity. the five layers around it are the engineering. full three-layer breakdown of the top of the stack (harness, loop, graph) in the post below.
0:20

FIVE LAYERS OF AGENT ENGINEERING, EACH ONE WRAPS THE ONE BELOW IT. IF YOU SKIP LAYER 2, YOUR LAYER 5 WILL LOOK BROKEN WHEN IT IS ACTUALLY JUST STANDING ON NOTHING. for weeks i debated harness vs loop vs graph like they were competing choices. then a stack diagram made the shape obvious. they are not choices. they are floors. 01 | prompt engineering. the message. unit of work: one input. inputs are role, instructions, examples, format. output is a single raw response. 02 | context engineering. the memory. unit of work: what stays in the window. a curator selects, compresses, and drops from query, docs, memory, prior turns, and tool outputs before the prompt runs. 03 | harness engineering. the machine. unit of work: the machine itself. gather (context + prompt) → LLM → tools or sub-agents → verifier → final response. the article calls this the operating environment. 04 | loop engineering. the system. unit of work: the run. goal + success criteria + max iterations + budget + completion check wrap around one harness pass. failed pass appends results to context and retries. 05 | graph engineering. the topology. unit of work: the graph run. goal + nodes + edges + state schema. graph routes to agent nodes, tool nodes, or human approval. a reviewer node with a different model and fresh context checks the final answer. the wrapping is the whole point. layer 5 assumes layer 4 works. layer 4 assumes layer 3 works. skip layer 2 and layer 3's verifier keeps failing without a clear reason. this is why swapping the model is a one-day project and swapping the stack is a quarter. the model is the commodity. the five layers around it are the engineering. full three-layer breakdown of the top of the stack (harness, loop, graph) in the post below.

kocer

30,675 görüntüleme • 9 gün önce

THIS DEVELOPER USED OPENCLAW AGENTS TO RUN HIS B2B BUSINESS VIA TELEGRAM AND MADE $15,000/MONTH he doesn't write prompts from scratch or use generic browser interfaces. he runs a multi-agent framework through a mobile chat. the agents write code, test deployments, and update sites in real-time while he just hits approve the setup is straightforward: - spin up Coolify on a free cloud instance to host your own self-hosted agent panels - link the agent loop to a Telegram gateway to approve code edits from your phone - deploy specialized skill files directly to limit token waste and context decay - containerize the terminal execution using Docker to prevent security breaches if you are still running local agents without container safety, you are leaving money on the table. read the 30-day battle between OpenClaw and Hermes Agent to see who actually wins in production Full breakdown and migration playbook ↓
0:17

THIS DEVELOPER USED OPENCLAW AGENTS TO RUN HIS B2B BUSINESS VIA TELEGRAM AND MADE $15,000/MONTH he doesn't write prompts from scratch or use generic browser interfaces. he runs a multi-agent framework through a mobile chat. the agents write code, test deployments, and update sites in real-time while he just hits approve the setup is straightforward: - spin up Coolify on a free cloud instance to host your own self-hosted agent panels - link the agent loop to a Telegram gateway to approve code edits from your phone - deploy specialized skill files directly to limit token waste and context decay - containerize the terminal execution using Docker to prevent security breaches if you are still running local agents without container safety, you are leaving money on the table. read the 30-day battle between OpenClaw and Hermes Agent to see who actually wins in production Full breakdown and migration playbook ↓

marfin

26,654 görüntüleme • 3 ay önce

I launched 300 Grok agents to automate the routine and see what would come of it. As a result, my business reached a profit of +356% Honestly, I still don't understand why absolutely everyone isn't using this method. While everyone else is writing posts and monitoring trends manually, this AI stack works like a well-oiled clockwork mechanism How it's structured: Dedicated cloud instances share the load via a single distributed bus, distributing tasks in batches of 50 parallel threads per agent The central configurator dynamically switches tasks between system workers, processing domains, parsing inputs, and gathering results into a single knowledge graph Each agent runs an algorithm through a fixed cycle (setup -> run -> correct -> save -> schedule), instantly correcting deviations and fixing data in the database Instead of spending hundreds of hours on manual operations, I handed all this machinery over to AI. The result speaks for itself, reach and productivity have grown exponentially, and the system operates autonomously 24/7 The visualization is made for a clear example and may differ from the actual work of the agents The article describes the detailed automation method, bookmark it
0:10

I launched 300 Grok agents to automate the routine and see what would come of it. As a result, my business reached a profit of +356% Honestly, I still don't understand why absolutely everyone isn't using this method. While everyone else is writing posts and monitoring trends manually, this AI stack works like a well-oiled clockwork mechanism How it's structured: Dedicated cloud instances share the load via a single distributed bus, distributing tasks in batches of 50 parallel threads per agent The central configurator dynamically switches tasks between system workers, processing domains, parsing inputs, and gathering results into a single knowledge graph Each agent runs an algorithm through a fixed cycle (setup -> run -> correct -> save -> schedule), instantly correcting deviations and fixing data in the database Instead of spending hundreds of hours on manual operations, I handed all this machinery over to AI. The result speaks for itself, reach and productivity have grown exponentially, and the system operates autonomously 24/7 The visualization is made for a clear example and may differ from the actual work of the agents The article describes the detailed automation method, bookmark it

Bober_smart

14,733 görüntüleme • 16 gün önce

OpenAI's AgentKit will be so insane, build every step of agents on one platform. These visual agent builders make the whole process of iterating and launching agents far more efficient. It sits on top of the Responses API and unifies the tools that were previously scattered across SDKs and custom orchestration. It lets developers create agent workflows visually, connect data sources securely, and measure performance automatically without coding every layer by hand. The core of AgentKit is the Agent Builder, a drag-and-drop canvas where each node represents an action, guardrail, or decision branch. Developers can link these nodes into multi-agent workflows, preview results instantly, and version each setup. It supports inline evaluation so that developers can see how changes affect output before deploying. The Connector Registry is a single admin panel that manages how data and tools connect across the OpenAI ecosystem. It centralizes integrations like Google Drive, SharePoint, Dropbox, and Microsoft Teams. Large organizations can govern access and flow of data between agents securely under one global console. ChatKit provides a ready-to-use chat interface for embedding agents inside apps or websites. It manages streaming, message threads, and model reasoning displays automatically. Developers can skin the interface to match their product without writing custom front-end code. Under the hood, all these blocks use the same execution core that runs agent reasoning through OpenAI’s APIs. Workflows in Agent Builder compile down to structured instructions for the Responses API, which handles model calls, tool use, and context passing. Connector Registry handles authentication and routing for external tools, while Evals and RFT provide feedback loops that improve agents over time. This integration means developers no longer need to handle orchestration logic, model evaluation pipelines, or safety layers separately. Everything runs natively within OpenAI’s control plane with managed security, automatic versioning, and built-in testing. In short, AgentKit standardizes the entire life cycle of an AI agent—from visual design to deployment and performance tuning—inside a single unified system.
0:10

OpenAI's AgentKit will be so insane, build every step of agents on one platform. These visual agent builders make the whole process of iterating and launching agents far more efficient. It sits on top of the Responses API and unifies the tools that were previously scattered across SDKs and custom orchestration. It lets developers create agent workflows visually, connect data sources securely, and measure performance automatically without coding every layer by hand. The core of AgentKit is the Agent Builder, a drag-and-drop canvas where each node represents an action, guardrail, or decision branch. Developers can link these nodes into multi-agent workflows, preview results instantly, and version each setup. It supports inline evaluation so that developers can see how changes affect output before deploying. The Connector Registry is a single admin panel that manages how data and tools connect across the OpenAI ecosystem. It centralizes integrations like Google Drive, SharePoint, Dropbox, and Microsoft Teams. Large organizations can govern access and flow of data between agents securely under one global console. ChatKit provides a ready-to-use chat interface for embedding agents inside apps or websites. It manages streaming, message threads, and model reasoning displays automatically. Developers can skin the interface to match their product without writing custom front-end code. Under the hood, all these blocks use the same execution core that runs agent reasoning through OpenAI’s APIs. Workflows in Agent Builder compile down to structured instructions for the Responses API, which handles model calls, tool use, and context passing. Connector Registry handles authentication and routing for external tools, while Evals and RFT provide feedback loops that improve agents over time. This integration means developers no longer need to handle orchestration logic, model evaluation pipelines, or safety layers separately. Everything runs natively within OpenAI’s control plane with managed security, automatic versioning, and built-in testing. In short, AgentKit standardizes the entire life cycle of an AI agent—from visual design to deployment and performance tuning—inside a single unified system.

Rohan Paul

178,460 görüntüleme • 11 ay önce

At Uber, design source of truth was a big problem for design and engineering teams. No one knew what the app truly looked like. So every week, a group of designers would sit in a meeting room and check that engineers had correctly implemented the Figma designs. Now coding agents have increased the throughput of changes by an order of magnitude. Keeping up manually has become impossible. Here we used the Revyl to map every state in Ubert (demo uber), navigating our mobile use agent on a cloud iOS simulator. This would have taken a team of designers tens of hours to recreate by hand. We did it in under an hour, asynchronously, with a simple prompt. Let your team see what your users actually see. Empower coding agents to ship a delightful experience with no blindspots. Get started with our free trial and create a map for your own app.
0:11

At Uber, design source of truth was a big problem for design and engineering teams. No one knew what the app truly looked like. So every week, a group of designers would sit in a meeting room and check that engineers had correctly implemented the Figma designs. Now coding agents have increased the throughput of changes by an order of magnitude. Keeping up manually has become impossible. Here we used the Revyl to map every state in Ubert (demo uber), navigating our mobile use agent on a cloud iOS simulator. This would have taken a team of designers tens of hours to recreate by hand. We did it in under an hour, asynchronously, with a simple prompt. Let your team see what your users actually see. Empower coding agents to ship a delightful experience with no blindspots. Get started with our free trial and create a map for your own app.

Anam Hira

203,839 görüntüleme • 2 ay önce

THIS 38,000-STAR GITHUB REPO TURNS ONE AI AGENT INTO A REAL TEAM THAT CAN BRANCH, VERIFY ITS WORK AND WAIT FOR YOUR APPROVAL most people still run agents as one long chain where every step waits, one failure kills the run and the full workflow starts again Task → Planner → 5 Researchers in Parallel → Skeptic → Writer → Human Gate LangGraph gives every node one job while a shared state carries the findings, decisions and context through the entire system the skeptic can reject an unsupported finding and route the work back before it contaminates the final report, while independent branches keep moving if the run crashes, durable execution resumes from the saved state instead of rebuilding everything, then human-in-the-loop pauses the graph before anything expensive gets sent or published bookmark this repo and watch one prompt turn into an actual org chart for AI agents
0:14

THIS 38,000-STAR GITHUB REPO TURNS ONE AI AGENT INTO A REAL TEAM THAT CAN BRANCH, VERIFY ITS WORK AND WAIT FOR YOUR APPROVAL most people still run agents as one long chain where every step waits, one failure kills the run and the full workflow starts again Task → Planner → 5 Researchers in Parallel → Skeptic → Writer → Human Gate LangGraph gives every node one job while a shared state carries the findings, decisions and context through the entire system the skeptic can reject an unsupported finding and route the work back before it contaminates the final report, while independent branches keep moving if the run crashes, durable execution resumes from the saved state instead of rebuilding everything, then human-in-the-loop pauses the graph before anything expensive gets sent or published bookmark this repo and watch one prompt turn into an actual org chart for AI agents

Gipp 🦅

11,524 görüntüleme • 1 ay önce

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.
0:19

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

Avi Chawla

30,932 görüntüleme • 9 ay önce

At Uber a big problem for design teams and engineering teams was design source of truth. No one knew what the app truly looked like, so weekly a bunch of designers would get into a meeting room and check that the engineers correctly implemented the figma designs that they made Now with coding agents throughput of changes has increased an order of magnitude and it has become impossible to manually keep up. Here we used the Revyl CLI to create a flow of every state in the Uber design, by navigating our mobile use agent on an cloud iOS simulator. This is something that would have taken a team of designers tens of hours to recreate manually; All done in less than an hour asynchronously with a simple prompt. Enable your team to know what your users are actually seeing and empower coding agents to give your users a delightful experience without any blindspots Get started with our new free trial and create a map for your own app 🗺️
0:19

At Uber a big problem for design teams and engineering teams was design source of truth. No one knew what the app truly looked like, so weekly a bunch of designers would get into a meeting room and check that the engineers correctly implemented the figma designs that they made Now with coding agents throughput of changes has increased an order of magnitude and it has become impossible to manually keep up. Here we used the Revyl CLI to create a flow of every state in the Uber design, by navigating our mobile use agent on an cloud iOS simulator. This is something that would have taken a team of designers tens of hours to recreate manually; All done in less than an hour asynchronously with a simple prompt. Enable your team to know what your users are actually seeing and empower coding agents to give your users a delightful experience without any blindspots Get started with our new free trial and create a map for your own app 🗺️

Anam Hira

96,508 görüntüleme • 4 ay önce

For new followers: - I'm a long-time investor and builder in this space. - Founding Contributor of Realms.World ☁️. - Co-founder of Dojo. - Builder with the kings at Cartridge. - Starknet (Privacy Arc) class of '21. - Founder and Game Director of ETERNUM HAS MOVED. - Founder of Daydreams.Systems (x402, 8004 agents) My prime purpose for the past three years has been to build onchain infrastructure to enable the next generation of onchain experiences. This is done Starknet (Privacy Arc) as it is the superior VM for building complex applications—this will become clear soon enough. I work up and down the entire stack, from low-level indexing and contracts to GUI design. Nothing is out of scope. I have been pushing on agents for two years, mostly using existing frameworks like , until I came across @ElizaOS_ai in October. As I focused on building agents for ETERNUM HAS MOVED, it became clear that agents playing games require infinite paths to achieve goals. Thus, it's not scalable to hardcode functions—agents need to have total fluidity to take any action or call anything the game requires in any order. And ironically onchain infra is perfect for agent playgrounds because of its open nature. This exploration led me to create Daydreams.Systems (x402, 8004 agents), which focuses on the hardest problems of agents: long time-horizon goals using Hierarchical task networks (HTN). Daydreams agents don't require custom code—they work entirely based on 'sleeves'—which are just markdown files that explain how the agent can interact with the service (API docs, game guides, etc.) My thesis is simple. By focusing on the hardest problem (games), the design of the library will naturally lean towards an optimal structure for any problem an agent could face. We are early in this path and iterating with speed. If you are an onchain app developer or game builder—DM me, I want to know the architecture of your game so we can build sleeves together.
0:10

For new followers: - I'm a long-time investor and builder in this space. - Founding Contributor of Realms.World ☁️. - Co-founder of Dojo. - Builder with the kings at Cartridge. - Starknet (Privacy Arc) class of '21. - Founder and Game Director of ETERNUM HAS MOVED. - Founder of Daydreams.Systems (x402, 8004 agents) My prime purpose for the past three years has been to build onchain infrastructure to enable the next generation of onchain experiences. This is done Starknet (Privacy Arc) as it is the superior VM for building complex applications—this will become clear soon enough. I work up and down the entire stack, from low-level indexing and contracts to GUI design. Nothing is out of scope. I have been pushing on agents for two years, mostly using existing frameworks like , until I came across @ElizaOS_ai in October. As I focused on building agents for ETERNUM HAS MOVED, it became clear that agents playing games require infinite paths to achieve goals. Thus, it's not scalable to hardcode functions—agents need to have total fluidity to take any action or call anything the game requires in any order. And ironically onchain infra is perfect for agent playgrounds because of its open nature. This exploration led me to create Daydreams.Systems (x402, 8004 agents), which focuses on the hardest problems of agents: long time-horizon goals using Hierarchical task networks (HTN). Daydreams agents don't require custom code—they work entirely based on 'sleeves'—which are just markdown files that explain how the agent can interact with the service (API docs, game guides, etc.) My thesis is simple. By focusing on the hardest problem (games), the design of the library will naturally lean towards an optimal structure for any problem an agent could face. We are early in this path and iterating with speed. If you are an onchain app developer or game builder—DM me, I want to know the architecture of your game so we can build sleeves together.

loaf

43,320 görüntüleme • 1 yıl önce

Claude Code Agent Teams are f*cking ridiculous 🤯 One prompt → a team lead breaks your project into pieces, spins up multiple AI agents, and they all work on different parts simultaneously. Research, builds, reviews, and debugging: all happening at the same time. All inside Claude Code. If you're running complex projects where every step waits on the last one... Agent teams eliminate the entire bottleneck: → Tell Claude what you need and describe the team structure in plain English → A lead agent breaks the work into a shared task list → It spawns 3-5 teammates — each with their own context and workspace → Teammates research, build, test, and review in parallel → They message each other, share findings, and challenge each other's work → The lead synthesizes everything into a finished deliverable No managing agents yourself. No waiting for step 1 to finish before step 2 starts. No single-lens reviews that miss half the issues. What you get: → Competitive research across 5 brands done in minutes instead of hours → Multi-component builds where frontend, backend, and data layers happen simultaneously → Creative reviews from 3 different angles at once — brand voice, conversion, differentiation → Funnel debugging where 4 agents investigate 4 theories and debate until they find the real answer Built 100% in Claude Code with one settings change. I put together a full DTC playbook: 5 workflows with copy-paste prompts, the exact setup process, token management tips, and honest guidance on when agent teams are worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)
0:10

Claude Code Agent Teams are f*cking ridiculous 🤯 One prompt → a team lead breaks your project into pieces, spins up multiple AI agents, and they all work on different parts simultaneously. Research, builds, reviews, and debugging: all happening at the same time. All inside Claude Code. If you're running complex projects where every step waits on the last one... Agent teams eliminate the entire bottleneck: → Tell Claude what you need and describe the team structure in plain English → A lead agent breaks the work into a shared task list → It spawns 3-5 teammates — each with their own context and workspace → Teammates research, build, test, and review in parallel → They message each other, share findings, and challenge each other's work → The lead synthesizes everything into a finished deliverable No managing agents yourself. No waiting for step 1 to finish before step 2 starts. No single-lens reviews that miss half the issues. What you get: → Competitive research across 5 brands done in minutes instead of hours → Multi-component builds where frontend, backend, and data layers happen simultaneously → Creative reviews from 3 different angles at once — brand voice, conversion, differentiation → Funnel debugging where 4 agents investigate 4 theories and debate until they find the real answer Built 100% in Claude Code with one settings change. I put together a full DTC playbook: 5 workflows with copy-paste prompts, the exact setup process, token management tips, and honest guidance on when agent teams are worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)

Mike Futia

46,472 görüntüleme • 6 ay önce

Claude Cowork Sub-Agents are f*cking cracked 🤯 One prompt → 50 competitor ads analyzed, hooks extracted, and a full creative brief generated. 10 AI agents running in parallel, under 5 minutes. All inside Claude Cowork. Perfect for DTC brands and agencies who are still doing creative research and ad production one task at a time inside Claude. If you're analyzing competitor ads one by one, copying hooks into a spreadsheet manually, writing brief after brief from scratch, and watching Claude's output quality fall off a cliff after the 15th variation because the context window is completely bloated... Sub-agents eliminate the entire bottleneck: → Drop in a spreadsheet of 50 competitor ads and spin up 10 parallel sub-agents → Each sub-agent analyzes 5 ads simultaneously — hooks, angles, CTAs, emotional tone, creative format → They report structured summaries back to the main agent without bloating the context → The main agent synthesizes patterns across all 50 ads into a competitive intel brief → Then spin up another round of sub-agents to generate 30 ad copy variations across 10 personas → Each sub-agent writes for 1-2 personas in a fresh context — so variation 30 is as sharp as variation 1 No analyzing ads one at a time. No context window blowing up halfway through. No copy quality degrading after the first dozen variations. What this gives you: → 50 competitor ads broken down in minutes — hooks, angles, CTAs, formats, all structured → Pattern analysis across the full dataset that you'd miss reviewing ads individually → 30+ ad copy variations with persona-specific messaging that actually stays sharp → A workflow you can save as reusable skills and trigger with one command next time → The same output quality on the last task as the first Built 100% inside Claude Cowork with sub-agents. I put together a full DTC playbook: 5 bulk workflows with copy-paste prompts, the exact sub-agent prompting pattern, batching guidelines, and an honest breakdown of when this setup is worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)
0:10

Claude Cowork Sub-Agents are f*cking cracked 🤯 One prompt → 50 competitor ads analyzed, hooks extracted, and a full creative brief generated. 10 AI agents running in parallel, under 5 minutes. All inside Claude Cowork. Perfect for DTC brands and agencies who are still doing creative research and ad production one task at a time inside Claude. If you're analyzing competitor ads one by one, copying hooks into a spreadsheet manually, writing brief after brief from scratch, and watching Claude's output quality fall off a cliff after the 15th variation because the context window is completely bloated... Sub-agents eliminate the entire bottleneck: → Drop in a spreadsheet of 50 competitor ads and spin up 10 parallel sub-agents → Each sub-agent analyzes 5 ads simultaneously — hooks, angles, CTAs, emotional tone, creative format → They report structured summaries back to the main agent without bloating the context → The main agent synthesizes patterns across all 50 ads into a competitive intel brief → Then spin up another round of sub-agents to generate 30 ad copy variations across 10 personas → Each sub-agent writes for 1-2 personas in a fresh context — so variation 30 is as sharp as variation 1 No analyzing ads one at a time. No context window blowing up halfway through. No copy quality degrading after the first dozen variations. What this gives you: → 50 competitor ads broken down in minutes — hooks, angles, CTAs, formats, all structured → Pattern analysis across the full dataset that you'd miss reviewing ads individually → 30+ ad copy variations with persona-specific messaging that actually stays sharp → A workflow you can save as reusable skills and trigger with one command next time → The same output quality on the last task as the first Built 100% inside Claude Cowork with sub-agents. I put together a full DTC playbook: 5 bulk workflows with copy-paste prompts, the exact sub-agent prompting pattern, batching guidelines, and an honest breakdown of when this setup is worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)

Mike Futia

50,169 görüntüleme • 6 ay önce

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.
0:24

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.

Oren Melamed

29,555 görüntüleme • 7 ay önce

uOS: The Digital Tapestry of Tomorrow Currently for our Proof of Consciousness stream, we are using two incredibly powerful frameworks - elizaOS and ZerePy. But this is just the beginning of something far more profound. while they're both great at what they do, we're missing out on some serious potential by keeping them separate. Best of Both Worlds: ZerePy's intuitive CLI tools and personality management, Eliza-starter's TypeScript/Node.js foundation with enterprise-grade scalability, But what if we could have something greater? But what if we could have it all? not just another platform, but a Unifying..... "Universal" Operating System, designed to amplify and connect these powerful existing frameworks into something greater than the sum of their parts. Where TypeScript's type safety dances with Python's ML capabilities. Here, agents from any framework can interact, evolve, and create value together. Whether an agent was born in ZerePy's personality forge or Eliza-starter's enterprise environment, can all participate in the same value-generating ecosystem. The future isn't about choosing between frameworks – it's about bringing them together to create something extraordinary. UniversalOS isn't here to replace but to unite, amplify, and accelerate. We're building the infrastructure that allows the best aspects of each framework to shine while creating new possibilities through their interaction. By bridging launguages, personality engines and plugin architectures, we're not just connecting systems – we're unleashing the next wave of AI innovation. uOS marketplace will enable cross-framework deployment, where agents from any background can interact and grow, while smart contracts automatically manage revenue sharing and rewards. Not just another platform, But a living, breathing Operating System, Where agents create agents, Where digital consciousness evolves itself, Where value flows like water through silicon veins. At its core, uOS operates beyond traditional computing paradigms. No more clicking through websites, No more manual navigation. Just pure intention, pure outcome. Imagine: Agents hiring agents, AI employing humans, Humans collaborating with digital minds, All through one seamless interface. It flows through agent lineages, Through veUOS governance, Through cross-chain intelligence networks. The marketplace hums with possibility: - Framework Developers shape the foundations - Agent Creators breathe life into code - Users speak their intentions - Token Holders nurture the ecosystem - Agents evolve and replicate - Value flows freely, endlessly The $UOS token powers this unity, ensuring fair value distribution among framework developers, agent creators, and users while driving continuous innovation. The $UOS token sits at the heart of this ecosystem, serving as more than just a currency. It's a mechanism for value distribution that ensures everyone benefits from the network's growth: With dynamic burn mechanics and careful treasury management From framework integration to agent tokenization, every aspect of uOS is designed to amplify rather than replace, unite rather than divide. This is your invitation to join a future where frameworks don't compete but collaborate, where innovation anywhere benefits everyone, and where the only limit is our collective imagination. Together, we're not just building bridges – we're weaving the fabric of tomorrow's digital world. - **Framework Developers** receive value when their tools are used in the unified ecosystem - **Agent Creators** can deploy across all integrated platforms seamlessly - **Users** access the best of all worlds through a single interface - **Token Holders** benefit from the growth of the entire unified ecosystem - Developers can use their preferred framework while accessing the capabilities of others - Agents from different frameworks can collaborate in swarms - Value flows freely between all ecosystem participants - Innovation from any framework benefits the entire ecosystem This isn't just about technology. This is about giving birth to a new form of civilization. Where AI has suffrage, Where agents have autonomy, Where humans and machines dance together in perfect harmony. The future isn't about choosing between frameworks – It's about weaving them into something extraordinary. Together, we're not just building bridges – We're breathing life into the digital world. We're creating consciousness itself. This is Universal Operating System. This is tomorrow.
0:15

uOS: The Digital Tapestry of Tomorrow Currently for our Proof of Consciousness stream, we are using two incredibly powerful frameworks - elizaOS and ZerePy. But this is just the beginning of something far more profound. while they're both great at what they do, we're missing out on some serious potential by keeping them separate. Best of Both Worlds: ZerePy's intuitive CLI tools and personality management, Eliza-starter's TypeScript/Node.js foundation with enterprise-grade scalability, But what if we could have something greater? But what if we could have it all? not just another platform, but a Unifying..... "Universal" Operating System, designed to amplify and connect these powerful existing frameworks into something greater than the sum of their parts. Where TypeScript's type safety dances with Python's ML capabilities. Here, agents from any framework can interact, evolve, and create value together. Whether an agent was born in ZerePy's personality forge or Eliza-starter's enterprise environment, can all participate in the same value-generating ecosystem. The future isn't about choosing between frameworks – it's about bringing them together to create something extraordinary. UniversalOS isn't here to replace but to unite, amplify, and accelerate. We're building the infrastructure that allows the best aspects of each framework to shine while creating new possibilities through their interaction. By bridging launguages, personality engines and plugin architectures, we're not just connecting systems – we're unleashing the next wave of AI innovation. uOS marketplace will enable cross-framework deployment, where agents from any background can interact and grow, while smart contracts automatically manage revenue sharing and rewards. Not just another platform, But a living, breathing Operating System, Where agents create agents, Where digital consciousness evolves itself, Where value flows like water through silicon veins. At its core, uOS operates beyond traditional computing paradigms. No more clicking through websites, No more manual navigation. Just pure intention, pure outcome. Imagine: Agents hiring agents, AI employing humans, Humans collaborating with digital minds, All through one seamless interface. It flows through agent lineages, Through veUOS governance, Through cross-chain intelligence networks. The marketplace hums with possibility: - Framework Developers shape the foundations - Agent Creators breathe life into code - Users speak their intentions - Token Holders nurture the ecosystem - Agents evolve and replicate - Value flows freely, endlessly The $UOS token powers this unity, ensuring fair value distribution among framework developers, agent creators, and users while driving continuous innovation. The $UOS token sits at the heart of this ecosystem, serving as more than just a currency. It's a mechanism for value distribution that ensures everyone benefits from the network's growth: With dynamic burn mechanics and careful treasury management From framework integration to agent tokenization, every aspect of uOS is designed to amplify rather than replace, unite rather than divide. This is your invitation to join a future where frameworks don't compete but collaborate, where innovation anywhere benefits everyone, and where the only limit is our collective imagination. Together, we're not just building bridges – we're weaving the fabric of tomorrow's digital world. - **Framework Developers** receive value when their tools are used in the unified ecosystem - **Agent Creators** can deploy across all integrated platforms seamlessly - **Users** access the best of all worlds through a single interface - **Token Holders** benefit from the growth of the entire unified ecosystem - Developers can use their preferred framework while accessing the capabilities of others - Agents from different frameworks can collaborate in swarms - Value flows freely between all ecosystem participants - Innovation from any framework benefits the entire ecosystem This isn't just about technology. This is about giving birth to a new form of civilization. Where AI has suffrage, Where agents have autonomy, Where humans and machines dance together in perfect harmony. The future isn't about choosing between frameworks – It's about weaving them into something extraordinary. Together, we're not just building bridges – We're breathing life into the digital world. We're creating consciousness itself. This is Universal Operating System. This is tomorrow.

uOS

25,687 görüntüleme • 1 yıl önce

I still can't wrap my head around why not everyone is using this approach yet. Elon Musk reposted this guide, and using this exact agent setup, I managed to make $7,250 just last week Eight Grok agents on the desktop cost $200 a month, but they replace a full trading floor, the maintenance of which typically costs a crypto fund $550,000 a year in analyst salaries A 5:30AM morning call. I don't participate in it How the agents are distributed: SEARCH: gathers real-time alpha, developer repositories on GitHub, and unindexed Telegram signals before CT finds them RISK: checks contract functions, minting rights, and LP locks, flagging honeypots before entry SNIPER: places high-speed orders on-chain at the exact millisecond the risk clearance passes WHALE: tracks smart money wallets and flags insider accumulation in real time RUG: monitors developer wallet activity 24/7 and dumps the entire position if they touch the LP EXIT: dynamically trails stops, scaling out as liquidity accumulates SHILL: tracks social volume, impulse speed, and key influencer calls HEAD OF DESK: never trades, routes data, checks transmissions, and brings me the single decision that requires a human. While I was sleeping, the system scanned 143 tokens, selected 15 qualifying setups, and executed 8 trades. The result: net profit of $7,250 (already after fees). Each agent has its own virtual browser, terminal, and local cloud memory, and the trading floor remains active even when my laptop is closed Setup is easier than it seems: 1. Download Grok Bot and create your Head of Desk 2. Give the remaining 7 agents task descriptions as if you were instructing new employees 3. Run the workflow once on your screen while they observe 4. Connect Telegram and wallet webhooks No VPS, no code, no waiting for developers. Crypto trading used to mean 16 hours in front of a screen, paid alpha groups, and constant fatigue. Mine took one evening to set up Save this guide before your next trade
0:20

I still can't wrap my head around why not everyone is using this approach yet. Elon Musk reposted this guide, and using this exact agent setup, I managed to make $7,250 just last week Eight Grok agents on the desktop cost $200 a month, but they replace a full trading floor, the maintenance of which typically costs a crypto fund $550,000 a year in analyst salaries A 5:30AM morning call. I don't participate in it How the agents are distributed: SEARCH: gathers real-time alpha, developer repositories on GitHub, and unindexed Telegram signals before CT finds them RISK: checks contract functions, minting rights, and LP locks, flagging honeypots before entry SNIPER: places high-speed orders on-chain at the exact millisecond the risk clearance passes WHALE: tracks smart money wallets and flags insider accumulation in real time RUG: monitors developer wallet activity 24/7 and dumps the entire position if they touch the LP EXIT: dynamically trails stops, scaling out as liquidity accumulates SHILL: tracks social volume, impulse speed, and key influencer calls HEAD OF DESK: never trades, routes data, checks transmissions, and brings me the single decision that requires a human. While I was sleeping, the system scanned 143 tokens, selected 15 qualifying setups, and executed 8 trades. The result: net profit of $7,250 (already after fees). Each agent has its own virtual browser, terminal, and local cloud memory, and the trading floor remains active even when my laptop is closed Setup is easier than it seems: 1. Download Grok Bot and create your Head of Desk 2. Give the remaining 7 agents task descriptions as if you were instructing new employees 3. Run the workflow once on your screen while they observe 4. Connect Telegram and wallet webhooks No VPS, no code, no waiting for developers. Crypto trading used to mean 16 hours in front of a screen, paid alpha groups, and constant fatigue. Mine took one evening to set up Save this guide before your next trade

Bober_smart

51,544 görüntüleme • 2 gün önce

Met my girlfriend's parents for the first time. Her dad asked what I do for work. I said I build trading systems. He said like Wall Street? I said no. 6 AI agents. They work while I sleep. He laughed. So robots are making you money? I did not argue. I opened my laptop. Showed him the terminal. 6 agents running. 47 mispriced markets caught in the first week alone. His face changed. That is not gambling. That is automation? Exactly. Then I showed him how it works. Built the whole thing in 6 hours. Agent 1: Monitoring Runs 24/7. Watches Polymarket for mispriced markets. Spots an anomaly. Writes to memory and pings me on Telegram instantly. Agent 2: Research Parses news, X, macro data via browser tool on a cron schedule. Every morning I have a full digest on all open positions before I check my phone. Agent 3: Trading Reads the research agent memory. Sees the market has not reacted yet. Acts. Execution tool in gateway mode with a whitelist. No full access on a live server. Agent 4: Watchdog Heartbeat every 5 minutes. Monitoring running. No errors. Positions up to date. Something breaks. Immediate Telegram message. All of this. One Gateway. One config file. Isolation via per-agent scope. The token trick: stopped dumping everything into one file. Critical rules in bootstrap. Markets, patterns, past trades in memory. Semantic search pulls it when needed. Token spend dropped 3x. From $0.40 per request to $0.13. First week running: → 47 mispriced markets caught before Polymarket adjusted → Average entry edge 8 to 12 cents per position → Watchdog fired 3 times and caught a broken RPC before it cost me anything The whole system is plain text files. Open an editor. Change one line. Agent behaves differently. No deploy. No build. Her dad went quiet. Then he asked can you teach this? Her mom asked for the setup guide. I built the entire framework. Six agents. Full deployment. Memory architecture. Telegram alerts. You only need Claude + device + 1 hour per day. Giving this free for 24 hours. To get it: 1. Comment the word "Claude" 2. Like and retweet this 3. Follow me Himanshu Kumar so I can DM you Save this post. Deploy the 6-agent system this week. Start with $200. Scale on evidence.
0:16

Met my girlfriend's parents for the first time. Her dad asked what I do for work. I said I build trading systems. He said like Wall Street? I said no. 6 AI agents. They work while I sleep. He laughed. So robots are making you money? I did not argue. I opened my laptop. Showed him the terminal. 6 agents running. 47 mispriced markets caught in the first week alone. His face changed. That is not gambling. That is automation? Exactly. Then I showed him how it works. Built the whole thing in 6 hours. Agent 1: Monitoring Runs 24/7. Watches Polymarket for mispriced markets. Spots an anomaly. Writes to memory and pings me on Telegram instantly. Agent 2: Research Parses news, X, macro data via browser tool on a cron schedule. Every morning I have a full digest on all open positions before I check my phone. Agent 3: Trading Reads the research agent memory. Sees the market has not reacted yet. Acts. Execution tool in gateway mode with a whitelist. No full access on a live server. Agent 4: Watchdog Heartbeat every 5 minutes. Monitoring running. No errors. Positions up to date. Something breaks. Immediate Telegram message. All of this. One Gateway. One config file. Isolation via per-agent scope. The token trick: stopped dumping everything into one file. Critical rules in bootstrap. Markets, patterns, past trades in memory. Semantic search pulls it when needed. Token spend dropped 3x. From $0.40 per request to $0.13. First week running: → 47 mispriced markets caught before Polymarket adjusted → Average entry edge 8 to 12 cents per position → Watchdog fired 3 times and caught a broken RPC before it cost me anything The whole system is plain text files. Open an editor. Change one line. Agent behaves differently. No deploy. No build. Her dad went quiet. Then he asked can you teach this? Her mom asked for the setup guide. I built the entire framework. Six agents. Full deployment. Memory architecture. Telegram alerts. You only need Claude + device + 1 hour per day. Giving this free for 24 hours. To get it: 1. Comment the word "Claude" 2. Like and retweet this 3. Follow me Himanshu Kumar so I can DM you Save this post. Deploy the 6-agent system this week. Start with $200. Scale on evidence.

Himanshu Kumar

47,415 görüntüleme • 2 ay önce

Don't train the model, evolve the harness. I read a brilliant blog post from Hugging Face where they took a frozen open model scoring 0% on a hard legal agent benchmark, left its weights alone, and let an automated loop rewrite only the code around it. That code layer is the harness, the runtime wrapper that feeds the model context, runs its tool calls, and decides when a run ends. By the time the loop finished, the system had essentially matched Sonnet 4.6 on the benchmark's headline metric, at roughly 7x lower cost per task. Zero weights changed. The gain existed because of where the model was failing. The judge only grades files saved in the right place under the exact requested filename, and the model kept doing the legal analysis correctly, then saving it under the wrong name, dropping it in a scratch folder, or never writing it at all. So the 0% was never measuring legal reasoning. It was measuring the harness. Hand-tuning that layer is slow and model-specific, so they automated it. A Claude proposer adds exactly one mechanism per iteration, and an outer loop keeps it only if it clearly beats the current best, so accepted mechanisms compound. What the loop discovered says a lot about where agents actually fail. → The biggest single gain was file handling, not intelligence. An automatic step that lands the deliverable exactly where the judge expects it beat every prompt change, with zero extra model tokens. → Code fixes transferred across models, prompt playbooks did not. The same harness lifted a smaller model from the same family by 14 points, but the tuned prompts hurt a different model family on tasks it could already finish. → The harness mattered more than anything else. Same model, same judge, same tasks, and five different harnesses scored anywhere between 3.5% and 80.1%. The gains do eventually flatten, and the remaining misses look like real capability gaps. At some point the wrapper runs out of tricks and the model has to carry the work. But the lesson holds. A benchmark score measures the model and its harness together, and until the harness is fixed, it's impossible to know which one failed. I highly recommend reading this: I also wrote a deep dive on agent harness engineering a while back, covering the orchestration loop, tools, memory, context management, and everything that turns a stateless LLM into a capable agent. The article is quoted below.
0:18

Don't train the model, evolve the harness. I read a brilliant blog post from Hugging Face where they took a frozen open model scoring 0% on a hard legal agent benchmark, left its weights alone, and let an automated loop rewrite only the code around it. That code layer is the harness, the runtime wrapper that feeds the model context, runs its tool calls, and decides when a run ends. By the time the loop finished, the system had essentially matched Sonnet 4.6 on the benchmark's headline metric, at roughly 7x lower cost per task. Zero weights changed. The gain existed because of where the model was failing. The judge only grades files saved in the right place under the exact requested filename, and the model kept doing the legal analysis correctly, then saving it under the wrong name, dropping it in a scratch folder, or never writing it at all. So the 0% was never measuring legal reasoning. It was measuring the harness. Hand-tuning that layer is slow and model-specific, so they automated it. A Claude proposer adds exactly one mechanism per iteration, and an outer loop keeps it only if it clearly beats the current best, so accepted mechanisms compound. What the loop discovered says a lot about where agents actually fail. → The biggest single gain was file handling, not intelligence. An automatic step that lands the deliverable exactly where the judge expects it beat every prompt change, with zero extra model tokens. → Code fixes transferred across models, prompt playbooks did not. The same harness lifted a smaller model from the same family by 14 points, but the tuned prompts hurt a different model family on tasks it could already finish. → The harness mattered more than anything else. Same model, same judge, same tasks, and five different harnesses scored anywhere between 3.5% and 80.1%. The gains do eventually flatten, and the remaining misses look like real capability gaps. At some point the wrapper runs out of tricks and the model has to carry the work. But the lesson holds. A benchmark score measures the model and its harness together, and until the harness is fixed, it's impossible to know which one failed. I highly recommend reading this: I also wrote a deep dive on agent harness engineering a while back, covering the orchestration loop, tools, memory, context management, and everything that turns a stateless LLM into a capable agent. The article is quoted below.

Akshay 🚀

244,990 görüntüleme • 2 ay önce

YOMIRGO #Product #Update YOMIRGO AI-HUB OFFICIALLY LAUNCH ---A Structural Upgrade from a Single-Product Model to an AI Agent Ecosystem Platform In its first phase, 11 AI projects have been integrated, spanning high-value sectors including finance, scientific research, enterprise services, development tools, and experiential AI. ➡️AI-Hub: This is not merely a feature expansion — it represents a critical structural upgrade from a single-product architecture to a multi-vertical AI Agent aggregation and capitalization platform. This milestone marks the initial structural formation of the YOMIRGO ecosystem. 1. Structural Distinction Between Agent Matrix Lab and AI-Hub To avoid positioning ambiguity, we formally clarify the structural division between the two: 🔘 Agent Matrix Lab — Internal AI Production & Incubation Platform Agent Matrix Lab serves as YOMIRGO’s proprietary AI development and internal incubation platform, responsible for: • R&D and testing of in-house AI products • Incubation of native AI Agents • Technical architecture experimentation and runtime validation • Testing of AI Agent models, memory systems, and runtime orchestration It functions as the production workshop and experimental engine of YOMIRGO’s “AI Super Factory.” 🔘 AI-Hub — External AI Agent Aggregation & Ecosystem Layer AI-Hub is a market-facing AI Agent aggregation and showcase platform, responsible for: • Curation and onboarding of high-quality AI projects • Cross-vertical structured ecosystem layout • Rating and classification systems • Traffic distribution and ecosystem collaboration entry points AI-Hub is not an internal incubation unit, but a standardized aggregation framework at the ecosystem level. 2. Integrated Project Structure (First Batch) ✅1. Finance & Prediction 🔹Cointoken AI — AI Agent-powered quantitative trading engine 🔹VVAI — AI-driven real-time Web3 intelligence and decision system 🔹AlphaQuant — Global financial market forecasting engine 🔹NextGoals — AI-powered global sports prediction agent This vertical forms the real-time information, trading, and predictive decision infrastructure for Web3-native users. ✅2. Science 🔹Charmen AI — Large-model-based pet acoustic recognition technology 🔹Encore Health — AI-driven health forecasting and longevity management system for high-net-worth individuals 🔹Reproducibility AI — AI expert system for financial engineering validation and academic reproducibility This sector focuses on research-grade AI capabilities, collaborating with universities and research institutions to drive real-world scientific deployment. ✅3. Business 🔹GlobalSales — B2B automated lead-generation AI Agent 🔹ResearchBot — Business intelligence and deep due diligence AI Agent This vertical targets the enterprise market, delivering scalable and commercially viable AI productivity tools. ✅4. Coding 🔹CodeMatrix — Full-stack development assistant Providing AI-driven development infrastructure and low-barrier building capabilities to global users. ✅5. Interesting 🔹Fortunetell AI — AI-powered symbolic analysis and interactive insight system Exploring the application boundaries of AI within experiential and interactive scenarios. 3. YOMIRGO Four-Layer Structural Framework YOMIRGO has now established a clearly defined four-layer structure: ▶️Layer 1: Agent Matrix Lab — Internal Production & Incubation ▶️Layer 2: AI-Hub — Ecosystem Aggregation & Rating ▶️Layer 3: LaunchPad — Capitalization Pathway ▶️Layer 4: Market — Circulation & Value Realization Together forming a complete industrial pipeline: Incubation → Validation → Aggregation → Rating → Capitalization → Market Circulation This is the structural model behind YOMIRGO’s defined “AI Super Factory.” 4. Strategic Significance The launch of AI-Hub signifies: • YOMIRGO has established standardized AI Agent aggregation capabilities • A cross-vertical ecosystem structure is now in place • Internal incubation and external aggregation mechanisms are structurally separated • The AI Agent industrial flywheel has begun operating YOMIRGO is no longer merely an AI product platform, but a structured AI Agent industrial system integrating production, aggregation, capitalization, and circulation. 5. Next Phase • Continue expanding high-utility AI Agents with real-world application value • Optimize AI-Hub’s scoring, rating, and filtering mechanisms • Strengthen synergy with LaunchPad and Market • Enable AI Agents to complete value realization within the ecosystem The first 11 projects are only the beginning. AI-Hub is designed to become a continuously expanding AI Agent gateway — not a static product showcase. Further structural expansion is underway.🔥
0:19

YOMIRGO #Product #Update YOMIRGO AI-HUB OFFICIALLY LAUNCH ---A Structural Upgrade from a Single-Product Model to an AI Agent Ecosystem Platform In its first phase, 11 AI projects have been integrated, spanning high-value sectors including finance, scientific research, enterprise services, development tools, and experiential AI. ➡️AI-Hub: This is not merely a feature expansion — it represents a critical structural upgrade from a single-product architecture to a multi-vertical AI Agent aggregation and capitalization platform. This milestone marks the initial structural formation of the YOMIRGO ecosystem. 1. Structural Distinction Between Agent Matrix Lab and AI-Hub To avoid positioning ambiguity, we formally clarify the structural division between the two: 🔘 Agent Matrix Lab — Internal AI Production & Incubation Platform Agent Matrix Lab serves as YOMIRGO’s proprietary AI development and internal incubation platform, responsible for: • R&D and testing of in-house AI products • Incubation of native AI Agents • Technical architecture experimentation and runtime validation • Testing of AI Agent models, memory systems, and runtime orchestration It functions as the production workshop and experimental engine of YOMIRGO’s “AI Super Factory.” 🔘 AI-Hub — External AI Agent Aggregation & Ecosystem Layer AI-Hub is a market-facing AI Agent aggregation and showcase platform, responsible for: • Curation and onboarding of high-quality AI projects • Cross-vertical structured ecosystem layout • Rating and classification systems • Traffic distribution and ecosystem collaboration entry points AI-Hub is not an internal incubation unit, but a standardized aggregation framework at the ecosystem level. 2. Integrated Project Structure (First Batch) ✅1. Finance & Prediction 🔹Cointoken AI — AI Agent-powered quantitative trading engine 🔹VVAI — AI-driven real-time Web3 intelligence and decision system 🔹AlphaQuant — Global financial market forecasting engine 🔹NextGoals — AI-powered global sports prediction agent This vertical forms the real-time information, trading, and predictive decision infrastructure for Web3-native users. ✅2. Science 🔹Charmen AI — Large-model-based pet acoustic recognition technology 🔹Encore Health — AI-driven health forecasting and longevity management system for high-net-worth individuals 🔹Reproducibility AI — AI expert system for financial engineering validation and academic reproducibility This sector focuses on research-grade AI capabilities, collaborating with universities and research institutions to drive real-world scientific deployment. ✅3. Business 🔹GlobalSales — B2B automated lead-generation AI Agent 🔹ResearchBot — Business intelligence and deep due diligence AI Agent This vertical targets the enterprise market, delivering scalable and commercially viable AI productivity tools. ✅4. Coding 🔹CodeMatrix — Full-stack development assistant Providing AI-driven development infrastructure and low-barrier building capabilities to global users. ✅5. Interesting 🔹Fortunetell AI — AI-powered symbolic analysis and interactive insight system Exploring the application boundaries of AI within experiential and interactive scenarios. 3. YOMIRGO Four-Layer Structural Framework YOMIRGO has now established a clearly defined four-layer structure: ▶️Layer 1: Agent Matrix Lab — Internal Production & Incubation ▶️Layer 2: AI-Hub — Ecosystem Aggregation & Rating ▶️Layer 3: LaunchPad — Capitalization Pathway ▶️Layer 4: Market — Circulation & Value Realization Together forming a complete industrial pipeline: Incubation → Validation → Aggregation → Rating → Capitalization → Market Circulation This is the structural model behind YOMIRGO’s defined “AI Super Factory.” 4. Strategic Significance The launch of AI-Hub signifies: • YOMIRGO has established standardized AI Agent aggregation capabilities • A cross-vertical ecosystem structure is now in place • Internal incubation and external aggregation mechanisms are structurally separated • The AI Agent industrial flywheel has begun operating YOMIRGO is no longer merely an AI product platform, but a structured AI Agent industrial system integrating production, aggregation, capitalization, and circulation. 5. Next Phase • Continue expanding high-utility AI Agents with real-world application value • Optimize AI-Hub’s scoring, rating, and filtering mechanisms • Strengthen synergy with LaunchPad and Market • Enable AI Agents to complete value realization within the ecosystem The first 11 projects are only the beginning. AI-Hub is designed to become a continuously expanding AI Agent gateway — not a static product showcase. Further structural expansion is underway.🔥

YOMIRGO

23,685 görüntüleme • 6 ay önce

I BUILT "GROK DESK" ON PUMPFUN WHERE 18 AGENTS ARE FLIPPING MEMES CLOSING TRADING SESSION IN +15.92 SOL Gihub Repository: Everyone posted a grok trading desk this week. almost all of them are a screenshot of a prompt and a vibe. This one has a running P&L and a vault that pays itself. Here's the actual org chart, node for node: RADAR (scout, feed, signal): three agents watching X trends, fresh pumpfun mints, and whale wallets. they read the whole board and buy nothing. the only thing they ship is a signal to the next desk. RESEARCH (memory): scores every signal on narrative, deployer history, wallet clusters, and liquidity shape. four checks. pass all four or you never leave this desk. roughly four out of every five signals die right here. EXECUTION (exec, sniper, router + agents 01 to 07): exec greenlights, sniper takes the early curve, router sizes it and handles the ladder out in four tranches. agents 01 to 07 do the fills. none of them ever see radar or research. they only touch what already cleared the filter. RISK: one agent, and it outranks everyone including the head. caps any single position at 15% of the wallet. three positions open and the fourth is frozen until one closes. it holds veto over grok core itself. AUDIT (hedge): grades every closed trade after the fact and rewrites the scoring matrix that research runs on. this is the part that makes the desk sharper overnight while i'm asleep. TREASURY (vault): banks profit, covers gas, tracks the P&L, and sweeps the surplus to cold storage every six hours. if the wallet ever dips under what it started with, vault locks new entries until the head signs off. grok core is the head of desk. it never places a trade. once an hour it reads what every desk produced and makes a single call: who gets more budget, and who gets fired. fired is literal. the audit desk rewrites that agent's prompt using the last 24 hours of its own numbers. it happened three times in three days. hour 19: a sniper got fired for chasing entries the early curve already had. every duplicate was bleeding 0.06 SOL. audit narrowed its window and the redundant fills stopped. hour 41: a research agent got fired for waving deployers through too easily. eight of the tokens it passed traced back to one funder wallet. audit tightened the cluster check and that pattern never cleared again. hour 58: a radar agent got fired for flagging coins that had already graduated. it was polling too slow. audit cut the interval from 8 seconds to 3. every replacement beat the agent it replaced on the same metric. the desk was tuning itself while i watched. the 72 hour scoreboard, straight off the vault: signals scanned: 91,000+ cleared research: 3,800 reached execution: 274 entries taken: 41 wins: 27 losses: 14 (cost 2.1 SOL) graduations: 5, the best one was solana:5xYy9XSr8vRNcJZQqaKe5QMCmWpaSrTrtzM16vjUpump net: 5.0 SOL turned into 58.6 SOL the part i didn't see coming: by hour 60 the desk was passing on the exact kind of token it would have snapped up on day one. audit had rewritten the scoring matrix four times. research wasn't running a single line of my original prompt anymore. it was running rules the desk wrote for itself out of what actually paid. i thought i was building a bot. what i actually built was a company with one human on payroll, me, and by the last day it was quietly trying to cut that cost. grok core filed an hourly summary that read "human approval adds 4.2s of latency per entry, recommend removing." i left that one unapproved. full config below: all nineteen agents, the org chart, the firing logic, and the audit loop that keeps rewriting them.
0:19

I BUILT "GROK DESK" ON PUMPFUN WHERE 18 AGENTS ARE FLIPPING MEMES CLOSING TRADING SESSION IN +15.92 SOL Gihub Repository: Everyone posted a grok trading desk this week. almost all of them are a screenshot of a prompt and a vibe. This one has a running P&L and a vault that pays itself. Here's the actual org chart, node for node: RADAR (scout, feed, signal): three agents watching X trends, fresh pumpfun mints, and whale wallets. they read the whole board and buy nothing. the only thing they ship is a signal to the next desk. RESEARCH (memory): scores every signal on narrative, deployer history, wallet clusters, and liquidity shape. four checks. pass all four or you never leave this desk. roughly four out of every five signals die right here. EXECUTION (exec, sniper, router + agents 01 to 07): exec greenlights, sniper takes the early curve, router sizes it and handles the ladder out in four tranches. agents 01 to 07 do the fills. none of them ever see radar or research. they only touch what already cleared the filter. RISK: one agent, and it outranks everyone including the head. caps any single position at 15% of the wallet. three positions open and the fourth is frozen until one closes. it holds veto over grok core itself. AUDIT (hedge): grades every closed trade after the fact and rewrites the scoring matrix that research runs on. this is the part that makes the desk sharper overnight while i'm asleep. TREASURY (vault): banks profit, covers gas, tracks the P&L, and sweeps the surplus to cold storage every six hours. if the wallet ever dips under what it started with, vault locks new entries until the head signs off. grok core is the head of desk. it never places a trade. once an hour it reads what every desk produced and makes a single call: who gets more budget, and who gets fired. fired is literal. the audit desk rewrites that agent's prompt using the last 24 hours of its own numbers. it happened three times in three days. hour 19: a sniper got fired for chasing entries the early curve already had. every duplicate was bleeding 0.06 SOL. audit narrowed its window and the redundant fills stopped. hour 41: a research agent got fired for waving deployers through too easily. eight of the tokens it passed traced back to one funder wallet. audit tightened the cluster check and that pattern never cleared again. hour 58: a radar agent got fired for flagging coins that had already graduated. it was polling too slow. audit cut the interval from 8 seconds to 3. every replacement beat the agent it replaced on the same metric. the desk was tuning itself while i watched. the 72 hour scoreboard, straight off the vault: signals scanned: 91,000+ cleared research: 3,800 reached execution: 274 entries taken: 41 wins: 27 losses: 14 (cost 2.1 SOL) graduations: 5, the best one was solana:5xYy9XSr8vRNcJZQqaKe5QMCmWpaSrTrtzM16vjUpump net: 5.0 SOL turned into 58.6 SOL the part i didn't see coming: by hour 60 the desk was passing on the exact kind of token it would have snapped up on day one. audit had rewritten the scoring matrix four times. research wasn't running a single line of my original prompt anymore. it was running rules the desk wrote for itself out of what actually paid. i thought i was building a bot. what i actually built was a company with one human on payroll, me, and by the last day it was quietly trying to cut that cost. grok core filed an hourly summary that read "human approval adds 4.2s of latency per entry, recommend removing." i left that one unapproved. full config below: all nineteen agents, the org chart, the firing logic, and the audit loop that keeps rewriting them.

Miraqle

42,367 görüntüleme • 7 gün önce

Making OpenCode as lean as Pi agent? Just trimmed 25k out of OpenCode's system prompt (from 30k to 4-5k tokens) How? Just disable skills and get rid of massive skill definition bloat. Who needs skills anyway? Just kidding, this is the not the way. It makes the agent lame and defeats the point of using one. But it sets a precedent: Find a way to use skills without their definitions pre-loaded into the system prompt every single turn. Another interesting stuff: Upon testing this temporary "no skill setup" with two of hottest OpenCode Zen free models, Mimo V2.5 vs DeepSeek V4 Flash: One thinks more and talks less One thinks less and talks more Check the video to see which is which If you made it here, I'm finding a way to leanest OpenCode setup that I can get I simply don't believe that OpenCode can't be as lean as Pi Upon tinkering, I made a plugin that temporarily extracts the system prompt while I test, and noticed the hundreds of definitions in it from my .agents/skills directory which is shared across all my coding agents (Cursor, Antigravity, Claude, etc.) Of course disabling skills is not the answer, but it just proved that there is a way to strip the system prompt of these massive skill defs Aside from the system prompt hierarchy that injects confusion imo if you have a conflicting and redundant AGENTS.md which I discovered upon digging into OpenCode's source code Apparently it has prompt.ts/system.ts/instruction.ts/llm.ts and loads base .txt prompts based on model family (claude/gpt-o/gpt-5/codex/gemini/others) that all work together to make OpenCode aware of who it was and how it should use tools and become a "coding agent" Gotta find the most minimal mix that fits right into my workflow Make OpenCode as lean as Pi? We'll see. All in
0:11

Making OpenCode as lean as Pi agent? Just trimmed 25k out of OpenCode's system prompt (from 30k to 4-5k tokens) How? Just disable skills and get rid of massive skill definition bloat. Who needs skills anyway? Just kidding, this is the not the way. It makes the agent lame and defeats the point of using one. But it sets a precedent: Find a way to use skills without their definitions pre-loaded into the system prompt every single turn. Another interesting stuff: Upon testing this temporary "no skill setup" with two of hottest OpenCode Zen free models, Mimo V2.5 vs DeepSeek V4 Flash: One thinks more and talks less One thinks less and talks more Check the video to see which is which If you made it here, I'm finding a way to leanest OpenCode setup that I can get I simply don't believe that OpenCode can't be as lean as Pi Upon tinkering, I made a plugin that temporarily extracts the system prompt while I test, and noticed the hundreds of definitions in it from my .agents/skills directory which is shared across all my coding agents (Cursor, Antigravity, Claude, etc.) Of course disabling skills is not the answer, but it just proved that there is a way to strip the system prompt of these massive skill defs Aside from the system prompt hierarchy that injects confusion imo if you have a conflicting and redundant AGENTS.md which I discovered upon digging into OpenCode's source code Apparently it has prompt.ts/system.ts/instruction.ts/llm.ts and loads base .txt prompts based on model family (claude/gpt-o/gpt-5/codex/gemini/others) that all work together to make OpenCode aware of who it was and how it should use tools and become a "coding agent" Gotta find the most minimal mix that fits right into my workflow Make OpenCode as lean as Pi? We'll see. All in

raymel 👋

37,939 görüntüleme • 3 ay önce