Starting an import
- Wizard
- Command
Import research work
The picker, the two run modes, and what gets reviewed before it writes.
Existing imports
Watch one, read its result, resume what was interrupted.
What it reads
References remain references. A file recorded as a pointer to bytes you keep elsewhere is never silently turned into an upload.Sessions import as standalone. 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.
Reviewing before it writes
Folder imports either review placement before writing, or use the explicit automatic-approval option — which is never selected for you. File and Git reconstruction drafts are saved for explicit publication review. The agent’s reading of your folder is a draft until you say otherwise. The import writes each project’s description and its own block on the project’s Overview page. No later step generates the rest of the page: a project’s summary is kept by whoever records work on it, your coding agent or the Probe daemon.What is left out
Not everything in a folder is research. The agent leaves out code for a shipped product (its web or mobile app, CLI or service, with that product’s tests and assets), vendored code, build output and caches; research code, configs, notebooks, results, logs and checkpoints stay, even inside a product’s repository. The review lists each left-out row with its file count and why, and nothing in it is uploaded. Left-out files are recorded as excluded and stay settled when their bytes change. To classify them again:Resuming
Transcripts only
Protocol-2 transcript imports require a compatible engine, API and tap release. An older combination imports at the earlier protocol rather than failing.