Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt

Use this file to discover all available pages before exploring further.

TrueFoundry Agents are available on SaaS only.
Build agents natively on TrueFoundry. You bring the intent — TrueFoundry handles everything else.

Bring Your Own Model

Connect any LLM available through TrueFoundry’s AI Gateway. Switch models without rewriting your agent.

MCP Server Integration

Plug in any MCP server to give your agent tools — file access, web search, APIs, databases, and more.

Sandbox Access

Agents run in a secure execution environment. Code execution, file operations, and external calls are sandboxed by default.

ReAct Agent Framework

Agents follow a reason-then-act loop out of the box. A built-in chat interface lets you interact with them immediately.
TrueFoundry manages the platform problems so you don’t have to: context window management, tool call orchestration, conversation history, system prompt handling, and multi-turn state. You focus on building and shipping.

Creating a New Agent

On the Agent Registry page, click Create New Agent and select Build Agent on TrueFoundry.
Create New Agent button on the Agent Registry page
Create New Agent dialog with Build Agent on TrueFoundry highlighted
This opens the Agent Playground where you build and test your agent.
1

Select a model

Choose any model available through AI Gateway.
2

Write your instructions

Add a system prompt that defines the agent’s behavior, persona, and constraints.
3

Connect MCP Servers

Click the + next to MCP Servers to open the tool selection dialog. Search for MCP servers, browse available tools, and select the ones your agent needs.
4

Add Skills (optional)

Click the + next to Skills to attach reusable SKILL.md instructions from the Skills Registry. See Mounting Skills for the full flow.
5

Run and iterate

Use the chat interface to test the agent. Adjust the prompt, switch models, or add more tools until the agent behaves as expected.
Agent Playground with model selection, system prompt, and MCP servers
Tools and MCP Servers selection dialog

Saving the Agent

Once you’re satisfied with the agent’s behavior, click Save Agent in the top-right corner. The dropdown gives you two options:
  • Save New Version — Update an existing agent with your changes.
  • Save New Agent — Create a brand-new agent from the current configuration.
Save dropdown with Save New Version and Save New Agent options

Agent Configuration

To edit an agent’s configuration after creation, click Manage on the Agent Registry page.
Agent Registry with Manage button highlighted on a TrueFoundry agent
The agent form contains the following fields:
FieldDescription
NameA unique name for the agent within your organization.
DescriptionA short description of what the agent does.
TagsOptional tags for categorization and search.
CollaboratorsTeam members or groups with Agent Manager (edit) or Agent Access (use) permissions.
Agent edit form showing name, description, and collaborator access control
For details on prompt management and versioning, see Prompt Management.

Mounting Skills

Attach reusable Skills — versioned SKILL.md instructions and supporting files — to a TrueFoundry Agent so the model picks them up at runtime. Skills require the agent’s Sandbox to be enabled.
1

Open the Skills selector

Click the + button next to Skills in the Playground sidebar. The selector lists every skill you have access to, grouped by Repository. Each row has a version dropdown — defaults to the latest, but you can pin any older version.
Skills selector in the Agent Playground listing available skills with version pickers and a preload toggle
2

Pick the skills the agent needs

Check the skills you want. Each selected skill becomes a skills[] entry on the agent.
Within a single agent, two skills cannot share the same name even if they live in different Repositories. The selector greys out the second skill and shows a tooltip explaining the conflict — pick one or use a differently named copy.
3

(Optional) Toggle Preload SKILL.md per skill

Each selected skill has a small icon toggle that controls Preload SKILL.md:
ModeBehavior
Off (default)Only the skill’s name and description are exposed upfront. The body is loaded on demand when the agent decides the skill is relevant.
OnThe full SKILL.md body is loaded upfront. Higher upfront context cost, but no extra step at runtime.
Turn preload on for short, always-relevant skills (e.g. a 200-line style guide). Leave it off for long, situational skills that only fire occasionally.
4

Test, then save the agent

Send a prompt that should trigger the skill, then click Save Agent to persist the skill list. Subsequent runs of the agent mount the same skills automatically.

Access Control for Skills

Skills inherit access control from their parent Repository — the caller must have read access on each skill’s Repository to mount it. When end-users invoke a saved agent, the Gateway treats READ on the agent as implicit access to all skills attached at save time, so they don’t need direct permissions on the underlying skill Repositories.

Sharing and Using Agents

Once published, every agent appears on the Agent Registry page. Agents you have access to show Try and Manage actions.

Try an Agent

Click Try on any agent in the registry to open a standalone chat page.
Agent Registry with Try button highlighted on a TrueFoundry agent
This is a full conversational interface with chat history — ready for end-users to interact with immediately.
Standalone agent chat page for interacting with a published agent

Integrate with Code

Every agent on TrueFoundry is API-accessible. The API contract is currently under active development and will be documented in the coming weeks.

Monitoring

Every TrueFoundry agent execution is traced end-to-end. Traces capture each step of the agent’s reasoning loop — LLM calls, tool invocations, sandbox executions — along with cost, token usage, and latency. Navigate to AI Monitoring > Request Traces and filter by span type AgentResponse to inspect individual agent runs.
Request Traces showing agent execution spans, cost, and token usage