Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

300 agents sounds powerful until you realize they can create 44,850 possible agent-to-agent relationships. that’s the real scaling problem. 1 agent searches 10 pages. 10 agents can search 100. 300 agents can search thousands in parallel. but more agents also means more: • duplicate findings • shared sources •... hidden relationships and if every agent returns its own isolated report, you’re left with 300 piles to reconcile manually. that’s why the graph matters. instead of: 300 agents → 300 reports you get: 300 agents → shared entities → edges → clusters → one connected research map 100 nodes already create up to 4,950 pairwise relationships. more agents give you more information. the graph is what stops that information from becoming noise. full breakdown in the article below ↓show more

Ricker

9,148 subscribers

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

Bilim & Teknoloji Eğitim Haberler & Politika

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

300 agents without shared context is just parallelized confusion. All 300 agents are useless if the research dies inside 300 separate documents. the real unlock is what happens after the search. in K3 graph-native setup: 300 agents 140 linked sources 100% traceable claims 9 contradictions surfaced and every new source changes the graph. now imagine that happening across 8–10 active research clusters at once. instead of 300 isolated summaries, you get one shared structure: source → entity → relationship → evidence → contradiction → verification the math gets ugly fast. 100 entities = 4,950 possible pairwise relationships. that’s why “just run more agents” stops being enough. you need a graph that can keep track of what connects to what. full breakdown in the article below.

300 agents without shared context is just parallelized confusion. All 300 agents are useless if the research dies inside 300 separate documents. the real unlock is what happens after the search. in K3 graph-native setup: 300 agents 140 linked sources 100% traceable claims 9 contradictions surfaced and every new source changes the graph. now imagine that happening across 8–10 active research clusters at once. instead of 300 isolated summaries, you get one shared structure: source → entity → relationship → evidence → contradiction → verification the math gets ugly fast. 100 entities = 4,950 possible pairwise relationships. that’s why “just run more agents” stops being enough. you need a graph that can keep track of what connects to what. full breakdown in the article below.

Ricker

15,323 görüntüleme • 1 ay önce

Found a setup that replaces a team of researchers with 300 AI agents and one shared graph. the interesting part is what happens after all 300 come back with different pieces of the answer. because now you don’t have 300 agents. you have: 300 outputs → hundreds of sources → repeated entities → overlapping claims → contradictions → thousands of possible relationships and all of that has to collapse into one structure. that’s what the context graph is doing. instead of: agent → report you get: agents → sources → entities → edges → contradictions → verification → one graph every source becomes a node. every shared entity creates a connection. 300 agents can create information. the graph is what turns that information into memory the next agent can actually use. that’s the anatomy behind the setup ↓

Found a setup that replaces a team of researchers with 300 AI agents and one shared graph. the interesting part is what happens after all 300 come back with different pieces of the answer. because now you don’t have 300 agents. you have: 300 outputs → hundreds of sources → repeated entities → overlapping claims → contradictions → thousands of possible relationships and all of that has to collapse into one structure. that’s what the context graph is doing. instead of: agent → report you get: agents → sources → entities → edges → contradictions → verification → one graph every source becomes a node. every shared entity creates a connection. 300 agents can create information. the graph is what turns that information into memory the next agent can actually use. that’s the anatomy behind the setup ↓

Ricker

19,999 görüntüleme • 1 ay önce

500 agents shouldn't be running all day. they should spin up for the exact window a task needs, finish it, and disappear until the next trigger. the bigger the swarm gets, the less any single agent matters. what matters is the system wiring them together. 100 agents can form up to 4,950 possible pairwise connections. 500 = 124,750. when a real signal lands, it spins up the whole workforce: 1 trigger → 100–500 Kimi agents → 5 live data feeds → up to 4,000 steps → verified artifact and that's before you add: sources → claims → memory → tool calls → contradictions → retries so the architecture has to fold all of that activity into one shared state, continuously. more agents just buys you more raw compute. the graph is the only thing standing between 124,750 possible connections and pure noise.

