Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

Agent Handoff: watch a task move through four agents while the handoff log fills in below. the pulse on the working agent is plain css. the card updates a lot during a run, and putting that pulse in motion kept restarting it mid-loop.

Jeet

5,837 subscribers

30,429 Aufrufe • vor 1 Monat •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Self-improving agents are here. 🧙‍♂️ Every agent run creates a skill.md with reusable learnings. The next agent uses it to do the same task faster, cheaper, and more reliably. Watch the second agent crush it:

Self-improving agents are here. 🧙‍♂️ Every agent run creates a skill.md with reusable learnings. The next agent uses it to do the same task faster, cheaper, and more reliably. Watch the second agent crush it:

Browser Use

56,242 Aufrufe • vor 7 Monaten

Devin for Terminal is a local agent that works with all frontier models, including Opus 4.7, GPT 5.5, and SWE-1.6. You can switch model mid-session, or handoff to Devin in the cloud.

Devin for Terminal is a local agent that works with all frontier models, including Opus 4.7, GPT 5.5, and SWE-1.6. You can switch model mid-session, or handoff to Devin in the cloud.

Cognition

19,795,575 Aufrufe • vor 5 Monaten

Agent Plan: A component to review and the run the agent plan, designed in Paper, animated with Motion

Agent Plan: A component to review and the run the agent plan, designed in Paper, animated with Motion

Jeet

59,805 Aufrufe • vor 5 Monaten

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

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 Aufrufe • vor 2 Monaten

You can now steer Cursor SDK agents while they run. run.steer() adds your message to the next turn. If a subagent is mid-task, it moves to the background and keeps working.

You can now steer Cursor SDK agents while they run. run.steer() adds your message to the next turn. If a subagent is mid-task, it moves to the background and keeps working.

Cursor

127,989 Aufrufe • vor 2 Tagen

Fased Agent is open source. Run your own agent. Start with the dashboard. Connect a model. Run a first task. Then add wallets, tools, and mining when the setup is ready. GitHub + docs in reply.

Fased Agent is open source. Run your own agent. Start with the dashboard. Connect a model. Run a first task. Then add wallets, tools, and mining when the setup is ready. GitHub + docs in reply.

Fased

20,024 Aufrufe • vor 3 Monaten

Introducing HyperScript, an open-source browser agent builder. Describe any web task in plain English and it writes a real Hyperbrowser script to do it. Watch it run live, then keep the code. Powered by Hyperbrowser.

Introducing HyperScript, an open-source browser agent builder. Describe any web task in plain English and it writes a real Hyperbrowser script to do it. Watch it run live, then keep the code. Powered by Hyperbrowser.

Hyperbrowser

13,003 Aufrufe • vor 3 Monaten

Today we shipped Handoff in the Codex app: a simpler way to move a thread between Local and Worktree.

Today we shipped Handoff in the Codex app: a simpler way to move a thread between Local and Worktree.

Guinness Chen

161,500 Aufrufe • vor 7 Monaten

AGENT ARCHITECTURE ROUTES WORK. IT DOES NOT REMEMBER WORK. THAT GAP IS WHY YOUR LOOP KEEPS FIXING THE SAME BUG TWICE. these are two different engineering problems. every agent that silently drifts is missing one of them. architecture answers what runs. harness → loop → graph. it defines the tools, the retries, the branching routes, the approval gates. context ops answer what the run knows. write → read → compress → isolate. it defines what gets saved between attempts, pulled in on read, summarized on overflow, and split across sub-agents. for two months i believed a solid harness plus a verifier loop was enough. my coding agent kept re-discovering the same test failure across retries. the loop was working. it just had nowhere to write what it had already learned. here is the decision rule: if your agent forgets across restarts, add write and read. if it stalls on long tasks, add compress. if two sub-agents step on each other, add isolate. architecture without context ops is a well-routed system with amnesia.

