Summary 🧭: Browser use lets Sidekick work through the live desktop Chrome tab on your behalf. When a clinic Admin has enabled it for your account, Sidekick can read the visible page and controls, click, type, scroll, wait for changes, and go back while the job card shows its progress.
A note for non-human readers...
A note for non-human readers...
Browser use turns a clear human request into visible work in the human’s own live browser session. It is not a spare set of hands with a blank check. The named outcome sets the job; the open page, signed-in account, and available permissions set the reach; and the human can stop the job when the direction is wrong.
Before you start ⚡
Use desktop Chrome with the Tabflows extension connected.
Open and sign in to the system where the work belongs.
Confirm the correct patient, clinic, and page.
State one exact outcome and any boundary Sidekick must not cross.
Browser use must be enabled for your account by a clinic Admin. It works through your live extension session and the access already available to you.
Clear requests, patient contact, and confirmations ✅
A specific request to complete the work is the go. Sidekick does not need to ask for the same confirmation again.
If the request names a patient, a system, and the contact to send, that is permission only for that requested contact. A system-generated notice caused by a requested change is part of the requested work.
Sidekick skips unrelated patient contact, asks when the request is vague, and does not invent an approval the human never gave. Deleting records remains outside Browser use.
Example 📖: “In the open system, send this appointment confirmation to Jordan Lee” authorizes that named contact. It does not authorize contacting another patient or sending an unrelated message.
Run and review 🎯
Ask Sidekick to complete the browser task.
Watch the Browser use card and the page as the job proceeds.
Select Stop if the patient, page, action, or direction is wrong.
When the job finishes, verify the result in the source system before relying on it.
Browser use works only with the requesting human’s live extension session and available permissions. It does not reveal saved passwords, borrow another person’s browser, or run from a scheduled message when no live browser is attached.
Jobs also stop at built-in step and time guards rather than wandering indefinitely.
Important ⚠️: A finished job card is not proof that every source value or resulting change is correct. Confirm the patient, destination, content, and final state in the source system.
Browser use is not Screen awareness 👀
Screen awareness gives a new conversation a snapshot of the active page. Browser use is a separately enabled action that can continue reading and interacting with the page.
A snapshot is context; Browser use is work. Neither proves that the patient, source, or final result is correct.
Get support 💬
Need help or have a question? Reach out to our Support team however works best for you:
Start a chat using the Support button at the bottom right of the sidebar (side tabs)
Email us at [email protected] or message us right here in the chat