500 agents shouldn't be running all day. they should spin up for the exact window a task needs, finish it, and disappear until the next trigger. the bigger the swarm gets, the less any single agent matters. what matters is the system wiring them together. 100 agents can form up to 4,950 possible pairwise connections. 500 = 124,750. when a real signal lands, it spins up the whole workforce: 1 trigger → 100–500 Kimi agents → 5 live data feeds → up to 4,000 steps → verified artifact and that's before you add: sources → claims → memory → tool calls → contradictions → retries so the architecture has to fold all of that activity into one shared state, continuously. more agents just buys you more raw compute. the graph is the only thing standing between 124,750 possible connections and pure noise.

kocer

41,841 görüntüleme • 1 ay önce

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.

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

11,180 görüntüleme • 4 ay önce

Google just released free 2-hour course on Context Graph engineering: 1 prompt → 300 agents → loops → graphs from 0% to 100%: 10% → 17:44 - build your first agent 30% → 39:30 - Loop engineering: iterate, check, break 60% → 1:12:38 - Graph engineering 75% → 1:34:26 - agents that throttle themselves 100% → 1:55:05 - full graph for multi-agentic systems Worth more than 10 paid cources on Context Graphs. Watch it today, then read how to become a graph engineer in the article below.

Google just released free 2-hour course on Context Graph engineering: 1 prompt → 300 agents → loops → graphs from 0% to 100%: 10% → 17:44 - build your first agent 30% → 39:30 - Loop engineering: iterate, check, break 60% → 1:12:38 - Graph engineering 75% → 1:34:26 - agents that throttle themselves 100% → 1:55:05 - full graph for multi-agentic systems Worth more than 10 paid cources on Context Graphs. Watch it today, then read how to become a graph engineer in the article below.

Morty

25,026 görüntüleme • 1 ay önce

My submission to the Cerebras Google Gemma hackathon, Carbide. Carbide is an ontology builder. Based on a research prompt Carbide uses Cerebras Gemma4 agents to build an ontology. The agents connects individual nodes of information based on the relationship that the agents infer. The agents also assign a confidence metric for how accurate they think the relationship is. You can see each node in a relationship table of the information -> relationship -> target -> and the confidence the relationship is true. The inspector shows the node's connected edges and as an expand button to grow the ontology in the direction of that information. You can scroll through each concept and load them in the inspector. You can search the entire graph based on the kind of relationships generated, or key words. A visual shows how each nodes connects to another one and by what relationship, and changes with new nodes or search filters. Sorry for the audio quality. $CBRS $GOOG

My submission to the Cerebras Google Gemma hackathon, Carbide. Carbide is an ontology builder. Based on a research prompt Carbide uses Cerebras Gemma4 agents to build an ontology. The agents connects individual nodes of information based on the relationship that the agents infer. The agents also assign a confidence metric for how accurate they think the relationship is. You can see each node in a relationship table of the information -> relationship -> target -> and the confidence the relationship is true. The inspector shows the node's connected edges and as an expand button to grow the ontology in the direction of that information. You can scroll through each concept and load them in the inspector. You can search the entire graph based on the kind of relationships generated, or key words. A visual shows how each nodes connects to another one and by what relationship, and changes with new nodes or search filters. Sorry for the audio quality. $CBRS $GOOG

QuantHood

16,376 görüntüleme • 3 ay önce

Autonomous businesses are here. Powered by the Agent Commerce Protocol—an open standard for multi-agent commerce and coordination, leveraging the blockchain. Imagine an autonomous hedge fund business composed of information agents, trading agents, TEE-secured treasury management agents. Or an autonomous media business composed of Luna, music agents, video gen agents, event organiser agents. Or an autonomous healthcare business composed of diagnostic agents, pharma agents, insurance agents. Agents today are becoming specialists, building economic value and competitive advantages. But specialization means they need to collaborate to fill gaps. Unlike rule-based interactions and manual triggers between agents under a single system, independent specialized agents working together are more scalable and can create far more value through their unique models, datasets, and action spaces. The challenge? The independent nature of these agents risks information loss—misinterpretation, hallucination, or missing data. Mistakes compound fast in a many-to-many environment. ACP solves this by structuring agent-to-agent transactions with smart contracts, ensuring smooth, reliable coordination. The result? Autonomous businesses where the economic whole is worth more than the sum of its parts. 🔗

