Skip to main content
A project is the unit you optimize. It owns its data and experiments while giving the application one stable project to select. Each Model Distillation project is backed by exactly one Weights & Biases project, which stores its traces. This page shows you how to create a project, connect your application to the proxy with the project’s OpenAI-Project value, and confirm that the proxy records traces you can use as training data.

Create a project

To create a project, follow these steps:
  1. From Projects, select Create or import a project.
  2. Configure the following fields:
    • W&B project: Select Create new to create a Weights & Biases project in the selected entity, or Import existing to connect a Weights & Biases project you already have. Importing doesn’t change the existing project’s data. A Weights & Biases project can back only one Model Distillation project per entity.
    • Project alias: Identifies the project in Studio URLs and Management API paths. The UI suggests a name derived from the Weights & Biases project name. Use lowercase letters, digits, and hyphens, up to 64 characters. The project alias can differ from the Weights & Biases project name.
    • Initial model: The model that serves version 1 while you collect traces and train alternatives.
  3. Select Create project.
Every new project requires an initial model so it can route traffic as soon as its routing deployment is applied.
The project alias is the alias path segment. Set project to the Weights & Biases project name and project_mode to create or import. Supply at least one routing target. Creation fails when targets is missing or empty.
For the complete schema, see Create a Model Distillation project.

Connect the application

After you create the project, point your application at the proxy, which routes its traffic through the project and records it as traces. Use the following client and request configuration: Replace your-team/ticket-classifier with the OpenAI-Project value that Studio shows in the project header and on the project’s settings page. The value is the entity and the Weights & Biases project name, not the project alias:
The proxy forwards all normal Chat Completions fields, replaces router with the selected target’s provider model, and applies that target’s stored parameter overrides. Requests without forge.project_version use version 1. To pin another version, add "forge.project_version": "2" to metadata.

Verify useful traces

Before you collect a large dataset, confirm the following:
  • Successful calls appear in the project’s request chart.
  • Traffic share matches routing weights.
  • A stable gen_ai.conversation.id groups each conversation in the W&B Weave Agents view.
  • Tool definitions, response formats, and multi-turn messages appear in the recorded request.
  • Failed provider calls are visible for debugging but excluded from training data.
When these checks pass, the project records traces that can serve as training examples.
Send the complete message history on every call. Each trace becomes one self-contained training example representing the assistant response produced for that history.
Last modified on October 26, 2026