Skip to main content
For a guided walkthrough, see Create an agent.

AgentManifest YAML spec

The YAML below shows a complete agent spec. See AgentManifest for a description of every field.

Reference

AgentManifest

AgentManifest is the shape of the spec saved in the Agent Registry. It shares all agent configuration fields below. Note that variables is a map of objects with default_value and description, not plain string values. Callers can override these with plain string values at invocation time when running the agent.

Agent configuration

The fields below make up the agent configuration shared by the AgentManifest.

model

model.params

Known parameters are listed below. Any additional provider-specific keys are also accepted.

messages[]

Seed messages injected after the system prompt and before the user’s input. Only user messages are supported. These are definition-time seed messages on the manifest — distinct from runtime UserMessage turn input, though both use type: "user.message".

skills[]

Each entry is a discriminated union. Use type to select the variant. Registered skill (type: "truefoundry-skills-registry")

mcp_servers[]

Each entry is a discriminated union. Use type to select the variant. Tool selectors support special tags that use MCP tool annotations: Tags and explicit tool names can be combined in the same list. Shared tool fields (both variants): Registered MCP server (type: "truefoundry-mcp-registry")

sample_inputs[]

Example inputs shown on the Agent Chat page (via “Try Now” on the agent listing). Each entry has:

response_format


config

config.sandbox

config.dynamic_sub_agents

config.context_management

config.context_management.compaction

config.context_management.large_tool_response

config.generative_ui

config.ask_user_questions