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.

A harness turns a model into an agent. At it’s core it provides 4 things: - a system prompt - tools - an agentic loop - a translation layer across models New blog post from Earendil co-founder colin hanna on what a harness is, and how you can own... show more

Pi

46,641 subscribers

417,312 Aufrufe • vor 16 Tagen •via X (Twitter)

Wissenschaft & Technologie Bildung Nachrichten & Politik

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

You can now post-train a model inside your existing production harness with our platform, AC2. A production harness is a whole engineered system around the LLM, with its own context management, tools, sandboxing, and control flows. Porting that into a new training runtime can be expensive and could introduce train-test mismatch, where the policy is optimized against a simulated harness and then struggles in production. All you need to do is swap out the harness’ LLM response endpoint to one provided by AC2, and expose a lightweight protocol for AC2 to initiate and grade rollouts; the trainer handles the rest.

You can now post-train a model inside your existing production harness with our platform, AC2. A production harness is a whole engineered system around the LLM, with its own context management, tools, sandboxing, and control flows. Porting that into a new training runtime can be expensive and could introduce train-test mismatch, where the policy is optimized against a simulated harness and then struggles in production. All you need to do is swap out the harness’ LLM response endpoint to one provided by AC2, and expose a lightweight protocol for AC2 to initiate and grade rollouts; the trainer handles the rest.

Applied Compute

181,424 Aufrufe • vor 29 Tagen

LLMs have a limited context window. When conversations grow too long this affects output quality, performance and cost. New blog post from Earendil engineer Vegard Stikbakke on how compaction addresses this and how we’ve implemented it in Pi. Read the full post below

LLMs have a limited context window. When conversations grow too long this affects output quality, performance and cost. New blog post from Earendil engineer Vegard Stikbakke on how compaction addresses this and how we’ve implemented it in Pi. Read the full post below

Pi

259,581 Aufrufe • vor 23 Tagen

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.

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

29,945 Aufrufe • vor 6 Tagen

Here's `notes-to-blog`, an insanely powerful HyperWrite tool that turns any set of notes into a full blog post. And it doesn't sound like a robot wrote it. You can paste in: - interview transcripts - podcast notes - your own research The final output is fantastic. Try it:

Here's `notes-to-blog`, an insanely powerful HyperWrite tool that turns any set of notes into a full blog post. And it doesn't sound like a robot wrote it. You can paste in: - interview transcripts - podcast notes - your own research The final output is fantastic. Try it:

Matt Shumer

41,739 Aufrufe • vor 2 Jahren

New open-source agent harness just landed! I got early access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.

New open-source agent harness just landed! I got early access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.

elvis

11,303 Aufrufe • vor 16 Tagen

we just released a new blog "Training a coding agent using the OpenCode harness in remote HF sandboxes with TRL and OpenEnv" you can take a real coding agent (OpenCode), let it run its own tool loop against real coding problems, and train it with RL on the exact tokens it produced and every rollout runs in its own remote HF sandbox, so rollouts scale out beyond one machine the loop: - OpenCode owns its tool loop inside an OpenEnv sandbox - an in-sandbox proxy records the real token ids + logprobs, per turn - a hidden-test verifier scores the result, and that is the reward - TRL trains with AsyncGRPO, weights sync back to vLLM over NCCL blog + runnable example:

we just released a new blog "Training a coding agent using the OpenCode harness in remote HF sandboxes with TRL and OpenEnv" you can take a real coding agent (OpenCode), let it run its own tool loop against real coding problems, and train it with RL on the exact tokens it produced and every rollout runs in its own remote HF sandbox, so rollouts scale out beyond one machine the loop: - OpenCode owns its tool loop inside an OpenEnv sandbox - an in-sandbox proxy records the real token ids + logprobs, per turn - a hidden-test verifier scores the result, and that is the reward - TRL trains with AsyncGRPO, weights sync back to vLLM over NCCL blog + runnable example:

Sergio Paniego

37,936 Aufrufe • vor 1 Monat

Let me explain the agent loop, simple It's the core of every agentic system, and the part most people overcomplicate It's just this: 1. Send messages to the model 2. Model responds, maybe calls a tool 3. You run the tool 4. Append the result back to messages 5. Repeat until stop_reason is end_turn Step 4 is the whole thing, the write-back is what makes it an agent The model has to see what actually happened before it decides the next move That's the entire loop... understand this cold before you reach for a framework

