How CLI Context Works
When you run platform commands from inside a workspace directory, the CLI:- Finds the Git worktree root.
- Reads the
originremote. - Normalizes the GitHub repository identity as
owner/repo. - Sends that identity to the platform so the request is scoped to the matching workspace.
osmosis dataset list, osmosis train submit, osmosis rollout list, and osmosis model deploy should be run from inside the cloned workspace repository.
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. |
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.Related Commands
Next Steps
Structure & Configuration
Learn the repository layout and config directories.
Git Sync
Understand how pushes become platform rollouts.