Credentials. Shared MCP header auth, OAuth tokens, and model keys are stored in the harness, so limit who can view or change these connections.
Who it is forA platform engineer who must give several teammates the same models, tools, and sandbox behind a login.
The problemLocal mode is single-user and has no login by default, so a team needs a shared, multi-replica deployment.
The outcomeA hosted TrueForge deployment with shared catalogs, optional OIDC login, and a sandbox available to agents.
What you need first
- A machine where you can run npx, for the local quickstart
- API access to at least one model provider you plan to connect (OpenAI, Anthropic, Google Gemini, or an OpenAI-compatible endpoint)
- Optional: credentials for any remote MCP server you plan to use (header auth or OAuth)
- For hosted mode: Postgres and Redis, plus Docker Compose, Helm, or Railway
Steps
- Choose hosted mode, which uses Postgres and Redis for storage.
- Deploy with Docker Compose, Helm, or Railway by following the Quickstart guide.
- Connect shared models, MCP servers, skills, and the sandbox in Initial Setup.
- Enable optional OIDC login from the Setup Login guide before inviting teammates.
- Create one shared agent and confirm a teammate can run it and see the session in Sessions.
Prompt for your agent
In the truefoundry/trueforge repo, deploy hosted mode using <deployment-method> (Docker Compose, Helm, or Railway) following the Quickstart, then connect one model and one MCP server. Report the deployment URL and confirm that a login is required. Verify that a shared agent runs successfully for a second user.
Caveat. The README gives no setup steps for Helm, Docker Compose, or Railway beyond naming them, so follow the linked Quickstart for exact instructions.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page