The Agent Harness Is Where the Money Actually Goes

TrueFoundry just shipped TrueForge, an open-source agent harness it markets, almost breathlessly, as the vendor-neutral rival to Claude Managed Agents. The headline number is a 50% cut in agent operating costs. I'd take that with the salt you'd expect from a launch-day benchmark - though, to their credit, the company points at DevRev's public Enterprise-Bench and ships a reproducible benchmark/ folder in the repo rather than just waving its hands over a slide deck. The genuinely interesting part is buried under the pricing talk: where TrueForge actually sits in your stack, and what that position buys you once agents stop being laptop toys and start living inside customer-facing products.

An agent harness is the runtime that turns a raw model into something that does work: it runs the loop, calls MCP tools, manages context, sandboxes execution, and holds the session state. Claude Managed Agents gives you all of that, but only with Anthropic's models on Anthropic's infrastructure. TrueForge runs the same loop against any provider - OpenAI, Anthropic, Gemini, or any OpenAI-compatible endpoint - and routes every call through its own AI Gateway so budgets, rate limits, and guardrails live on your side of the fence. It ships as MIT-licensed code you can run locally with SQLite or host on Postgres plus Redis via Docker Compose or Helm. The repo already has a couple thousand stars and a steady commit cadence, so this is real software, not a press-release vaporware slide.

Source article image
Source image 1

Here's the part worth sitting with. The CEO's framing in The New Stack interview is blunt: a provider selling you a million tokens for fifty dollars has zero incentive to tell you the same job could run on a model that charges fifty cents. The harness decides which model handles which part of the plan, when an MCP server gets called, and what context

Source article image
Source image 2
survives - so whoever owns it owns the cost curve and the security boundary. That's not a small detail. It means the interesting layer of agentic AI is no longer the model; it's the orchestration plane around it, and enterprises are going to want that plane to be something they can read, fork, and point at their own hardware.

None of this makes Anthropic a villain. Claude Managed Agents is still the fastest way to get a working agent in front of a customer, and TrueForge happily treats Anthropic as a first-class provider - its own marketing leans on "any model," not "no Claude." The shift is that "managed" no longer has to mean "walled garden," and that the cost of switching between providers stops being an architecture rewrite. I'm curious how this lands with people actually running agents in production: when you own the harness, do you end up routing different tasks to different models on cost - or does it just become one more layer of config to babysit?

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more