Complete guide to capturing conversations, migrating context across AI platforms, setting up your Pro subscription, and building a centralized memory layer across devices.
Visit the Chrome Web Store, search for ContextMover, and clickAdd to Chrome.
2
Open any supported AI platform
Go to Claude, ChatGPT, Gemini, Grok, Perplexity, or DeepSeek and have a conversation. ContextMover captures your session automatically — there is no setup required and nothing extra to click.
3
Open the sidebar
Click the ContextMover icon in your Chrome toolbar (or press the keyboard shortcut shown in the extension popup). Your captured sessions appear in the list on the left.
4
Migrate to another platform
Select a session, pick a target platform, choose a migration tier (see Tiers below), and clickMigrate. Your context appears in the target AI's input field, ready to continue.
IMG
screenshot — sidebar session list + migrate button
Pro Subscription Setup
Unlock unlimited migration, Attention Engine (Tier 3), and multi-seat access.
Getting Pro
1
Go to contextmover.com and sign in
Use the Google account that you want to be your master account. This email becomes the license holder — write it down.
2
Choose a plan and complete payment
Select Monthly or Yearly. Payment is processed through Stripe (card) or Razorpay (UPI/cards for India). After payment you receive a confirmation email and your account upgrades immediately.
3
Sign in to the extension with the same Google account
Open the ContextMover sidebar → Settings → Sign in with Google. Use the exact same email you paid with. The extension validates your seat against the subscription database on sign-in.
IMG
screenshot — Settings → Sign in with Google
One seat = one Chrome profile. The Pro license is tied to your Google account email. If you sign in with a different Gmail on the extension, it will not inherit the Pro seat unless that email is added as an authorized seat (see Centralized Memory Layer below).
What Pro Unlocks
✓Unlimited session migrations per day (Free tier is capped)
✓Tier 3 — Attention Engine: on-device semantic AI for the highest-quality summaries
✓Google Drive sync: sessions backed up to your own Drive automatically
✓Personal Vault: encrypted sync to your own Supabase project
✓Authorized sub-seats: share your Pro plan across multiple Chrome profiles / devices
✓Priority background indexing: your sessions are indexed first
Centralized Memory Layer
Link multiple Chrome accounts and devices to one Pro master — a single brain for all your AI conversations.
ContextMover's multi-seat architecture lets you sign in to the extension across as many Chrome profiles or devices as you own and treat them all as one unified memory. Your work laptop, home desktop, and secondary browser profile all share the same session library via Google Drive.
Architecture
MasterThe Google account you paid with. Owns the Pro license. Authorizes sub-accounts. Google Drive appdata is attached to this account — all sub-seats sync here.
Sub-seatAny Google account you add to the Pro Seats list. Inherits Pro features. Syncs sessions to the master account's Drive folder.
Adding an Authorized Sub-Seat
1
Open the web dashboard
Go to contextmover.com/account and sign in with your master account.
2
Navigate to Pro Seats
Click Manage Seats in the sidebar. You will see a list of currently authorized emails.
3
Add the sub-account email
Enter the Gmail address of the Chrome profile you want to authorize, then clickAdd Seat. The sub-account is now recognized as a Pro user.
4
Sign in to the extension on the second device / profile
Open ContextMover on the second Chrome profile. Sign in with the sub-account email (Settings → Sign in with Google). The extension recognizes the seat and unlocks Pro features.
5
Connect both profiles to the same Google Drive
In each profile, open Settings → Google Drive → Connect. Sign in with the master account (not the sub-account). Both profiles now read and write to the same Drive appdata folder — sessions captured on device A appear on device B automatically.
IMG
screenshot — Manage Seats page with authorized emails
Connect Drive with the master account email on every device, regardless of which Google account the Chrome profile uses for extension sign-in. This ensures all devices write to the same Drive folder and sync remains consistent.
Sub-account emails must be explicitly listed under your master account's Pro Seats. An email that is not listed does not inherit Pro — even if that person knows your password. Remove seats for accounts you no longer want to authorize.
Tier 1 — Full Context Migration
Verbatim. Every word of your conversation, injected as-is. Best for short-to-medium sessions.
Instant
Speed
Perfect
Quality
≤ ~20k tokens
Session size
Tier 1 copies every single message from the captured session into the target platform's input, preserving the full conversation verbatim. No summarization or compression is applied. This is the fastest option and gives the target AI complete context — but it consumes the target model's context window proportionally.
When to use Tier 1
→ Short debugging sessions (under 30 messages)
→ Sessions where exact phrasing matters (legal, medical, code reviews)
→ You want to pick up exactly where you left off with zero loss
How to run a Tier 1 migration
1
Open the ContextMover sidebar
Select the session you want to migrate from the session list.
2
Click Migrate
A panel opens. Under Intelligence Tier select Full Context (T1).
3
Pick the target platform
Choose Claude, ChatGPT, Gemini, Grok, Perplexity, or DeepSeek from the dropdown.
4
Click Migrate
The extension opens (or focuses) a new tab on the target platform and injects your full conversation into the input field. Press Enter or Submit on the target platform to continue.
IMG
screenshot — migration modal with Tier 1 selected
Tier 2 — Smart Summary Migration
Regex-scored extraction. Pulls goals, decisions, and code snippets — discards filler. Best for medium-to-large sessions.
~1–3 s
Speed
60–80%
Compression
Any
Session size
Tier 2 runs a fast heuristic extraction pass over your session. It scores each message for importance using regex patterns that detect goals, questions, decisions, code blocks, and error messages. Low-signal messages (acknowledgements, filler) are dropped. The result is a dense summary that fits comfortably in the target model's context window while preserving all meaningful content.
When to use Tier 2
→ Long brainstorming or planning sessions you need to continue quickly
→ Sessions that exceed the target model's context window at full verbatim
→ You want most context preserved but can tolerate minor rephrasing
How to run a Tier 2 migration
1
Open the sidebar and select a session
Any session works — Tier 2 handles sessions of any length.
2
Click Migrate → Smart Summary (T2)
The tier selector will show an estimated token count before and after compression.
3
Pick the target platform and click Migrate
The summary is computed client-side in ~1–3 seconds, then injected into the target tab. No data leaves your device during summarization.
IMG
screenshot — Tier 2 selected, showing estimated compression ratio
Tier 2 is the recommended default for most migrations. It balances speed, quality, and token efficiency. Upgrade to Tier 3 only when you need semantic precision over keyword matching.
Tier 3 — Attention Engine Migration
On-device semantic AI (MiniLM-L6-v2 ONNX). Understands meaning, not just keywords. Pro only.
~8–25 s
Speed (modern CPU)
~40–120 s
Speed (older i3/i5)
Highest
Quality
Tier 3 runs a real neural embedding model — Xenova/all-MiniLM-L6-v2 — entirely on your device using WASM ONNX. It converts every chunk of your session into a 384-dimensional semantic vector, then uses an attention scoring algorithm to identify which parts of the conversation are semantically most important. The output is a dense, high-fidelity summary that preserves nuance that keyword extraction misses.
How Tier 3 works under the hood
1. Background indexing: As soon as you capture a session, ContextMover begins chunking and embedding it in a background worker. This happens continuously at low priority so your browser stays fast.
2. Migration takes priority: When you start a T3 migration, background indexing is paused and all ONNX compute is dedicated to your migration job. Other sessions resume indexing after migration completes.
3. Attention scoring: The engine scores each chunk using cosine similarity and positional weighting to compute an importance map across the conversation.
4. Injection: Top-scoring chunks are formatted for the target platform (XML for Claude, Markdown for ChatGPT, plain text for Gemini) and injected.
When to use Tier 3
→ Very long sessions where Tier 2 loses important nuance
→ Research, analysis, or multi-step reasoning sessions
→ You have a modern CPU (2020+) and 1–2 minutes to spare
How to run a Tier 3 migration
1
Ensure the session is indexed
Open the sidebar. Sessions that have been indexed show a semantic search icon. If your session has no index yet, wait for background indexing to complete or select the session and let T3 index it during migration.
2
Click Migrate → Attention Engine (T3)
You may see a tier-confirmation dialog explaining the expected wait time based on session length.
3
Confirm and wait
A progress indicator appears. On a modern CPU (Intel 12th gen / Ryzen 5000+) expect 8–25 seconds. On older hardware (i3 4th gen) expect 40–120 seconds. Your browser remains usable during this time.
4
Review the quality score
After injection, ContextMover shows a quality score (0–100) indicating how much semantic coverage was preserved. A score above 75 is excellent.
IMG
screenshot — T3 progress indicator + quality score after migration
Tier 3 requires a Pro subscription. On very old hardware (pre-2015 CPUs without SIMD AVX2 support) ONNX may be slow — consider using Tier 2 for day-to-day use and reserving T3 for your highest-priority sessions.
Downloading Session Files
Export any captured session as a JSON or Markdown file for archiving or offline use.
Every session ContextMover captures is stored locally in IndexedDB. You can export any session at any time — no internet connection required.
Exporting a session
1
Open the sidebar and find the session
Use the search bar or scroll the session list to locate the conversation you want.
2
Open the session detail view
Click on the session name to open the transcript viewer.
3
Click the Download icon
In the top-right of the transcript viewer, click the download icon. A dropdown lets you choose:
JSON — complete session data including metadata, timestamps, and all messages. Use for re-importing or programmatic access.
Markdown — human-readable transcript. Use for documentation, sharing, or pasting into Notion/Obsidian.
4
Save the file
Your browser's standard Save dialog opens. Choose a location. Done.
IMG
screenshot — transcript viewer with download dropdown open
JSON exports include the full messages array and session metadata. You can re-import a JSON export in a future version of ContextMover (import feature coming soon).
Google Drive Connection
Automatic bidirectional backup of all your sessions. Survives browser wipes, new devices, and re-installs.
ContextMover stores backups in Google Drive's appdata folder — a private, hidden area only your ContextMover extension can read. No one else (not even Google, through the Drive UI) can browse this folder. Sessions sync automatically in the background after every capture.
Which Google account to use for Drive
Always connect Drive with your master account email.
This is the Gmail you used to purchase the Pro subscription — not a sub-account. Every device and Chrome profile (including sub-seat profiles) should authorize Drive with the master account. This ensures all sessions converge into one Drive folder and sync across all your devices seamlessly.
Connecting Google Drive
1
Open ContextMover Settings
Click the settings icon in the sidebar footer (gear icon).
2
Find the Google Drive section
Scroll to Cloud Sync → Google Drive. You will see a Connect button.
3
Click Connect and sign in
A Google OAuth popup opens. Select your master account email (the one on your Pro subscription). Grant the requested Drive appdata permission. Do not select a sub-account here.
4
Wait for initial sync
The first sync uploads all locally captured sessions to Drive. Depending on how many sessions you have, this may take 10–60 seconds. A spinner in the sidebar header shows sync status.
5
Repeat on every device / Chrome profile
On each additional device or profile where you use ContextMover, follow the same steps and authorize Drive with the same master account email. Within minutes, sessions from all devices will appear in every profile.
IMG
screenshot — Settings → Google Drive → Connect with master account selected
IMG
screenshot — Drive sync status indicator in sidebar header
Do not connect Drive with a sub-account email. If each device uses a different Drive account, sessions will not merge and you will have multiple isolated libraries instead of one unified memory layer.
Disconnecting Drive
Go to Settings → Google Drive → Disconnect. This revokes the extension's OAuth token and stops future syncs. Your Drive appdata folder is retained (nothing is deleted from Drive). You can reconnect at any time.
Complete multi-device setup checklist
1Purchase Pro on contextmover.com using your master Google account
2Add sub-account emails in the Pro Seats manager on the web dashboard
3Install ContextMover on every Chrome profile / device
4Sign in to extension with the profile's own Google account (master or sub)
5Connect Google Drive on every profile using the master account email
6Verify sessions from all devices appear in all profiles within ~60 seconds