Workspace Repository

A workspace repository is the GitHub repository connected to one Osmosis platform workspace. The platform creates it from the Osmosis workspace template or connects an existing repository, then uses Git Sync to discover rollouts and configs. Your local workspace directory is a clone of that repository.

How CLI Context Works

When you run platform commands from inside a workspace directory, the CLI:

Finds the Git worktree root.
Reads the origin remote.
Normalizes the GitHub repository identity as owner/repo.
Sends that identity to the platform so the request is scoped to the matching workspace.

This means commands like osmosis dataset list, osmosis train submit, osmosis rollout list, and osmosis model deploy should be run from inside the cloned workspace repository.

git remote get-url origin
osmosis dataset list

The origin remote must point to a GitHub repository connected to your platform workspace. If the repository was renamed on GitHub, update your local remote before running CLI commands.

Common Requirements

Requirement	Why it matters
Git worktree	The CLI uses the Git root as the workspace directory.
GitHub `origin` remote	The CLI maps `origin` to the platform workspace.
Platform login	Platform commands require `osmosis auth login` or `OSMOSIS_TOKEN`.
Required directories	`rollouts/`, `configs/training/`, `configs/eval/`, and `data/` make the directory a valid Osmosis workspace directory.

configs/benchmark/ is optional and used only by osmosis benchmark submit. osmosis doctor and osmosis doctor --fix neither require nor create it. Run a local health check when something looks wrong:

osmosis doctor

Repair missing scaffold directories:

osmosis doctor --fix

Repository Ownership

Workspace creators usually create the repository from the platform during onboarding. Invited members should clone the existing workspace repository rather than creating a separate one. Only workspace owners and admins can manage GitHub repository connection settings in the platform. Members can clone and use the repository if they have GitHub access.

osmosis template list
osmosis template apply multiply-local-strands
osmosis rollout init my-rollout
osmosis eval submit configs/eval/my-rollout.toml
osmosis train submit configs/training/my-rollout.toml

Get started

Runs

Workspace

Reference

How CLI Context Works

Common Requirements

Repository Ownership

Next Steps

Structure & Configuration

Git Sync

​How CLI Context Works

​Common Requirements

​Repository Ownership

​Related Commands

​Next Steps

Structure & Configuration

Git Sync

How CLI Context Works

Common Requirements

Repository Ownership

Related Commands

Next Steps