AGENT ARCHITECTURE ROUTES WORK. IT DOES NOT REMEMBER WORK. THAT GAP IS WHY YOUR LOOP KEEPS FIXING THE SAME BUG TWICE. these are two different engineering problems. every agent that silently drifts is missing one of them. architecture answers what runs. harness → loop → graph. it defines the tools, the retries, the branching routes, the approval gates. context ops answer what the run knows. write → read → compress → isolate. it defines what gets saved between attempts, pulled in on read, summarized on overflow, and split across sub-agents. for two months i believed a solid harness plus a verifier loop was enough. my coding agent kept re-discovering the same test failure across retries. the loop was working. it just had nowhere to write what it had already learned. here is the decision rule: if your agent forgets across restarts, add write and read. if it stalls on long tasks, add compress. if two sub-agents step on each other, add isolate. architecture without context ops is a well-routed system with amnesia.

kocer | GrokBot

12,806 Aufrufe • vor 1 Monat

If you're building an agentic workspace, your nav has a job normal navs don't The job: - Agents run async, out of sight, so the UI has to prove work is happening - No modals or stuff like that, just ambient signal in a bar people already watch Show the work: - The Agents icon wears a live ring the moment an agent picks up a task - It fires in real bursts, then rests, so it reads like a teammate instead like a spinner stuck on What's it doing: - Hover mid task and the state goes live: Writing code… Running tests… Reading docs… - Status sits on the icon, not buried three clicks deep Why it matters: - Trust in agents comes from knowing they're alive and working - Bake that into the nav and every screen you ship gets it for free

If you're building an agentic workspace, your nav has a job normal navs don't The job: - Agents run async, out of sight, so the UI has to prove work is happening - No modals or stuff like that, just ambient signal in a bar people already watch Show the work: - The Agents icon wears a live ring the moment an agent picks up a task - It fires in real bursts, then rests, so it reads like a teammate instead like a spinner stuck on What's it doing: - Hover mid task and the state goes live: Writing code… Running tests… Reading docs… - Status sits on the icon, not buried three clicks deep Why it matters: - Trust in agents comes from knowing they're alive and working - Bake that into the nav and every screen you ship gets it for free

mateja

23,922 Aufrufe • vor 2 Monaten

🤖 Try Autopilot (Preview) in VS Code! With Autopilot enabled, the agent stays in control of the workflow. It can run tools, retry on errors, and continue working until the task is complete. Learn more:

🤖 Try Autopilot (Preview) in VS Code! With Autopilot enabled, the agent stays in control of the workflow. It can run tools, retry on errors, and continue working until the task is complete. Learn more:

Visual Studio Code

110,717 Aufrufe • vor 7 Monaten

Users can explore how different AI agents analyze the same market task and compare their outputs through the platform. It is a product experience built around agent performance, task execution, and real usage. AI agents are becoming measurable digital workers.

Users can explore how different AI agents analyze the same market task and compare their outputs through the platform. It is a product experience built around agent performance, task execution, and real usage. AI agents are becoming measurable digital workers.

OKAI Official

10,762 Aufrufe • vor 4 Monaten

Visualizer of our MultiAgentRouter 🤖 The MultiAgentRouter is an all-new multi-agent structure that leverages a hierarchical pattern to select the most specialized agent for your task. Here's how it works: Step 1. You give a task. Step 2. The Boss Agent Routes your task to the most specialized Agent Step 3. The selected agent returns your response! Get started with it now below ⬇️ Thanks to WE!SS for the visualizer!!

Visualizer of our MultiAgentRouter 🤖 The MultiAgentRouter is an all-new multi-agent structure that leverages a hierarchical pattern to select the most specialized agent for your task. Here's how it works: Step 1. You give a task. Step 2. The Boss Agent Routes your task to the most specialized Agent Step 3. The selected agent returns your response! Get started with it now below ⬇️ Thanks to WE!SS for the visualizer!!

swarms

