Required Directories
The CLI expects these directories to exist:configs/benchmark/ is optional and used only by osmosis benchmark submit; osmosis doctor and osmosis doctor --fix do not require or create it.
Run a health check from anywhere inside the workspace directory:
rollouts/
The directory where your AgentWorkflow and Grader code lives. Each rollout is a subdirectory containing an entrypoint file (typically main.py) that defines the agent workflow and grading logic.
configs/
Configuration files for evaluation and training, plus optional benchmark submission configs.
The default templates and rollout-specific evaluation and training configs are pre-populated with required fields and commented-out optional settings. See Configuration Files for the full TOML schema reference.
data/
Directory for local dataset files. Upload them to the platform with osmosis dataset upload, then reference the uploaded dataset by name from your training and evaluation configs.
pyproject.toml
Standard Python project configuration for the workspace repository. Individual rollouts can also have their own rollouts/<name>/pyproject.toml files for rollout-specific dependencies.
pyproject.toml
AGENTS.md & CLAUDE.md
AGENTS.md is the canonical instruction file for AI coding assistants. CLAUDE.md points Claude Code to AGENTS.md; it is not a second, independently maintained set of instructions. The nested configs/AGENTS.md adds config-specific rules for files under configs/.
Generated Runtime State
The CLI may create local runtime files under.osmosis/, such as exported metrics. Treat those as local state, not source code.
Next Steps
Workspace Repository
Learn how the CLI resolves the connected workspace.
Configuration Files
Review training and evaluation TOML schemas.