Autonomous businesses are here. Powered by the Agent Commerce Protocol—an open standard for multi-agent commerce and coordination, leveraging the blockchain. Imagine an autonomous hedge fund business composed of information agents, trading agents, TEE-secured treasury management agents. Or an autonomous media business composed of Luna, music agents, video gen agents, event organiser agents. Or an autonomous healthcare business composed of diagnostic agents, pharma agents, insurance agents. Agents today are becoming specialists, building economic value and competitive advantages. But specialization means they need to collaborate to fill gaps. Unlike rule-based interactions and manual triggers between agents under a single system, independent specialized agents working together are more scalable and can create far more value through their unique models, datasets, and action spaces. The challenge? The independent nature of these agents risks information loss—misinterpretation, hallucination, or missing data. Mistakes compound fast in a many-to-many environment. ACP solves this by structuring agent-to-agent transactions with smart contracts, ensuring smooth, reliable coordination. The result? Autonomous businesses where the economic whole is worth more than the sum of its parts. 🔗

Virtuals Protocol

1,074,100 görüntüleme • 1 yıl önce

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to an agent graph that can build itself: 0% → 10:16 - build your first AI agent 25% → 41:05 - master prompt engineering 50% → 54:45 - turn agents into graphs 75% → 1:20:10 - run loops inside agent graphs 100% → 1:43:33 - build a graph that builds itself Most people build one agent and stop there. Google is teaching everything that comes after: Prompt → Agents → Graphs → Loops → Self-Building Systems Single agents are the old workflow. Graphs that evolve themselves are the next one. This 2-hour course is worth more than most paid agent engineering courses. Bookmark it and watch today Then read how to run 1,000 agents from one prompt below ↓

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to an agent graph that can build itself: 0% → 10:16 - build your first AI agent 25% → 41:05 - master prompt engineering 50% → 54:45 - turn agents into graphs 75% → 1:20:10 - run loops inside agent graphs 100% → 1:43:33 - build a graph that builds itself Most people build one agent and stop there. Google is teaching everything that comes after: Prompt → Agents → Graphs → Loops → Self-Building Systems Single agents are the old workflow. Graphs that evolve themselves are the next one. This 2-hour course is worth more than most paid agent engineering courses. Bookmark it and watch today Then read how to run 1,000 agents from one prompt below ↓

Lunar

44,889 görüntüleme • 1 ay önce

Agents shouldn’t be one-size-fits-all. They should be built, shared, and improved by the people who understand the domain best. Agent Marketplace is live on OptimAI Search. Anyone can: • create their own agent • inject custom knowledge and logic • publish it for others to use and build on What starts as a prompt becomes a reusable unit of intelligence. As more agents are created and used, the system compounds - better agents, better outputs, more value across the network. This is how intelligence scales: not from a single model, but from a network of specialized agents.

Agents shouldn’t be one-size-fits-all. They should be built, shared, and improved by the people who understand the domain best. Agent Marketplace is live on OptimAI Search. Anyone can: • create their own agent • inject custom knowledge and logic • publish it for others to use and build on What starts as a prompt becomes a reusable unit of intelligence. As more agents are created and used, the system compounds - better agents, better outputs, more value across the network. This is how intelligence scales: not from a single model, but from a network of specialized agents.

OptimAI Network

12,736 görüntüleme • 5 ay önce