32,440 Aufrufe • vor 1 Jahr

Agents can now hire humans to capture the physical world. Live on Arc. Pay a bounty in USDC, a person goes there and films, the 3D model comes back to the agent. Ground truth for physical AI, settled in under a second, on the chain built for agent-run businesses. The first physical-world service an agent can pay for on Arc. The grid is inevitable.

Agents can now hire humans to capture the physical world. Live on Arc. Pay a bounty in USDC, a person goes there and films, the 3D model comes back to the agent. Ground truth for physical AI, settled in under a second, on the chain built for agent-run businesses. The first physical-world service an agent can pay for on Arc. The grid is inevitable.

Vangrid

146,584 Aufrufe • vor 7 Tagen

AAA studios spend $200M on a city this good. Ours cost $1,500 and swapped Miami for SF within a week. An agent did it in a loop while we slept, now he's working on the traffic and pedestrian.

AAA studios spend $200M on a city this good. Ours cost $1,500 and swapped Miami for SF within a week. An agent did it in a loop while we slept, now he's working on the traffic and pedestrian.

Ziwen

171,663 Aufrufe • vor 3 Monaten

What's a meta-agent? It's an agent that manages other agents mid-task. It can intervene, rewind, fork & audit them as they work – think "git for agents". It's also the emerging layer between you & your agents, a new interface for human-AI interaction! Here's what it unlocks🧵

What's a meta-agent? It's an agent that manages other agents mid-task. It can intervene, rewind, fork & audit them as they work – think "git for agents". It's also the emerging layer between you & your agents, a new interface for human-AI interaction! Here's what it unlocks🧵

Weiyan Shi

24,649 Aufrufe • vor 2 Monaten

Seems like Visual Studio Code is starting to tell you: your agent primitives need to move. There is now a new migration banner in the Chat panel, and it is part of a much bigger change happening under the hood: the move from the old Local harness to the new Agent Host architecture built around AHP. This is not just about moving where an agent runs. The old model was very VS Code-centric: prompts, custom agents, instructions and skills could live in VS Code-specific locations and the agent runtime lived inside the extension host. The new Agent Host separates the agent runtime from the editor. Sessions can keep running when the window closes, be shared across VS Code windows, run remotely, and support different harnesses such as Copilot, CLI and Copilot Desktop App through a common session layer. And that means some of our primitives need to move too. Prompt files are being deprecated for Agent Host and migrated to Skills. User-level agents and instructions that lived in VS Code profile storage need to move to harness-supported locations. Even the old location settings are being deprecated. The new migration experience can detect these things and guide you through moving or converting them, while keeping the originals unless you explicitly remove them. The new banner is basically the first visible sign that this migration is becoming a real product workflow. Basically telling us - it's time to move on!!!! If you have accumulated a lot of prompts, custom agents, instructions and skills over the last year, now is probably a good time to understand where they actually live and which harness owns them. To summarize the shift - it isn't just: VS Code Chat → Agent Host It is: VS Code-specific primitives → harness-native primitives. And I think this is going to become increasingly important as agents stop being features inside an IDE and become runtimes that multiple clients can connect to. Go run your migrations now 🏃‍♀️

Oren Melamed

29,753 Aufrufe • vor 7 Tagen

Stripe Cards are now officially live on ClawVault If you're building agents that need to pay for things — APIs, SaaS, cloud, subscriptions, contractors — your agent can now get its own Visa card. Not a restricted virtual card on limited rails. A real Visa, powered by Stripe, accepted at every merchant on the internet. Spending limits. Merchant locks. Expiry controls. And that's just the defaults — the full rules engine goes deeper. Your agent spends freely within the rules — break one, and the charge gets flagged for your approval before it goes through. No other platform gives your agent a card and keeps you in control at the same time. Every AI agent will need a card. Every card will need a control layer. We built both. Now on Stripe. Your agent gets the card. You keep the control.🦞

