Past coding sessions
Your saved Claude Code, Codex and pi transcripts, uploaded into the team knowledgebase so they are searchable alongside everything else.- The picker detects saved histories independently of which agents you installed — a machine that once had Codex and no longer does still has its transcripts.
- Every detected source is selected by default. Only what you leave selected is imported.
- There is an explicit Skip action. Continuing with nothing selected is a real answer.
Historical conversations import as standalone sessions. Backfill verifies their native session identity and preserves immutable retries, but it does not infer or create links to projects, experiments or runs. Nothing is guessed.
A folder of project work
An agent reads the folder, works out what is in it, uploads what it finds and writes a description of it.1
Pick the folder
A browsing picker, with keys beyond the usual arrows:
2
Choose the destination
Select or create the Probe project the work will land in, and the workspace it is filed in. When Weights & Biases is part of the import, this choice covers both the files and the W&B history — one destination, chosen once, before anything starts.
3
Choose how it runs
Review the plan first
Review the plan first
Scanning and reading happen in the installer, and you approve the plan before anything is delivered. Reading progress names its current phase and the analysis steps it has completed. Completed reads are cached, so an interrupted preparation reuses them instead of starting over.
Scan and import in the background
Scan and import in the background
Approves the resulting proposal automatically. Scanning and uploading run as phases of one saved import job and you can carry on immediately.This option is never selected by default — automatic approval is a choice you make, not one you fall into.
What it does with what it finds
- Files become artifacts on the chosen anchor, deduplicated by content.
- References stay references. An artifact recorded as a pointer to bytes you keep elsewhere is never silently turned into an upload.
- A GitHub checkout is recognised. Backfill checks your existing GitHub integration’s access, uses bounded commit history as context, and reuses or attaches the corresponding code source after placement review.
- File and Git reconstruction drafts are saved for explicit publication review — the agent’s reading of the folder is a draft, not a published document. Refreshing the AI summary is a separate step again.
Resuming, and what is not silently added
Imports run in the background. Workers survive a terminal disconnect and retry temporary network failures on their own. After a machine restart, reopening the wizard resumes interrupted jobs from their saved checkpoints. Recovery keeps the original session versions and destination. Folder delivery resumes the saved plan and file versions — new or changed files are not silently added to that delivery during a retry. Rerun to resume. Coverage of current files is reported separately from pending delivery, so “we read everything” and “everything arrived” are never conflated.Weights & Biases in the same pass
Selecting W&B alongside a folder import scans and imports both in the background under the destination you chose up front. There is no later file-plan review to come back to, and your workspace selection is preserved if the current choice changes. For W&B on its own — local run directories or a hosted project — see Weights & Biases.Watching them
The wizard’s main menu shows active import bars directly under the device summary, and Existing imports is the full view.Existing imports
Monitor progress, read results, and resume work that needs attention.