Skip to main content

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

Your local workspace is a git repository — osmosis init runs git init and creates an initial commit automatically. Push the repository to GitHub and connect it to the Osmosis Platform to sync your rollout code for training. Once connected, the platform automatically discovers and syncs AgentWorkflow and Grader definitions from your rollouts/ directory every time you push.

​
Setup

1

Push workspace to GitHub

Create a GitHub repository and push your workspace:
gh repo create my-project --private --source=. --push
Or add an existing remote:
git remote add origin git@github.com:your-org/my-project.git
git push -u origin main
2

Open Git Integration in the Platform

Go to Osmosis Platform and navigate to Integrations > Git.
3

Install the Osmosis GitHub App

Click Connect GitHub and follow the prompts to install the Osmosis GitHub App on your GitHub organization or account. Grant access to the repositories you want to sync.
4

Connect the repository

Select the repository from the list and connect it to your platform workspace. The platform will perform an initial sync immediately.

​
How Sync Works

  • Pushing to the default branch (typically main) triggers an automatic sync.
  • The platform discovers rollout definitions in the rollouts/ directory of your repository.
  • Each rollout subdirectory (e.g. rollouts/my-rollout/) becomes a rollout entity on the platform, available for training and evaluation.
  • Config files under configs/ are also synced so that osmosis train submit can reference them by path.
Git Sync is the source of truth for training. When you run osmosis train submit, the platform reads your rollout code from the synced repository, not from your local working tree. Local edits that haven’t been committed, pushed, and synced will not be picked up by the training run.

​
Sync Status

You can view sync history in the Platform UI under Integrations > Git. Each sync event shows:
StateMeaning
PendingPush detected, sync queued
SyncingPlatform is processing the repository contents
SuccessAll rollouts synced successfully
FailedSync encountered an error (check logs for details)
A manual Sync button is available in the Platform UI to trigger a re-sync without pushing a new commit.

​
Important Notes

  • Only pushes to the default branch trigger automatic sync. Pushes to feature branches are ignored until merged.
  • If a repository is deactivated in the Git integration settings, all rollouts sourced from that repository become inactive on the platform.
Use commit_sha in your training config to pin a training run to a specific commit, ensuring reproducibility even as you continue pushing changes.