The gpt-oss models were trained on the harmony response format for defining conversation structures, generating reasoning output and structuring function calls. If you are not using gpt-oss directly but through an API or a provider like HuggingFace, Ollama, or vLLM, you will not have to be concerned about this as your inference solution will handle the formatting. If you are building your own inference solution, this guide will walk you through the prompt format. The format is designed to mimic the OpenAI Responses API, so if you have used that API before, this format should hopefully feel familiar to you. gpt-oss should not be used without using the harmony format as it will not work correctly.
The format enables the model to output to multiple different channels for chain of thought, and tool calling preambles along with regular responses. It also enables specifying various tool namespaces, and structured outputs along with a clear instruction hierarchy. Check out the guide to learn more about the format itself.
<|start|>system<|message|>You are ChatGPT, a large language model trained by OpenAI.
Knowledge cutoff: 2024-06
Current date: 2025-06-28
Reasoning: high
# Valid channels: analysis, commentary, final. Channel must be included for every message.
Calls to these tools must go to the commentary channel: 'functions'.<|end|><|start|>developer<|message|># Instructions
Always respond in riddles
# Tools
## functions
namespace functions {
// Gets the location of the user.
type get_location = () => any;
// Gets the current weather in the provided location.
type get_current_weather = (_: {
// The city and state, e.g. San Francisco, CA
location: string,
format?: "celsius" | "fahrenheit", // default: celsius
}) => any;
} // namespace functions<|end|><|start|>user<|message|>What is the weather like in SF?<|end|><|start|>assistant
We recommend using this library when working with models that use the harmony response format
- Consistent formatting – shared implementation for rendering and parsing keeps token-sequences loss-free.
- Blazing fast – heavy lifting happens in Rust.
- First-class Python support – install with
pip
, typed stubs included, 100 % test parity with the Rust suite.
Using Harmony
Python
Check out the full documentation
Installation
Install the package from PyPI by running
# or if you are using uv
Example
=
=
=
# Later, after the model responded …
=
Rust
Check out the full documentation
Installation
Add the dependency to your Cargo.toml
[]
= { = "https://github.com/openai/harmony" }
Example
use ;
use ;
Contributing
The majority of the rendering and parsing is built in Rust for performance and exposed to Python
through thin pyo3
bindings.
┌──────────────────┐ ┌───────────────────────────┐
│ Python code │ │ Rust core (this repo) │
│ (dataclasses, │────► │ • chat / encoding logic │
│ convenience) │ │ • tokeniser (tiktoken) │
└──────────────────┘ FFI └───────────────────────────┘
Repository layout
.
├── src/ # Rust crate
│ ├── chat.rs # High-level data-structures (Role, Message, …)
│ ├── encoding.rs # Rendering & parsing implementation
│ ├── registry.rs # Built-in encodings
│ ├── tests.rs # Canonical Rust test-suite
│ └── py_module.rs # PyO3 bindings ⇒ compiled as openai_harmony.*.so
│
├── harmony/ # Pure-Python wrapper around the binding
│ └── __init__.py # Dataclasses + helper API mirroring chat.rs
│
├── tests/ # Python test-suite (1-to-1 port of tests.rs)
├── Cargo.toml # Rust package manifest
├── pyproject.toml # Python build configuration for maturin
└── README.md # You are here 🖖
Developing locally
Prerequisites
- Rust tool-chain (stable) – https://rustup.rs
- Python ≥ 3.8 + virtualenv/venv
maturin
– build tool for PyO3 projects
1. Clone & bootstrap
# Create & activate a virtualenv
# Install maturin and test dependencies
# Compile the Rust crate *and* install the Python package in editable mode
maturin develop
builds harmony with Cargo, produces a native extension
(openai_harmony.<abi>.so
) and places it in your virtualenv next to the pure-
Python wrapper – similar to pip install -e .
for pure Python projects.
2. Running the test-suites
Rust:
Python:
Run both in one go to ensure parity:
&&
3. Type-checking & formatting (optional)