Corvio Help Center · Local import

Import local agent work into Corvio

Local data requires a local process. Corvio's remote MCP cannot scan your computer, so use the signed local importer directly or ask a local agent to follow the reviewed Skill.

Updated 2026-08-19

Choose the local path

In a terminal, run corvio agent-history detect to inspect supported local sources. To let an agent help, install or send it the official corvio-import-local-work Skill and ask it to prepare the discovery receipt.

Supported sources depend on the signed importer build and operating system. Detection should report source kinds and counts before any conversation body is read or uploaded.

  1. Install the official local importer and sign in through its device link.
  2. Run corvio agent-history detect.
  3. Review detected tools, paths, counts, and unsupported sources.
  4. Continue with corvio agent-history import only after the plan is clear.

Consent in three separate stages

Metadata discovery does not authorize reading bodies. Reading selected chat or file bodies does not authorize upload. The CLI asks separately for source selection, sample/body collection, and final upload confirmation.

Exclude secrets, credentials, private keys, browser profiles, caches, unrelated repositories, and sources you do not own. If source ownership is unclear, stop rather than widening the scan.

Keep the receipts

A complete import returns a discovery summary, selected-source manifest, upload plan, session ID, and final status. Keep the session receipt so retries do not create an untraceable second import.

For an unsupported source, use manual file upload or export from the source tool. Do not teach an agent to crawl arbitrary home directories as a fallback.