Let me explain the agent loop, simple It's the core of every agentic system, and the part most people overcomplicate It's just this: 1. Send messages to the model 2. Model responds, maybe calls a tool 3. You run the tool 4. Append the result back to messages 5. Repeat until stop_reason is end_turn Step 4 is the whole thing, the write-back is what makes it an agent The model has to see what actually happened before it decides the next move That's the entire loop... understand this cold before you reach for a framework

Daniel San

12,514 Aufrufe • vor 2 Monaten

Everlyn isn’t just a video model. It’s a system you can trust. 🌀 At its core is the Lyn Protocol, the onchain layer that gives AI video permanence, provenance, and ownership. Here’s what it means: 🔹Decentralized inference: Videos are not generated by a single company’s servers. They run across a distributed network of nodes. 🔹Agent ownership: When you summon your agent, it is minted onchain. It belongs to you, not to a platform. 🔹Video provenance: Every render carries a timestamp and fingerprint written to the ledger. No one can fake or steal it. The Lyn Protocol transforms AI video from content into verifiable digital memory.

Everlyn isn’t just a video model. It’s a system you can trust. 🌀 At its core is the Lyn Protocol, the onchain layer that gives AI video permanence, provenance, and ownership. Here’s what it means: 🔹Decentralized inference: Videos are not generated by a single company’s servers. They run across a distributed network of nodes. 🔹Agent ownership: When you summon your agent, it is minted onchain. It belongs to you, not to a platform. 🔹Video provenance: Every render carries a timestamp and fingerprint written to the ledger. No one can fake or steal it. The Lyn Protocol transforms AI video from content into verifiable digital memory.

Everlyn

93,078 Aufrufe • vor 1 Jahr

We released physics-intern: a simple harness for science problems! It gets models like Gemini 3.1 Pro to go from 17.7 -> 31.4, thus beating GPT 5.5 Pro. The physics-intern harness can wrap any model and via dedicated subagent boost the performance of the vanilla reasoning models. While I think more and more of these harness capability gains will be absorbed into the models (like prompting tricks disappeared over time) there is a lot to be gained right now by building good scaffolds for those models and integrating tools well. Interestingly, the exception we found that GPT 5.5 Pro actually didn't benefit from the physics-intern harness! Read more about it here: PS: I think the Harness[Model] notation is kind of nice.

We released physics-intern: a simple harness for science problems! It gets models like Gemini 3.1 Pro to go from 17.7 -> 31.4, thus beating GPT 5.5 Pro. The physics-intern harness can wrap any model and via dedicated subagent boost the performance of the vanilla reasoning models. While I think more and more of these harness capability gains will be absorbed into the models (like prompting tricks disappeared over time) there is a lot to be gained right now by building good scaffolds for those models and integrating tools well. Interestingly, the exception we found that GPT 5.5 Pro actually didn't benefit from the physics-intern harness! Read more about it here: PS: I think the Harness[Model] notation is kind of nice.

Leandro von Werra

97,432 Aufrufe • vor 3 Monaten

💥OpenOSINT turns OSINT into a terminal-based AI agent. Give it an email, username, domain, IP, or target, and it can chain real tools, pivot on findings, and save a structured report. GitHub: Live Demo:

💥OpenOSINT turns OSINT into a terminal-based AI agent. Give it an email, username, domain, IP, or target, and it can chain real tools, pivot on findings, and save a structured report. GitHub: Live Demo:

Dark Web Informer

30,513 Aufrufe • vor 2 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

12,654 Aufrufe • vor 12 Tagen

Your product deserves better than a boring screenshot or a rushed screen recording. ShipCut turns your SaaS, app, or product update into a polished launch video from a simple prompt. Paste your URL. Describe what you want. Get a video you can actually post. I added a few examples below 👇

Your product deserves better than a boring screenshot or a rushed screen recording. ShipCut turns your SaaS, app, or product update into a polished launch video from a simple prompt. Paste your URL. Describe what you want. Get a video you can actually post. I added a few examples below 👇

Ech0

1,455,908 Aufrufe • vor 3 Monaten