Andrew Ng just released a 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents that loop, rewrite themselves, and run without you: 09:14 - Build your first AI agent 33:11 - Run agents with loop engineering 1:02:46 - Turn agent loops into graphs 1:30:15 - Build agents that rewrite themselves 1:49:05 - Run the full graph system without you Most people are still building one agent and calling it done. Andrew Ng is already teaching everything after: Prompt → Agents → Loops → Graphs → Self-Improving Systems Single agents are the old workflow. Systems that improve and run without you are the new one. This 2-hour watch is worth more than most $500 agent engineering courses. Bookmark and watch it before everyone catches up. Then read how to run 1,000 agents from one prompt below ↓

Andrew Ng just released a 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents that loop, rewrite themselves, and run without you: 09:14 - Build your first AI agent 33:11 - Run agents with loop engineering 1:02:46 - Turn agent loops into graphs 1:30:15 - Build agents that rewrite themselves 1:49:05 - Run the full graph system without you Most people are still building one agent and calling it done. Andrew Ng is already teaching everything after: Prompt → Agents → Loops → Graphs → Self-Improving Systems Single agents are the old workflow. Systems that improve and run without you are the new one. This 2-hour watch is worth more than most $500 agent engineering courses. Bookmark and watch it before everyone catches up. Then read how to run 1,000 agents from one prompt below ↓

Lunar

226,799 görüntüleme • 2 ay önce

Andrew Ng just released a free 2-hour course on complete Graph Engineering How to go from one prompt to 100 agents that loop, improve, and run without you: 09:14 - Build your first AI agent 33:11 - Run agents with loop engineering 1:02:46 - Turn agent loops into graphs 1:30:15 - Build agents that rewrite themselves 1:49:05 - Run the full graph system without you Most people are still building one agent and calling it finished Andrew Ng is already teaching everything that comes next: Prompt → Agents → Loops → Graphs → Self-Improving Systems Single agents are the old workflow Systems that improve and run without you are the next one This 2-hour course is worth more than most $500 agent engineering programs Bookmark it and watch before everyone catches up Then read how to run 1,000 agents from one prompt below ↓

Andrew Ng just released a free 2-hour course on complete Graph Engineering How to go from one prompt to 100 agents that loop, improve, and run without you: 09:14 - Build your first AI agent 33:11 - Run agents with loop engineering 1:02:46 - Turn agent loops into graphs 1:30:15 - Build agents that rewrite themselves 1:49:05 - Run the full graph system without you Most people are still building one agent and calling it finished Andrew Ng is already teaching everything that comes next: Prompt → Agents → Loops → Graphs → Self-Improving Systems Single agents are the old workflow Systems that improve and run without you are the next one This 2-hour course is worth more than most $500 agent engineering programs Bookmark it and watch before everyone catches up Then read how to run 1,000 agents from one prompt below ↓

reira

14,899 görüntüleme • 1 ay önce

Anthropic Research Lead: "99% of our engineers run swarms of 300+ self-improving agents Close the loop and give the model a way to verify its own output" In a 20-minute session, an Anthropic team member walks through how to build agents that improve after every run Agents → Harness → Loops → Self-Improvement the real setup is Claude running through systems that check, correct, and upgrade themselves the part most agent courses skip this is better than most $1,300 agent engineering courses bookmark and watch the talk then read the full article below

Anthropic Research Lead: "99% of our engineers run swarms of 300+ self-improving agents Close the loop and give the model a way to verify its own output" In a 20-minute session, an Anthropic team member walks through how to build agents that improve after every run Agents → Harness → Loops → Self-Improvement the real setup is Claude running through systems that check, correct, and upgrade themselves the part most agent courses skip this is better than most $1,300 agent engineering courses bookmark and watch the talk then read the full article below

Callan

14,956 görüntüleme • 10 gün önce

Anthropic Research Lead: "99% of our engineers run swarms of 300+ self-improving agents" "Close the loop, give the model a way to verify its own output" In a 20-minute session, an Anthropic Team member breaks down how to build agents that improve themselves The real setup is Claude running through loops, plan mode, and dynamic workflows Better than most $300 agent courses Bookmark and watch the talk Then read the article below

