Skip to main content
Three ways in, depending on where the runs are.
The guided path is the wizard. npx probe-research → Import research work handles a folder and its W&B history together: you pick the destination Probe project once, up front, and both are scanned and imported in the background. The commands below are for scripts, and for W&B on its own.

​
Local run directories

For the wandb/ trees sitting on a machine or a shared volume.
discover is worth running first: it lists every W&B run directory under the root and the fidelity each would import at, so a tree with partial data does not surprise you afterwards.
--project names an existing Probe project and is required. A W&B project does not map one-to-one onto a Probe project — forcing that guess is how imports end up in the wrong place — and this step runs after a file import, so the destination already exists.

​
A hosted project

--dry-run reports the plan and writes nothing. Use it.

​
One run’s history into an existing Probe run

Mirrors one W&B run’s metric history into a Probe run you already have — for when the Probe run was opened by your own tooling and the curve lives at W&B.

​
A live connection

On the Integrations page, a W&B connection gets its own named team workspace and independent Live sync and Backfill controls.
Live sync has a cutoff. It covers runs created after you activated it. A run that already existed is history — use backfill for it.This matters when testing: attaching to a run that has already finished tests backfill, not live sync. Watch the connection’s last-sync time rather than inferring from whether rows appeared.

​
Removing a connection

A W&B connection, connected or disconnected, has one Delete flow on the Integrations page. It shows what it will remove once, asks you to confirm, and then removes the key, the source attachments, the sync history and the data it imported, together, in the background, with progress you can follow.
Detaching a W&B source deletes what it imported. The runs it brought into Probe, and any work attached to them, are deleted permanently; runs created in Probe and the W&B project itself are not touched. To keep the imported runs, leave the source attached and pause its sync.

​
Source-backed runs

An imported run can stay source-backed: its metric history remains at W&B rather than being copied wholesale. Authenticated chart reads then fetch bounded ranges on demand and label partial or sampled coverage explicitly — a chart that is showing you a window says so rather than implying it is the whole curve.

​
Timestamps

Imported runs carry backdated wall clocks where the source supplied them. Rows with no timestamp at all are skipped rather than stamped with the import time — so an imported history does not appear to have all happened on the afternoon you imported it.If you are writing your own importer against the SDK, pass wall_clock explicitly. Omitted, it stamps at ingest time, which is right for a live loop and wrong for a replay.

​
Folder imports that include W&B

The wizard’s folder import can do both in one pass: select or create the destination Probe project up front — it covers the files and the W&B history together — then scanning and importing run in the background with no later file-plan review.

​
What it does not do

Probe does not write back to W&B. The import is one-directional.

Instrumenting new runs instead

For runs you have not launched yet, probe.init() replaces wandb.init().