What TrueFoundry Adds on Top of TrueForge

TrueForge is the open-source agent harness that runs the core agent loop — model calls, MCP tools, skills, sandboxing, approvals, context management, and session state. You can self-host it and wire up your own credentials, storage, and monitoring. TrueFoundry Agent Harness runs that same harness for you and layers on what a team needs to operate agents in production: centralized governance, end-to-end observability, a fully managed runtime, and enterprise hosting.

​

Governance

The single biggest difference between TrueFoundry Agent Harness and a self-hosted harness is that no API keys or credentials are ever pasted into agent definitions. Models, MCP servers, and skills are all managed through TrueFoundry’s central control plane:

• Models — Provider credentials live in the AI Gateway. Agents reference model names. RBAC controls who can use which models. Budgets, rate limits, and guardrails are enforced at the AI Gateway.
• MCP Servers — Authentication (OAuth tokens, API keys) lives in the MCP Gateway. Agents call tools by name. The AI Gateway handles credential injection, token refresh, and user delegation.
• Skills — Published in the Skills Registry with full versioning and RBAC. Agents pick from a governed catalog. Platform teams control what’s available to whom.

In Claude Managed Agents or LangSmith Managed Deep Agents, developers must register credentials (vault IDs, header arrays with bearer tokens) per agent or workspace. In TrueFoundry, platform teams configure access once and agent builders never handle secrets.

​

Observability

Because Agent Harness runs in the same gateway plane as model and MCP traffic, every agent session is captured with cost, tokens, turns, tool calls, and end-to-end traces — with no extra instrumentation in your agent code. This is one pane of glass across model, MCP, and agent traffic, and it inherits AI Gateway analytics, request logs, OpenTelemetry export, and Prometheus/Grafana. See Observability for the Agent Sessions views, per-session metrics, and traces.

​

Managed runtime

The harness capabilities themselves are part of open-source TrueForge. TrueFoundry runs them for you as a managed, governed service:

• Managed sandbox — colocated with the harness for roughly 1ms execution latency, provisioned on demand, with lifecycle and cleanup handled for you. Secrets never enter the sandbox.
• Sensible defaults — subagents, context compaction, large-result offloading, ask-user questions, and Generative UI are enabled out of the box; there is nothing to wire up.
• Governed approvals — tools are flagged destructive once at the MCP Gateway, so the human-approval gate is enforced for every agent automatically instead of being configured per agent.
• Full observability — every capability above shows up in agent session traces with cost, tokens, and latency.

​

Enterprise hosting

TrueForge in local mode is meant for a single machine. TrueFoundry runs the harness as a shared, production service you can deploy as SaaS (globally distributed), self-hosted, or on-prem — in your own cloud and region, with authentication, RBAC, and the control plane included.

​

Comparison with other harnesses

Claude Managed Agents and LangSmith Managed Deep Agents are both strong hosted runtimes. The differences become clear when you look at how each platform handles builder experience, credentials, governance, observability, and deployment.

​

Next steps