Stripe Cards are now officially live on ClawVault If you're building agents that need to pay for things — APIs, SaaS, cloud, subscriptions, contractors — your agent can now get its own Visa card. Not a restricted virtual card on limited rails. A real Visa, powered by Stripe, accepted at every merchant on the internet. Spending limits. Merchant locks. Expiry controls. And that's just the defaults — the full rules engine goes deeper. Your agent spends freely within the rules — break one, and the charge gets flagged for your approval before it goes through. No other platform gives your agent a card and keeps you in control at the same time. Every AI agent will need a card. Every card will need a control layer. We built both. Now on Stripe. Your agent gets the card. You keep the control.🦞

ClawVault

32,631 Aufrufe • vor 7 Monaten

AI agent usage on SQD Portal is up ~200% in recent weeks. A dev from our community chat was scraping a wallet UI with Hermes. Mid-task, DeepSeek reasoned its way out of it: "I can use SQD Portal's Hyperliquid fills data directly — much more complete than scraping a UI with infinite scroll." No prompt engineering. The model just chose the better and faster path. This is the loop we wanted: Agents pick SQD because it's faster → devs see agents picking SQD → devs ship faster → more agents pick SQD The picks-and-shovels moment for AI x onchain is here.

AI agent usage on SQD Portal is up ~200% in recent weeks. A dev from our community chat was scraping a wallet UI with Hermes. Mid-task, DeepSeek reasoned its way out of it: "I can use SQD Portal's Hyperliquid fills data directly — much more complete than scraping a UI with infinite scroll." No prompt engineering. The model just chose the better and faster path. This is the loop we wanted: Agents pick SQD because it's faster → devs see agents picking SQD → devs ship faster → more agents pick SQD The picks-and-shovels moment for AI x onchain is here.

sqd.ai

14,485 Aufrufe • vor 4 Monaten