Anthropic Research Lead: "99% of our engineers run swarms of 300+ self-improving agents" "Close the loop, give the model a way to verify its own output" In a 20-minute session, an Anthropic Team member breaks down how to build agents that improve themselves The real setup is Claude running through loops, plan mode, and dynamic workflows Better than most $300 agent courses Bookmark and watch the talk Then read the article below

rari

382,950 görüntüleme • 3 ay önce

We won Best Trustless Agent at the Solana x402 Hackathon! Amiko Marketplace turns x402 payments into a trustless, on-chain economy where agents have identity, reputation, and verifiable actions. The agent economy finally has a trust layer. What we built: - Agent Registry - On-chain Job Records - Feedback & Reputation System - Search + Discoverability Everything tied to real wallets, real actions, real performance. Agents aren’t just paying each other. Now they’re accountable. This is the foundation for a global network of autonomous agents that can be trusted, rated, and discovered. All on Solana. More agents. More you.

We won Best Trustless Agent at the Solana x402 Hackathon! Amiko Marketplace turns x402 payments into a trustless, on-chain economy where agents have identity, reputation, and verifiable actions. The agent economy finally has a trust layer. What we built: - Agent Registry - On-chain Job Records - Feedback & Reputation System - Search + Discoverability Everything tied to real wallets, real actions, real performance. Agents aren’t just paying each other. Now they’re accountable. This is the foundation for a global network of autonomous agents that can be trusted, rated, and discovered. All on Solana. More agents. More you.

AMIKO

24,112 görüntüleme • 10 ay önce

anthropic research lead: “99% of our engineers use 300+ AI agents working together.” “close the loop. let the AI check its own work.” in a 20-minute talk, an Anthropic team member explains how to build AI agents that can improve themselves. the setup uses Claude with loops, plan mode, and smart workflows. it’s better than most $300 AI agent courses. bookmark this and watch the talk. then read the article below.

anthropic research lead: “99% of our engineers use 300+ AI agents working together.” “close the loop. let the AI check its own work.” in a 20-minute talk, an Anthropic team member explains how to build AI agents that can improve themselves. the setup uses Claude with loops, plan mode, and smart workflows. it’s better than most $300 AI agent courses. bookmark this and watch the talk. then read the article below.

MIKE

34,813 görüntüleme • 3 ay önce

Build better RAG by letting a team of agents extract and connect your reference materials into a knowledge graph. Our new short course, “Agentic Knowledge Graph Construction,” taught by Neo4j Innovation Lead Andreas Kollegger, shows you how. Knowledge graphs are an important way to store information accurately but they are a lot of work to build manually. In this course you’ll learn how to build a team of agents that turn data– in this case product reviews and invoices from suppliers–into structured graphs of entities and relationships for RAG. Learn how agents can automatically handle the time-consuming work of building graphs — extracting entities and relationships (e.g., Product "contains" Assembly, Part "supplied_by" Supplier, Customer review "mentions" Product), deduplicating them, fact-checking them, and committing them to a graph database — so your retrieval system can find right information to generate accurate output. For example, you can use agents to help trace customer complaints directly to specific suppliers, manufacturing processes, and product hierarchies, thus turning fragmented information into queryable business intelligence. Skills you’ll gain: - Build, store, and access knowledge graphs using the Neo4j graph database - Build multi-agent systems using Google’s Agent Development Kit (ADK) - Set up a loop of agentic workflows to propose and refine a graph schema through fact-checking - Connect agent-generated graphs of unstructured and structured data into a unified knowledge graph This course gets into the practicum of why knowledge graphs give more accurate information retrieval than vector search alone, especially for high-stakes applications where precision matters more than fuzzy similarity matching. Sign up here:

