Skip to main content
The open source SDK and the osmosis CLI ship in the same osmosis-ai Python package. The SDK requires Python 3.12 or later.

Install the v0.3 Release Candidate

Pin the current v0.3 release-candidate line so your environment receives RC builds without crossing the next minor-version boundary:
Verify both the package and bundled CLI:
The lower bound must include 0.3.0rc1; a final-release lower bound such as >=0.3 does not select pre-releases in a clean environment.

Optional Extras

Install only the features your project imports: Extras can be combined. A Strands rollout served over HTTP, for example, uses:

Minimal SDK Example

This entrypoint explicitly wires a workflow and grader into LocalBackend, then exposes that backend as a rollout server:
Install the server extra, save the example as main.py, and run the entrypoint:
The Platform sets _OSMOSIS_ROLLOUT_PORT and the server then binds every interface in the managed container; local runs default to 127.0.0.1:8000.
The rollout server does not authenticate inbound callers. Keep it on loopback locally and expose it only through the Platform’s managed environment.
This example demonstrates wiring, not a trainable policy call. For training, use the Strands integration or OpenAI Agents integration so model requests route through the active rollout context.

Platform Authentication and Upgrades

SDK-only local code does not need a Platform login. Commands that submit evaluations or training runs do; follow CLI Installation & Authentication to run osmosis auth login or configure OSMOSIS_TOKEN. If you are upgrading an existing v0.2 harness, read the SDK v0.2 → v0.3 migration guide before changing the dependency, especially if it constructs HarborBackend.

Next Steps

AgentWorkflow

Implement the behavior that produces one rollout sample.

Execution Backends

Wire your workflow and grader into Local or Harbor execution.
Last modified on August 10, 2026