Stanford researchers did it again. They just built the agent-native version of Git. When an agent works on a longer task, the run builds up a lot of state. This includes files edited/created, a dev server, a database, installed packages, KV cache, etc. Say the agent is at step 10 and makes a mistake, maybe it misreads a traceback and rewrites a file that was actually fine. The tests start failing, and the run goes off track, although everything through step eight was correct. By default, the agent just tries to fix it, which creates more edits and tool calls. This burns more tokens and grows the context. The other options are a person stepping in to redirect it or restarting the whole run from step one. That's wasteful, because it pays for every model/tool call again and re-prefills the context. Moreover, since an agent's run is non-deterministic, it doesn't reproduce the same early steps anyway. The reason it's hard to just jump back exactly to a previous correct step and resume from there is that the trajectory is only a message log. It records what the agent said and which tools it called, but not the live state underneath. That state includes things like memory, open file handles, child processes, installed packages, /tmp, and KV cache. None of that is in the log. Git can version the files, but it doesn't snapshot the running process or the KV cache. Checking out step eight moves the files back, but the process is still sitting in step-ten memory with a cold cache. Shepherd is a runtime layer by Stanford that records the run as a trace of typed events rather than a flat log. Each agent-environment interaction becomes a commit, similar to Git, but it tracks the live run. Its commit includes the agent process and the filesystem together, copy-on-write, so a branch carries the actual state and not just the files. Going back to a previous step is then a single call that forks from that commit and continues from the exact state. The copy-on-write fork is roughly five times faster than docker commit, and because the prompt prefix through step eight is unchanged, the KV cache is reused over 95% on replay, so early steps aren't reprocessed again. Once the run can be forked, a meta-agent can sit on top and operate it. It watches the trace and reverts as soon as it looks wrong, before the bad write is committed. In practice, it's just Python calling fork, replay, and revert on the trace, rather than a separate control plane wired into the harness. Not everything is reversible though. Files and sandbox changes undo themselves, but a database write has no automatic undo, so it needs a matching undo step set up in advance. Something external, like a sent email or a real charge, can't be undone, so the supervisor's job there is to catch it before it fires. They tested this on a few public benchmarks. On CooperBench, where two agents work on the same codebase, adding a live supervisor took the pair-coding pass rate from 28.8% to 54.7%. It's still early and labeled alpha. The benefit mostly shows up when a run gets branched a lot over a heavy sandbox state, which is exactly where restarting wastes the most tokens and time. If Git was made to make file changes reversible, Shepherd is trying to do the same thing for a live agent run. Shepherd Repo: (don't forget to star it ⭐ ) That said, Shepherd reverts a bad step inside a run. The harness around it, the prompts, tools, and checks the supervisor relies on, still drifts across runs as models and dependencies change. Akshay wrote about making that harness repair itself, where a failing trace gets diagnosed, the fix is verified against the exact input that failed, and the failure is locked as a regression test so it can't recur. Read it below.

Stanford researchers did it again. They just built the agent-native version of Git. When an agent works on a longer task, the run builds up a lot of state. This includes files edited/created, a dev server, a database, installed packages, KV cache, etc. Say the agent is at step 10 and makes a mistake, maybe it misreads a traceback and rewrites a file that was actually fine. The tests start failing, and the run goes off track, although everything through step eight was correct. By default, the agent just tries to fix it, which creates more edits and tool calls. This burns more tokens and grows the context. The other options are a person stepping in to redirect it or restarting the whole run from step one. That's wasteful, because it pays for every model/tool call again and re-prefills the context. Moreover, since an agent's run is non-deterministic, it doesn't reproduce the same early steps anyway. The reason it's hard to just jump back exactly to a previous correct step and resume from there is that the trajectory is only a message log. It records what the agent said and which tools it called, but not the live state underneath. That state includes things like memory, open file handles, child processes, installed packages, /tmp, and KV cache. None of that is in the log. Git can version the files, but it doesn't snapshot the running process or the KV cache. Checking out step eight moves the files back, but the process is still sitting in step-ten memory with a cold cache. Shepherd is a runtime layer by Stanford that records the run as a trace of typed events rather than a flat log. Each agent-environment interaction becomes a commit, similar to Git, but it tracks the live run. Its commit includes the agent process and the filesystem together, copy-on-write, so a branch carries the actual state and not just the files. Going back to a previous step is then a single call that forks from that commit and continues from the exact state. The copy-on-write fork is roughly five times faster than docker commit, and because the prompt prefix through step eight is unchanged, the KV cache is reused over 95% on replay, so early steps aren't reprocessed again. Once the run can be forked, a meta-agent can sit on top and operate it. It watches the trace and reverts as soon as it looks wrong, before the bad write is committed. In practice, it's just Python calling fork, replay, and revert on the trace, rather than a separate control plane wired into the harness. Not everything is reversible though. Files and sandbox changes undo themselves, but a database write has no automatic undo, so it needs a matching undo step set up in advance. Something external, like a sent email or a real charge, can't be undone, so the supervisor's job there is to catch it before it fires. They tested this on a few public benchmarks. On CooperBench, where two agents work on the same codebase, adding a live supervisor took the pair-coding pass rate from 28.8% to 54.7%. It's still early and labeled alpha. The benefit mostly shows up when a run gets branched a lot over a heavy sandbox state, which is exactly where restarting wastes the most tokens and time. If Git was made to make file changes reversible, Shepherd is trying to do the same thing for a live agent run. Shepherd Repo: (don't forget to star it ⭐ ) That said, Shepherd reverts a bad step inside a run. The harness around it, the prompts, tools, and checks the supervisor relies on, still drifts across runs as models and dependencies change. Akshay wrote about making that harness repair itself, where a failing trace gets diagnosed, the fix is verified against the exact input that failed, and the failure is locked as a regression test so it can't recur. Read it below.

Avi Chawla

441,974 Aufrufe • vor 3 Monaten