> ## Documentation Index
> Fetch the complete documentation index at: https://docs.osmosis.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Understand workspace repositories and local workspace directories

## 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](/platform/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:

```text theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/cli.json"]}}
repository/
├── rollouts/            # AgentWorkflow + Grader code
├── configs/             # Training and evaluation configs
├── data/                # Local test datasets
├── pyproject.toml       # Python project config
├── AGENTS.md            # AI coding assistant instructions
├── CLAUDE.md            # Claude Code instructions
└── .gitignore
```

See [Structure & Configuration](/cli/workspace/structure-and-config) for a detailed breakdown.

## CLI Context

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.

```bash theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/cli.json"]}}
git remote get-url origin
osmosis dataset list
```

If the CLI cannot resolve the workspace, run:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/cli.json"]}}
osmosis doctor
```

## Typical Local Loop

<Steps>
  <Step title="Edit or scaffold a rollout">
    ```cli theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/cli.json"]}}
    osmosis rollout init <name>
    ```
  </Step>

  <Step title="Push and sync">
    ```bash theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/cli.json"]}}
    git add .
    git commit -m "add rollout"
    git push
    ```
  </Step>

  <Step title="Submit an evaluation run">
    ```cli theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/cli.json"]}}
    osmosis eval submit configs/eval/<name>.toml
    ```
  </Step>

  <Step title="Submit training">
    ```cli theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/cli.json"]}}
    osmosis train submit configs/training/<name>.toml
    ```
  </Step>
</Steps>

## Next Steps

<CardGroup cols={2}>
  <Card title="Workspace Repository" icon="code-branch" href="/cli/workspace/repository">
    Learn how GitHub `origin` scopes CLI commands to a platform workspace.
  </Card>

  <Card title="Structure & Configuration" icon="folder-tree" href="/cli/workspace/structure-and-config">
    Understand the files in a cloned workspace repository.
  </Card>

  <Card title="Git Sync" icon="rotate" href="/cli/workspace/git-sync">
    Push to GitHub and let the platform sync rollout code automatically.
  </Card>
</CardGroup>