TrueForge

Overview

TrueForge is an open-source agent harness with three parts: a core server that runs the agent loop, an HTTP API with a TypeScript SDK, and a chat UI with a React UI SDK. It orchestrates bring-your-own model providers, MCP servers, and sandbox services, while handling planning, tool execution, context management, approvals, and session state. It supports local mode with SQLite and hosted mode with Postgres and Redis.

Key Features

• Any model provider: OpenAI, Anthropic, Google Gemini, other catalog providers, or any OpenAI-compatible endpoint.
• MCP tools: remote MCP servers with header auth or OAuth, including in-chat authorization.
• Skills: git-backed SKILL.md instruction packs loaded on demand in the sandbox.
• Sandbox as a tool: isolated code and file execution provisioned only when needed, with secrets kept in the harness.
• Human checkpoints: tool approval, ask-user-questions, and Generative UI in chat.
• Context engineering: subagents, deferred tool loading, Code Mode, large-result offloading, and compaction.

Use Cases

• Personal use on a local machine as a single process with SQLite, similar to Claude Desktop.
• Team or production shared deployments with Postgres, Redis, and optional OIDC login.
• Automating agent sessions and streaming turns from application code via the HTTP API and TypeScript SDK.
• Embedding a customized chat interface in a React app with @truefoundry/trueforge-ui.

Getting Started

• Run npx @truefoundry/trueforge@latest for a local quickstart.
• Use the Quickstart guide to run TrueForge locally or with Docker Compose, Kubernetes, or Railway, then connect models, tools, and skills and build a reusable agent.

Deployment & Requirements

• Local mode runs as a single process with SQLite storage and no extra infrastructure.
• Hosted mode uses Postgres for storage and Redis as extra infrastructure; it can run with Docker Compose, Helm, or Railway.
• Shared deployments can enable optional OIDC login with admin versus user roles.

Before You Adopt

• License: MIT. Review its terms before using, modifying, or distributing the project.
• Local mode defaults to no login and stores data in a local SQLite file, which matters for access control and privacy.
• Sandbox code and file execution currently depends on Daytona as the available sandbox provider.