1. Choose the context
Use the composer, Selection shortcut, Screenshot shortcut, or optional on-page controls to attach the exact browser context you want. ContextPorter supports selected text, page text, sanitized DOM, visible screenshots, full-page screenshots and local files.
2. Review the turn
Attached context is visible in the ContextPorter UI. Sent screenshot and text context remain associated with the user message so you can see what accompanied the turn.
3. Send to the provider you chose
ContextPorter sends the message and explicitly attached context to the selected supported AI provider using the Chromium profile session available to that provider. ContextPorter does not proxy the content through its own backend.
4. Continue the conversation
Where supported, ContextPorter keeps the provider's native conversation continuity. Switching providers is an explicit action and the UI asks whether you want to start fresh or continue with local conversation context.
5. Keep local control
Settings, lightweight recent-chat metadata and local attachment references stay inside the Chromium profile. Screenshots, uploaded files and materialized provider artifacts are stored in extension-owned IndexedDB with bounded retention and a local cache limit.
Optional page tools
Persistent on-page Selection and Screenshot buttons are optional. Enabling them requires separate all-sites access because the controls must be present on normal webpages. They can be turned off independently in Settings.