You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Split the agent server's two conflated responsibilities — rollout orchestration (/run) and the agent loop (/responses) — into separate, independently swappable concerns. decouple rollout orchestration and agent harnesses #2858
Establish canonical patterns for how agents and resources servers use the shared Sandbox API, closing gaps in the current sandbox documentation. epic: canonical sandbox patterns #2763
Improve data preparation with a unified dataset preparation workflow and standard source-format adapters so contributors onboard data once and the format works everywhere. epic: dataset preparation #1338
Make rollout failures bounded, visible, and recoverable — report failures as policy-neutral facts so callers decide whether to retry, replace, mask, omit, or stop, rather than Gym silently changing eval/training semantics. Make rollout failures bounded, visible, and recoverable #2750
Make Python object-oriented agent implementations — starting with NOOA — pluggable into Gym without requiring Gym-specific FastAPI routes or cookie handling. Object-oriented agents in Gym #2096
Release date: October 7, 2026
This is a summary snapshot of the planned work targeted for the NeMo Gym v0.7.0 release. Updates will be managed in the GitHub Project.
1. Runtime & Agent Infrastructure
Core platform for running agents, evaluations, and workflows.
2. Training
Capabilities for creating training data, optimizing policies, and improving agents.
3. Evaluation & Benchmarks
Measuring, comparing, validating, and understanding agent performance.
4. Ecosystem
Expanding supported environments, frameworks, and deployment targets.