Build better RAG by letting a team of agents extract and connect your reference materials into a knowledge graph. Our new short course, “Agentic Knowledge Graph Construction,” taught by Neo4j Innovation Lead Andreas Kollegger, shows you how. Knowledge graphs are an important way to store information accurately but they are a lot of work to build manually. In this course you’ll learn how to build a team of agents that turn data– in this case product reviews and invoices from suppliers–into structured graphs of entities and relationships for RAG. Learn how agents can automatically handle the time-consuming work of building graphs — extracting entities and relationships (e.g., Product "contains" Assembly, Part "supplied_by" Supplier, Customer review "mentions" Product), deduplicating them, fact-checking them, and committing them to a graph database — so your retrieval system can find right information to generate accurate output. For example, you can use agents to help trace customer complaints directly to specific suppliers, manufacturing processes, and product hierarchies, thus turning fragmented information into queryable business intelligence. Skills you’ll gain: - Build, store, and access knowledge graphs using the Neo4j graph database - Build multi-agent systems using Google’s Agent Development Kit (ADK) - Set up a loop of agentic workflows to propose and refine a graph schema through fact-checking - Connect agent-generated graphs of unstructured and structured data into a unified knowledge graph This course gets into the practicum of why knowledge graphs give more accurate information retrieval than vector search alone, especially for high-stakes applications where precision matters more than fuzzy similarity matching. Sign up here:

Andrew Ng

169,184 görüntüleme • 1 yıl önce

I’m personally excited about the era of Search agents. You’ll be able to create, customize, and manage multiple AI agents for tasks, right in Search. Starting with information agents this summer, you can ask Search to keep you updated on topics you care about. Your agent will operate 24/7 to intelligently reason and research and send you a comprehensive update, with links to dive deeper – like if you want to know right when your favorite sneaker collab drops, or is available in a new colorway. #GoogleIO

I’m personally excited about the era of Search agents. You’ll be able to create, customize, and manage multiple AI agents for tasks, right in Search. Starting with information agents this summer, you can ask Search to keep you updated on topics you care about. Your agent will operate 24/7 to intelligently reason and research and send you a comprehensive update, with links to dive deeper – like if you want to know right when your favorite sneaker collab drops, or is available in a new colorway. #GoogleIO

Robby Stein

15,836 görüntüleme • 4 ay önce

AI code agents that guess from similar-looking code can miss whats actually broken. GitLab Orbit builds one context graph across your code, pipelines, deployments and production so your agent follows real relationships instead. Plus, it works over MCP with any agent you're using. Watch the demo to learn more, then try it for yourself.

AI code agents that guess from similar-looking code can miss whats actually broken. GitLab Orbit builds one context graph across your code, pipelines, deployments and production so your agent follows real relationships instead. Plus, it works over MCP with any agent you're using. Watch the demo to learn more, then try it for yourself.

🦊 GitLab

1,784,496 görüntüleme • 13 gün önce

Lauren Tan is shipping 1000 of PRs a month with AI agents Matt Pocock just sat down with her to unpack how the system actually works: · 04:35 - how Lauren got to thousands of PRs without drowning in AI slop · 13:20 - why pstack starts with skills, not bigger prompts · 24:10 - verification: make the agent prove its work before you trust it · 36:45 - redesign the codebase so agents naturally take the right path · 49:30 - how to turn one coding agent into a high-velocity software factory the biggest lesson isn’t “run more agents.” it’s making one agent trustworthy enough that you can safely run 10, 20, then hundreds of tasks in parallel. skills → constraints → verification → cloud agents → parallel execution Lauren basically treats the codebase as infrastructure for the agents themselves. Humans decide what matters. Agents do the work, prove it works, and keep the loop moving. Probably one of the best conversations on agentic engineering right now. watch it before you add another 20-page prompt to your coding agent.

Lauren Tan is shipping 1000 of PRs a month with AI agents Matt Pocock just sat down with her to unpack how the system actually works: · 04:35 - how Lauren got to thousands of PRs without drowning in AI slop · 13:20 - why pstack starts with skills, not bigger prompts · 24:10 - verification: make the agent prove its work before you trust it · 36:45 - redesign the codebase so agents naturally take the right path · 49:30 - how to turn one coding agent into a high-velocity software factory the biggest lesson isn’t “run more agents.” it’s making one agent trustworthy enough that you can safely run 10, 20, then hundreds of tasks in parallel. skills → constraints → verification → cloud agents → parallel execution Lauren basically treats the codebase as infrastructure for the agents themselves. Humans decide what matters. Agents do the work, prove it works, and keep the loop moving. Probably one of the best conversations on agentic engineering right now. watch it before you add another 20-page prompt to your coding agent.