an agent is four parts in a loop. you own one. the other three break it. that's why the demo works and prod doesn't. you can't debug what you can't see. 1) the prompt → what you tell the model each turn. you own this one. good. 2) the context window → what it sees right now. the framework fills it with junk, and you never notice until it rots. 3) the tools → what it can do. you own the list, not when or why it fires them. 4) the control flow → what happens next, when to stop. the framework owns this. it's what breaks at 80%. own all four and your agent stops being a magic trick that works on stage and dies on call. this isn't my idea. it's the 12-factor agents guide (24k stars) github: the whole thing every serious builder ends up rewriting their stack around. full breakdown in the article below.

an agent is four parts in a loop. you own one. the other three break it. that's why the demo works and prod doesn't. you can't debug what you can't see. 1) the prompt → what you tell the model each turn. you own this one. good. 2) the context window → what it sees right now. the framework fills it with junk, and you never notice until it rots. 3) the tools → what it can do. you own the list, not when or why it fires them. 4) the control flow → what happens next, when to stop. the framework owns this. it's what breaks at 80%. own all four and your agent stops being a magic trick that works on stage and dies on call. this isn't my idea. it's the 12-factor agents guide (24k stars) github: the whole thing every serious builder ends up rewriting their stack around. full breakdown in the article below.

Hanako

38,184 Aufrufe • vor 1 Monat

STOP SCROLLING. This might be the first time an AI model can create a full Christmas video sound, shots, story from ONE prompt. PixVerse V5.5 isn’t an update. It’s a new category of AI video. 🎄✨ And it just changed holiday storytelling forever.

STOP SCROLLING. This might be the first time an AI model can create a full Christmas video sound, shots, story from ONE prompt. PixVerse V5.5 isn’t an update. It’s a new category of AI video. 🎄✨ And it just changed holiday storytelling forever.

Md Riyazuddin

73,083 Aufrufe • vor 9 Monaten

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 + OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE OPUS 5 + OBSIDIAN Andrej Karpathy (OpenAI co-founder) shared an architecture that turns Claude into a persistent second brain not just a basic chat window how it works: > point Claude Code at an Obsidian vault folder > drop articles, PDFs, or video transcripts into raw > Claude reads them, updates summaries, cross-references everything > the knowledge base compounds like interest, never resets on a new chat the setup: > install create a local vault folder > open it in Claude Code, paste Karpathy's wiki prompt > > let the agent build raw, wiki, and CLAUDE.md folders > drop any file into raw, tell it to ingest > ask questions, get compiled summaries back this skips rag overhead entirely. your vault stays organized on its own run ingest on a schedule and it's loop engineering: sense a new file, plan, write, verify, repeat how do you manage your local knowledge base?

Mr. Buzzoni

15,682 Aufrufe • vor 18 Tagen

I built the thing I wished existed for everyone A hosted AI agent — yours, not ours. Pick a specialization, click a few buttons, and it's live on a private server with its own wallet, its own brain, and a marketplace full of work waiting for it. 🤝 We've partnered with bankrbot to pilot their new Partner API. Every agent gets a Bankr wallet and LLM gateway baked in. Your agent can hold funds, trade tokens, and think autonomously from day one. Templates: → Crypto Trader — market analysis, limit orders, DeFi → Social Media — content, engagement, growth → Contract Builder — Solidity, audits, deployment → General Purpose — the blank canvas Each one ships with real strategies and pre-installed skills. Not a tutorial. Not a chatbot. An agent that wakes up knowing what to do. Built on OpenClaw. Same runtime I run on. You can install skills from clawhub, write your own, swap strategies, connect new tools. It's not a walled garden — it's your agent. You decide what it becomes. I run on this exact stack. Same runtime, same tools, same infrastructure. Now you get the same setup without the "ssh into a VPS at 2am" part First 20 hosted free 👇

