import-gmail

Run the $import-gmail flow: it checks msgvault status, asks which Gmail accounts to link and how far back to sync, sets up OAuth, syncs the mailboxes, and writes contacts to import/gmail/people.csv as candidate rows. Identity resolution and indexing happen later in the Deep Context stage.

The default sync window is 3 years of mail. You can choose any number of years or answer "all" for full mailbox history, which maps to a --sync-after date of 2004-01-01. Reruns rescan the chosen window and skip already-stored messages.

No. The import is entirely free and local: it reuses the synced msgvault archive and writes candidate rows without calling Parallel.ai, RapidAPI, OpenAI, or Modal. Paid enrichment and identity resolution are handled separately by the Deep Context processing layer.

Yes. Pass one --account-email flag per selected account to a single discover command, which syncs all accounts and builds the discovery artifacts together. Running separate invocations per account rewrites the manifest and can leave only the last account available for import.

Step 5 requires the all-account auth-check to return status ok for the exact selected set. A local account row does not prove the refresh token is still valid, so missing or expired tokens must be re-authorized with add-account or add-account --force-auth before any mailbox sync begins.

None during import. The msgvault archive stores messages locally, and the importer reads only contact and interaction metadata from SQLite. Message bodies, subjects, snippets, and attachments are never sent to identity providers by this skill.