Skip to main content
Some work only exists behind a login and a few clicks — a dashboard with no API, a portal that only exports from a button, a flow you’d normally do by hand. Browser Use gives Notis a real, controllable web browser so it can do that work for you: open the page, sign in, navigate, fill the form, grab the data. It’s powered by a single skill — Notis Browser Control. Once installed, the same skill drives a browser whether Notis is running on the Cloud Computer or on your own machine through the Local Shell — you don’t pick a different tool for each, Notis just uses whichever environment the task is in.

​
What you can ask for

  • “Log in to my analytics dashboard and export this month’s report.”
  • “Go to this supplier portal and pull the latest order status for each SKU.”
  • “Fill out this multi-step application form with the details I gave you.”
  • “Check whether my listing is still live and screenshot the page.”

​
Install the Notis Browser Control skill

Browser Use ships as a skill, so adding it is the same one-click flow as any other skill: From the catalog
  1. Open your Notis portal
  2. Go to Skills
  3. Find Notis Browser Control in the curated catalog and click Install
From a chat
“Install the Notis Browser Control skill.”
Notis confirms and it’s available everywhere immediately. See Skills for the full install flow.

​
Cloud or your own desktop — same skill

The skill is environment-agnostic:
  • On the Cloud Computer, Notis drives a private browser in its own cloud workspace — nothing touches your machine. This is the default.
  • On your own desktop, through the Local Shell, Notis drives a browser on your computer when the task genuinely needs your local network, files, or sessions.
You don’t choose between them. Notis stays in the cloud whenever it can and only reaches for your machine when the task requires it.

​
The main limitation: it can’t use your everyday browser

For your security, Notis can’t take over the browser you use day-to-day — the one already logged in to your bank, email, and everything else. It always drives a separate, clean browser instead. That keeps Notis isolated from your personal sessions, but it also means it starts logged out of every site. Two ways to give it the access it needs without handing over your main browser:

​
Save a profile

Let Notis sign in once and save the browser profile. The next time it opens that site, the session is already there — no re-login. Profiles persist between runs, so a portal you logged into last week is still ready this week.

​
Connect 1Password

For credentials, connect 1Password in your integrations. Notis pulls the right login from your vault at the moment it’s needed, so you never paste a password into a chat. 1Password connects through a service account — a scoped, revocable token that gives Notis access to only the items you allow, never your full vault. Follow 1Password’s guide to create one: Get started with 1Password Service Accounts.

​
When Notis uses it

Only when a task needs a browser and no API or integration will do. If the work can be done through a connected app, Notis takes that path first — it’s faster and more reliable. Browser Use is for the sites that can only be reached by actually visiting them.
  • Cloud Computer — the cloud workspace where the browser runs by default.
  • Local Shell — run the same skill against a browser on your own machine.
  • Skills — how to install and manage skills.
  • Integrations — connect 1Password and other accounts Notis can use.