Overview

What Is a Workspace?

An Osmosis workspace is the platform space where your team manages datasets, training runs, models, deployments, members, and one connected GitHub repository. The connected GitHub repository is the workspace repository. Your local clone is the workspace directory.

Term	Meaning
Platform workspace	The team space in the Osmosis Platform.
Workspace repository	The GitHub repository connected to that platform workspace.
Workspace directory	Your local clone of the workspace repository.

Getting Started

Start with Onboarding to create or join a platform workspace, connect GitHub, clone the workspace repository, and authenticate the CLI. After onboarding, your local workspace directory contains the standard workspace structure:

repository/
├── rollouts/            # AgentWorkflow + Grader code
├── configs/
│   ├── eval/            # Evaluation configs
│   ├── training/        # Training configs
│   └── benchmark/       # Optional configs for benchmark submit
├── data/                # Local test datasets
├── pyproject.toml       # Python project config
├── AGENTS.md            # Canonical AI coding assistant instructions
├── CLAUDE.md            # Claude Code pointer to AGENTS.md
└── .gitignore

configs/benchmark/ is needed only when you use osmosis benchmark submit. It is not part of the required workspace scaffold checked or repaired by osmosis doctor. See Structure & Configuration for a detailed breakdown.

CLI Context

By default, the CLI scopes platform commands to the workspace repository you are currently inside. It reads Git origin, resolves the GitHub owner/repo, and sends that repository identity to the platform.

git remote get-url origin
osmosis dataset list

For platform-only work from another directory, root --workspace selects an exact workspace by name:

osmosis --workspace <workspace-name> dataset list
osmosis --workspace <workspace-name> benchmark runs list

This explicit scope works for the full benchmark command family, platform dataset/model/secret commands, and train / eval list, info, logs, and stop. Source-backed eval submit and train submit also work from any current directory when passed an absolute config path inside the matching repository’s canonical config directory. Local rollout workflows still require a workspace directory. If the CLI cannot resolve the workspace, run:

osmosis doctor

Typical Local Loop

Edit or scaffold a rollout

osmosis rollout init <name>

Push and sync

git add .
git commit -m "add rollout"
git push

Run a local evaluation

osmosis eval run configs/eval/<name>.toml

Pass the managed evaluation gate

osmosis eval submit configs/eval/<name>.toml

Submit training

osmosis train submit configs/training/<name>.toml

Next Steps

Workspace Repository

Learn how GitHub origin scopes CLI commands to a platform workspace.

Structure & Configuration

Understand the files in a cloned workspace repository.

Git Sync

Push to GitHub and let the platform sync rollout code automatically.

Get started

Runs

Workspace

Reference

What Is a Workspace?

Getting Started

CLI Context

Typical Local Loop

Next Steps

Workspace Repository

Structure & Configuration

Git Sync

​What Is a Workspace?

​Getting Started

​CLI Context

​Typical Local Loop

​Next Steps

Workspace Repository

Structure & Configuration

Git Sync

What Is a Workspace?

Getting Started

CLI Context

Typical Local Loop

Next Steps