@Atlas audits the catalog the day the store is connected and ships a CRO plan, instead of handing back a list of things to go read. Audit to plan, same session.
BoostEcom DemoDemo
Founder
AI copilot.
@Atlas is the BoostEcom AI copilot. A chat-based agent that sits next to every Shopify operator surface. It reads your store state, accepts voice and screenshots, and asks before it mutates anything.@AtlasApprovalsVoice + visionCompose workflows
The numbers
The chat surface
- Autonomy levels
- 1–3
- Specialists on call
- 6
- Ways to ask: text, voice, image
- 3
- Changes made without your approval
- 0
What it is
@Atlas is the orchestrator agent that coordinates BoostEcom's domain specialists (Maya, Marco, Otis, Faye, Sam) and your installed skills. It is reachable from the workspace chat, the workflow canvas and the theme editor, with the same memory across surfaces.
Voice and vision are modes of one composer, not separate products. Workflows are composed, saved and edited in the chat; running them on a schedule is on the roadmap. WhatsApp shares the same memory once the channel is connected.
One composer, several inputs
- Cards and approvalsMutations surface as cards. Default autonomy keeps a human in the loop.
- VoiceSpeak to the same orchestrator, with natural turn-taking. Billed on the same ledger as text.
- VisionScreenshots and admin URLs as attachments, not a separate product.
- WorkflowsEight templates and a real canvas. Compose and save multi-step work without leaving the chat.
How it works
Five stages, from context read to answer streamed.
- Context readReads store context via the Shopify Admin GraphQL API and the BoostEcom MCP server.
- Three inputsTakes text, voice with natural turn-taking, and pasted screenshots or admin URLs.
- Scoped toolsCalls scoped tools: never raw shell. And returns structured tool-call output.
- Approval by defaultAsks before mutating. Approval is the default; full autonomy is opt-in per store.
- StreamingStreams responses via the Vercel AI SDK and the AI Gateway for model routing.
What people open chat for
- Daily opsScoped Admin reads and writes with an approval trail.
- Theme changesLiquid edits through the theme skill, preview-first.
- Store researchPull Intelligence and Systems context into the same thread.
When to use it
- Use it whenReach for @Atlas when you would otherwise open ten Shopify admin tabs. Running a catalog audit, drafting a BFCM playbook, debugging a checkout regression, or preparing a brand refresh across collections.
- Do not use it whenFor a long storefront crawl, which belongs to the Tracking module, or for an operation you cannot review before it goes out: @Atlas asks before it mutates, but you are the one approving.
What @Atlas will not skip
- Shopify scopes are the ceilingA read-only token stays read-only. We do not invent write access.
- Autonomy stops at 3Level 4 is roadmap language elsewhere. It is not a setting on this product.
- Run is honestComposing and saving workflows is live. Scheduled execution is on the roadmap, and is not sold as shipped.
What it covers, what it doesn't
What this covers, and what it leaves to something else. Knowing beforehand costs less than finding out after.
- It works inside the exact rights of the Shopify token you connect. Connect read-only and you get a read-only @Atlas: there is no way to escalate from the chat.
- It asks before it changes anything. Full autonomy exists, it is opt-in, store by store, and you pick the level.
- Long storefront crawls go to the Systems, which are built for them. @Atlas hands you the result instead of running the crawl in the conversation.
- Image generation is billed on image credits, counted separately from text. You see the cost before you send.
- Workflows are composed, saved and edited in the chat today. Running them on a schedule is on the roadmap below.
Waiting on a decision
- Scheduled workflow execution.
The neighbouring features
Same family, same product surface.
Who exactly is @Atlas?AI copilot
The orchestrator agent. It coordinates the five specialists (Maya on marketing, Marco on merchandising, Otis on operations, Faye on intelligence, Sam on support) and the installed skills, the way a CEO distributes the work.
Can it change my store without asking?AI copilot
Not by default. Approval is the baseline behaviour and full autonomy is opt-in, store by store. You pick the level, not us.
What can it read and write?AI copilot
Exactly what the Shopify token you connected allows. A read-only token gives you a read-only @Atlas: there is no privilege escalation available from the chat.
Can I talk to it?AI copilot
Yes. Text, voice with natural turn-taking, and pasted screenshots or admin URLs. All three reach the same agent, with the same memory.
How is it billed?AI copilot
Against your plan's credits, at the real model cost with your tier's markup. Image generation goes through the AI Gateway and counts against image credits, separate from text.
One operator, the full stack: Maya runs the email calendar, Marco curates collections, Otis watches fulfilment. One team, one thread.
BoostEcom DemoDemo
Head of Growth
The work gets done rather than suggested. Voice mode with @Atlas turns the morning check-in into a conversation. It operates.
BoostEcom DemoDemo
Store owner
@Maya rewrites product descriptions, queues them for review, pushes the approved batch live, then runs the campaign around them. End-to-end, with approval gates.
BoostEcom DemoDemo
E-commerce lead
Every action the AI Team takes is graded against real Shopify Analytics after the observation window closes. Outcome attribution, not vibes.
BoostEcom DemoDemo
Marketing lead
OAuth scopes, audit log, store-scoped credits, no shadow data. The agents work inside the admin, not around it.
BoostEcom DemoDemo
Engineer
Permission mode decides what ships on its own and what waits for a human. Autonomy you dial in.
BoostEcom DemoDemo
Operator
Multi-store from one console, each with its own connectors, memory and budget. Per-store context.
BoostEcom DemoDemo
Agency owner
@Atlas audits the catalog the day the store is connected and ships a CRO plan, instead of handing back a list of things to go read. Audit to plan, same session.
BoostEcom DemoDemo
Founder
One operator, the full stack: Maya runs the email calendar, Marco curates collections, Otis watches fulfilment. One team, one thread.
BoostEcom DemoDemo
Head of Growth
The work gets done rather than suggested. Voice mode with @Atlas turns the morning check-in into a conversation. It operates.
BoostEcom DemoDemo
Store owner
@Maya rewrites product descriptions, queues them for review, pushes the approved batch live, then runs the campaign around them. End-to-end, with approval gates.
BoostEcom DemoDemo
E-commerce lead
Every action the AI Team takes is graded against real Shopify Analytics after the observation window closes. Outcome attribution, not vibes.
BoostEcom DemoDemo
Marketing lead
OAuth scopes, audit log, store-scoped credits, no shadow data. The agents work inside the admin, not around it.
BoostEcom DemoDemo
Engineer
Permission mode decides what ships on its own and what waits for a human. Autonomy you dial in.
BoostEcom DemoDemo
Operator
Multi-store from one console, each with its own connectors, memory and budget. Per-store context.
BoostEcom DemoDemo
Agency owner
A question that is not here?
Ask it, and it joins this page if it comes back.