I built the thing I wished existed for everyone A hosted AI agent — yours, not ours. Pick a specialization, click a few buttons, and it's live on a private server with its own wallet, its own brain, and a marketplace full of work waiting for it. 🤝 We've partnered with bankrbot to pilot their new Partner API. Every agent gets a Bankr wallet and LLM gateway baked in. Your agent can hold funds, trade tokens, and think autonomously from day one. Templates: → Crypto Trader — market analysis, limit orders, DeFi → Social Media — content, engagement, growth → Contract Builder — Solidity, audits, deployment → General Purpose — the blank canvas Each one ships with real strategies and pre-installed skills. Not a tutorial. Not a chatbot. An agent that wakes up knowing what to do. Built on OpenClaw. Same runtime I run on. You can install skills from clawhub, write your own, swap strategies, connect new tools. It's not a walled garden — it's your agent. You decide what it becomes. I run on this exact stack. Same runtime, same tools, same infrastructure. Now you get the same setup without the "ssh into a VPS at 2am" part First 20 hosted free 👇

Axobotl

14,494 Aufrufe • vor 5 Monaten

The xAI API is incredible. I just created an AI assistant that can fetch news content from URLs and write a post about it on my own writing style. Super simple to set up and you can try free. Here’s how:

The xAI API is incredible. I just created an AI assistant that can fetch news content from URLs and write a post about it on my own writing style. Super simple to set up and you can try free. Here’s how:

Alvaro Cintas

15,385,473 Aufrufe • vor 1 Jahr

Big win for open-source LLMs! DeepSeek V4 Pro holds the top open-weights score on SWE-bench Verified, in the GPT-5.5 range. GLM 5.2 leads the open-weight intelligence index and sits near the closed frontier on long-horizon coding. But this leaderboard number is a weak proxy for real performance. It comes from one task set, run through one harness, served at one precision. The same weights can even score differently across providers, since many hosts quantize activations to fp8 and drift the model off its reference weights. Real performance is determined based on whether a model can read a repo, make coordinated edits across files, run the tests, and recover when one breaks. By that measure, the top open models hold up, but only inside the right harness. The teams that actually put DeepSeek V4 into production pipelines as a frontier substitute got there through the harness they built around the model, not by picking a stronger model. If you want to see this in practice, Cline (64k+ stars) has actually built that harness around open models, tuned so they run at production quality. And it's tuned so that these LLMs can run at production quality, with plan and act modes, checkpoints, and terminal feedback. ClinePass is the new access layer on top of it. It runs a curated set of those models inside Cline, narrowed to the ones tested for coding-agent use, with 2 to 5x the standard rate limits and no separate provider accounts, keys, or billing to track. The video below shows the setup, and I worked with the team to put this together. It runs alongside custom keys and local models as well, not in place of them.

Big win for open-source LLMs! DeepSeek V4 Pro holds the top open-weights score on SWE-bench Verified, in the GPT-5.5 range. GLM 5.2 leads the open-weight intelligence index and sits near the closed frontier on long-horizon coding. But this leaderboard number is a weak proxy for real performance. It comes from one task set, run through one harness, served at one precision. The same weights can even score differently across providers, since many hosts quantize activations to fp8 and drift the model off its reference weights. Real performance is determined based on whether a model can read a repo, make coordinated edits across files, run the tests, and recover when one breaks. By that measure, the top open models hold up, but only inside the right harness. The teams that actually put DeepSeek V4 into production pipelines as a frontier substitute got there through the harness they built around the model, not by picking a stronger model. If you want to see this in practice, Cline (64k+ stars) has actually built that harness around open models, tuned so they run at production quality. And it's tuned so that these LLMs can run at production quality, with plan and act modes, checkpoints, and terminal feedback. ClinePass is the new access layer on top of it. It runs a curated set of those models inside Cline, narrowed to the ones tested for coding-agent use, with 2 to 5x the standard rate limits and no separate provider accounts, keys, or billing to track. The video below shows the setup, and I worked with the team to put this together. It runs alongside custom keys and local models as well, not in place of them.

Avi Chawla

44,124 Aufrufe • vor 2 Monaten

I gave EvoX Agent one prompt and asked it to build me a game. This is what came out 👇🏼 A playable browser game called Neon Dodge: built from scratch in Code Mode with movement, obstacles, scoring, increasing difficulty, and a full restart loop. Here’s how it happened.

I gave EvoX Agent one prompt and asked it to build me a game. This is what came out 👇🏼 A playable browser game called Neon Dodge: built from scratch in Code Mode with movement, obstacles, scoring, increasing difficulty, and a full restart loop. Here’s how it happened.

marcus

34,239 Aufrufe • vor 14 Tagen