TrueForge 0.2.0 turns an open agent harness into an operations-ready scheduler

TrueFoundry’s open-source agent harness reached a stable 0.2.0 release on September 18 with a decidedly operational feature set: persisted cron schedules, session metrics, tighter resource ownership and a Helm chart promoted from release candidate to stable. The release notes describe a production-oriented step rather than a new model or prompting technique.

Scheduling becomes a first-class object

TrueForge can now save cron schedules for existing agents, expose them through /api/v1/schedules, validate scheduling policy at write time and claim due runs through a single dispatcher. In distributed deployments, a dedicated controller process runs those periodic loops while the server handles requests; standalone deployments keep the controller in-process. The accompanying 0.2.0 Helm chart pins the stable app and image versions for cluster installs.

That distinction matters for data and analytics agents. A scheduled metadata audit, warehouse-health check or report-generation job is no longer just a recurring prompt: it becomes a persisted resource with run history, pause and resume controls, and an identifiable owner.

Ownership is part of the runtime

The same release tightens who can see and operate those resources. According to the release notes, users may read sessions, turns, events, metrics, schedules and runs they created, or resources attached to an agent they manage. Mutating a session or schedule remains restricted to its creator. TrueForge also added an optional OIDC email allowlist, agent-level external authorization and mutual TLS for selected internal hops.

The guardrails extend to tools. Request-scoped MCP servers and skills can be supplied without appearing in the shared settings catalog; destructive MCP tools retain approval by default, while read-only selections can clear it. Remote MCP responses are capped at 50 MB to reduce the risk of oversized tool output exhausting the process.

A useful boundary for NL2SQL teams

TrueFoundry’s original TrueForge architecture post presents the harness as the layer around a model: the execution loop, context compaction, sandboxing, approvals and persisted state. Models and MCP servers remain bring-your-own, and the sandbox is invoked as a tool only when code execution is needed.

The company’s own 14-task Enterprise-Bench comparison claimed roughly 11 solved tasks for both TrueForge and Claude Managed Agents, with TrueForge using fewer tokens and costing about 30% less when both used Opus 4.8. That result is vendor-run, uses an LLM judge and is not a text-to-SQL benchmark, so it should be treated as a reproducible claim rather than independent proof.

The stronger signal in 0.2.0 is architectural. For teams operating database agents, the release makes schedules, authorization and observability properties of the harness instead of one-off application code. The remaining evaluation question is whether those controls hold under real multi-tenant workloads and long-running database tasks; the release notes provide the machinery, not that production evidence.