Skip to main content
Before you build agents, configure the shared resources TrueForge orchestrates. You do this once in Settings; agents then pick from what you have connected.

​
What is supported out of the box

Each Settings page is backed by its shipped catalog — a YAML file in the TrueForge server (linked above) that lists the presets the UI can offer. Catalogs are discovery lists only. Choosing a preset in the UI asks you for credentials (API key, OAuth, and so on); TrueForge stores the configured resource in its database and then they are used in the agent configuration.
If you remove an entry from the catalog after configuring it in the UI, it will still be available for selection in the agent configuration.
You can also add entries that are not in a catalog — for example a custom OpenAI-compatible model endpoint, or an MCP server at any URL.

​
Changing what the UI offers

If you self-host TrueForge and want a different preset list (add internal MCP servers, trim unused models, ship company skills), point the server at your own YAML files: When unset, TrueForge uses the catalogs shipped with the server.

​
Who can change Settings

With login / OIDC enabled, only users with the admin role can open and change Settings. Everyone can still chat and use agents. Without OIDC (typical local mode), Settings are open to whoever can reach the server.

​
Next step

Once models (and any connectors, skills, or sandbox you need) are configured, create an agent.