Skip to main content
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

By default, when you run platform commands from inside a workspace directory, the CLI:
  1. Finds the Git worktree root.
  2. Reads the origin remote.
  3. Normalizes the GitHub repository identity as owner/repo.
  4. Sends that identity to the platform so the request is scoped to the matching workspace.
This Git-derived scope remains the default and is required for local source workflows such as rollout list, eval run, and eval upload. Platform-only commands can instead select an exact workspace by name from any directory:
Root --workspace works without a local repository for the full benchmark command family, platform dataset/model/secret commands, and train list, info, logs, and stop; eval list, info, logs, retry, and stop. Without it, those commands continue to use Git-derived scope. eval run, eval upload, eval download, and the rollout commands always resolve the workspace from the current repository, because each one reads or writes a workspace-relative layout on disk. eval submit and train submit are source-backed exceptions. You can invoke them from any current directory with root --workspace, but the config path must be absolute and remain under the containing repository’s canonical configs/eval/ or configs/training/ directory:
The CLI locates the config’s containing Osmosis Git workspace, verifies the selected platform workspace is connected to the same repository, and sends only workspace-name scope for the request.
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

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:
Repair missing scaffold directories:

​
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.

​
Next Steps

Structure & Configuration

Learn the repository layout and config directories.

Git Sync

Understand how pushes become platform rollouts.
Last modified on September 1, 2026