ContextIQ on Chrome
A one-click DOM picker that sends any element from your live storefront straight into the @Atlas chat — section copy, broken hero, missing alt text, anything you can hover.
ContextIQ is the BoostEcom Chrome extension. It runs only when you open it on a tab — no background polling, no telemetry, no personal data collection. It does one thing: lets you select any element on any storefront, captures its selector + outerHTML, and forwards the context to @Atlas so the next message in the chat already knows what you're looking at.
Prerequisites
Before you start
- A BoostEcom account (sign up free).
- Chrome, Edge, Brave, or any Chromium-based browser.
- The store you want to ask @Atlas about — your own or a competitor's, doesn't matter, the extension works on every URL.
Step 1
Install ContextIQ
Open the ContextIQ marketplace listing and click Add to Chrome. The extension requires three permissions:
| Permission | Why |
|---|---|
| activeTab | So ContextIQ can read the page you're on when you click its icon. |
| storage | To remember your BoostEcom session locally — no server roundtrip per pick. |
| <all_urls> | DOM picking works on every store, not a whitelist. |
There is no tabs, no webRequest, no cookies permission. The
extension cannot read pages you don't have open and cannot make
background requests on your behalf.
Step 2
Pin your first element
Open any storefront. Click the ContextIQ icon — a sidebar slides in from the right. Click Pick element. Hover anywhere on the page, the element you'd select highlights blue. Click to commit.
The sidebar now shows:
- A live preview of the selected node (image, text, or component).
- The CSS selector path (
section.hero > h1.headline). - A textarea where you type your ask — "rewrite this in a luxury tone" or "audit the alt text + heading hierarchy".
Hit Send. The selector + outerHTML + your prompt land in a fresh
@Atlas conversation on boostecom.app. Switch to that tab to read the
response.
Step 3
What @Atlas does with the DOM context
The HTML fragment becomes part of the prompt @Atlas receives, so the response is grounded in what you actually showed — no "based on what a typical hero section looks like" hallucinations.
Common asks that work well:
- Copy rewrites — "rewrite this h1 in three tones: luxury, playful, urgent".
- A11y audits — "what's wrong with the alt text and heading order on this section?".
- Liquid refactors — "rewrite this section schema with cleaner blocks and the right preset defaults".
- Cross-store comparisons — pin one section on your store and another on a competitor's, ask @Atlas which converts better and why.
Step 4
Keyboard shortcuts
| Shortcut | Action |
|---|---|
| Alt + C | Open / close the ContextIQ sidebar. |
| Alt + P | Toggle the DOM picker on the active tab. |
| Escape | Cancel the picker without sending. |
Remap them from chrome://extensions/shortcuts if they collide with
your store admin shortcuts.
Troubleshooting
When the picker doesn't fire
- Iframes — the picker is restricted to the top frame by Chrome's security model. If you need to pick inside an embedded checkout iframe, open the iframe URL in its own tab first.
- Shadow DOM — ContextIQ pierces open shadow roots automatically. Closed shadow roots (rare on real storefronts) aren't pickable — that's a Chrome limitation, not ours.
- Session expired — if the sidebar shows "Sign in to BoostEcom", click the link and re-authenticate. ContextIQ stays signed in for 30 days after the last picker action.
Privacy
What we collect
- The selector + outerHTML you explicitly send. Nothing else.
- No browsing history. No page metrics. No background DOM reads.
- The extension source is auditable — every release is signed and pinned in the ContextIQ marketplace listing.