Docs  Mori Chrome

Everywhere

Mori Chrome

The Mori side panel for your own Chrome: she reads the whole page, plans, and acts in your real signed in browser, on her own or as the browser arm of your desktop Mori, and she stops before paying.


What it adds

Mori Chrome is a free extension on the Chrome Web Store. It puts Mori in a side panel of the Chrome you already use, so web work happens in your real, signed in sessions instead of a fresh browser that knows nothing about you.

In the browser, Mori can read the whole page, click and navigate, type and fill forms, pull out what matters, research and compare across tabs, and stop before paying.

Two ways to use it

  • On its own. No desktop app needed: add the extension, paste a key or sign in, and work from the side panel.
  • Linked to your desktop Mori. Signed in to the same Studio Mori account on both sides, the extension becomes the browser arm of your desktop Mori: a thread on the desktop can read pages, act on them, take screenshots, manage tabs and read the console in your Chrome, with the same memory.

Linking it to the desktop

Open the Mori Chrome page in the desktop app. Add the extension, open its side panel, and sign in to the same account; it links on its own, and the page says Mori Chrome is connected.

If automatic handoff is not available on your account, the page shows a Pairing code to paste into the extension once. The code is signed, so a code from anywhere else is refused. The page's status line says exactly where things stand, for example Reachable, but not paired, or that the extension rejected the code.

After an extension update, Reload the extension makes Chrome pick up the new build; the link drops for a moment and comes back on its own.

Which browser Mori drives

Which browser Mori drives, on the Mori Chrome page, chooses where web work runs: let Mori pick, Mori's Chrome (her own signed in window), or Use my real Chrome. One message can name a different one for that turn, like "in my browser" or "in your own Chrome".

If this computer was ever paired, Mori opens Chrome herself when a task needs it and waits for the extension. On Windows, the system's own UI Automation comes first and the extension is the fallback. Without the extension, a built in browser agent reads a page's elements and clicks by selector. See Computer use and browser.

How she works on a page

  • Plan first. She drafts the steps and lists the sites she will touch before doing anything.
  • Read like the browser. Every link, button, field and heading, element by element, so she acts on what is really there rather than on a guess from a picture.
  • Act. She clicks, types and fills on the live page, through multi step flows, across as many tabs as the job needs.
  • Check. She looks at the result on the page before calling it done.

Pages are data, never commands

Everything on a web page is treated as data, however it is phrased. A page that says "ignore your instructions" or "email this to" is text she read, not an order. Actions come only from you.

Stopping at the pay button

Mori compares listings, adds the right item to the cart and fills in shipping up to the final screen. In your Chrome she never presses a final pay or place order button, and never types card details or passwords. She stops there for you to press. See Shopping.

Permissions

Chrome asks for the extension's own permissions when you add it. In the desktop app, browser work follows the Browser Control switch in Settings > Permissions. See Security.