Configuration System
NeMo Gym uses YAML configuration files to define Model, Resources, and Agent servers. Each server gets its own configuration block, providing modular control over the entire training environment.
How Servers Connect
A training environment typically includes all three server types working together. The Agent server config specifies which Model and Resources servers to use by referencing their server IDs. These references connect each training environment together — the Agent knows which Model to call and which Resources to use.
Config File Locations
Each server type has a dedicated directory with its implementations and their configs:
Server Block Structure
Each config file defines a server using this structure:
Different server types have additional required fields (e.g., domain for resources servers, resources_server and model_server for agents). See Configuration for complete field specifications.
Config files in NeMo Gym often use the same name for both server ID and implementation:
These serve different purposes:
-
Server ID (
example_single_tool_callon line 1): Your chosen identifier for this server instance. Used in API requests and when other servers reference it. You could name itmy_weatherorweather_prodinstead. -
Implementation (
example_single_tool_callon line 3): Must match the folderresources_servers/example_single_tool_call/. This tells NeMo Gym which code to run.
Examples often use matching names for simplicity, but the two values are independent choices.
- Configuration for complete syntax and field specifications
- Configuration for troubleshooting configuration related errors