DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a local agent chat with your own models and tools with Trueforge

Start TrueForge on one machine and chat with an agent that uses MCP tools and skills.

Who it is forA developer who wants to try an agent on their own machine before deciding on a team setup.

The problemBuilding an agent loop with streaming, session storage, tool servers, approvals, and a UI takes significant effort before any real work can start.

The outcomeA working local agent chat connected to a chosen model, with MCP tools and skills available to the agent.

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

  1. Run npx @truefoundry/trueforge@latest in a terminal.
  2. Open the bundled chat UI and connect a model from the catalog or an OpenAI-compatible endpoint.
  3. Add MCP servers and skills from the Initial Setup catalogs.
  4. Create an agent that selects those resources and enable tool approval.
  5. Keep the instance on localhost, because local mode has no login by default and stores data in SQLite.

Prompt for your agent

Using the truefoundry/trueforge repo, start TrueForge locally with `npx @truefoundry/trueforge@latest`, connect the model <model-provider>, and create an agent that uses one MCP server named <mcp-server>. Report the agent's name and the URL of the chat UI. Verify that the agent answers a test prompt and that the session appears in Sessions.

Caveat. The README says local mode is for your machine only and should stay on localhost, so do not expose it to the internet.

Share: 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