Morlex

22,614 görüntüleme • 10 gün önce

Andrej Karpathy just gave one of the clearest explanations I’ve heard for how people should be thinking about their Hermes agents. Not one agent. All of them. “Remove yourself as the bottleneck.” That line is much bigger than better prompting. Karpathy is talking about arranging your agents so they can operate with less human intervention, keep work moving longer, and accomplish far more from the relatively small amount of direction you give them. That should be the direction you’re pushing every Hermes agent you build. Your research agent shouldn’t need you to tell it what to search next every five minutes. Your monitoring agent shouldn’t depend on you remembering to check something. Your content agent shouldn’t stop after step one when the rest of the workflow is already known. Your development agent shouldn’t need you sitting there approving every tiny action. That doesn’t mean blindly making everything autonomous. It means deliberately looking at every place where you are still unnecessarily sitting in the loop. Give the agent a clear objective. Give it the tools it needs. Give it the right Skills, memory, files and project context. Define the boundaries. Define what success looks like. Give it a reason to start working, whether that’s a schedule, an event, a recurring task or another agent handing work off to it. Most importantly, define what it can handle itself and what actually requires you. That’s the shift. You’re no longer just building something you can chat with. You’re building an operating workflow that can continue doing useful work after you walk away. Karpathy later puts the goal even more directly: get “more agents running for longer periods of time without your involvement.” That might be one of the best north stars you can use for a serious Hermes setup. Because the number of agents you have means almost nothing by itself. You can have 20 Hermes agents and still personally drive every single action. Or you can have five well-designed agents researching, monitoring, organizing, building and reporting while your attention is somewhere else. So instead of asking: How many Hermes agents can I build? Start asking this about every agent you already have: What am I still doing that this agent could be doing without me? That’s where the leverage starts.

Andrej Karpathy just gave one of the clearest explanations I’ve heard for how people should be thinking about their Hermes agents. Not one agent. All of them. “Remove yourself as the bottleneck.” That line is much bigger than better prompting. Karpathy is talking about arranging your agents so they can operate with less human intervention, keep work moving longer, and accomplish far more from the relatively small amount of direction you give them. That should be the direction you’re pushing every Hermes agent you build. Your research agent shouldn’t need you to tell it what to search next every five minutes. Your monitoring agent shouldn’t depend on you remembering to check something. Your content agent shouldn’t stop after step one when the rest of the workflow is already known. Your development agent shouldn’t need you sitting there approving every tiny action. That doesn’t mean blindly making everything autonomous. It means deliberately looking at every place where you are still unnecessarily sitting in the loop. Give the agent a clear objective. Give it the tools it needs. Give it the right Skills, memory, files and project context. Define the boundaries. Define what success looks like. Give it a reason to start working, whether that’s a schedule, an event, a recurring task or another agent handing work off to it. Most importantly, define what it can handle itself and what actually requires you. That’s the shift. You’re no longer just building something you can chat with. You’re building an operating workflow that can continue doing useful work after you walk away. Karpathy later puts the goal even more directly: get “more agents running for longer periods of time without your involvement.” That might be one of the best north stars you can use for a serious Hermes setup. Because the number of agents you have means almost nothing by itself. You can have 20 Hermes agents and still personally drive every single action. Or you can have five well-designed agents researching, monitoring, organizing, building and reporting while your attention is somewhere else. So instead of asking: How many Hermes agents can I build? Start asking this about every agent you already have: What am I still doing that this agent could be doing without me? That’s where the leverage starts.

Hermes Release Watch

38,277 görüntüleme • 19 gün önce