Docs & Support
Get up and running
Install, connect and automate — everything you need to start, plus answers to the questions we hear most.
Quickstart
Install
Add Operun from the Chrome Web Store. The MV3 build asks for nothing but the minimum permissions it needs to act on pages you choose.
Connect
Open the popup, paste your runner token, and connect. The edge hands are ready — the cloud brain takes it from here.
Automate
Describe the workflow. Operun navigates, clicks, types and captures, settling each step through the in-flight escrow as it goes.
# list the tabs you can drive
$ operun browser list-tabs
# navigate a tab
$ operun browser goto --tab 0 --url https://example.com
# run an action and settle credits atomically
$ operun browser act --action snapshot
Frequently asked questions
Does Operun use the debugger permission?
No. The store build of Operun never requests chrome.debugger, so there is no yellow "debugging this browser" bar and no whole-web install warning. A separate operator build — for people automating their own browser — adds debugger for network capture, and it is distributed outside the store.
Where does my data live?
Locally. Credentials, cookies and session tokens are processed in memory on your device only and are never written to disk or uploaded to the cloud. The cloud control plane only receives the minimum commands and results needed to orchestrate your workflow.
Does Operun use eval or load remote code?
No. The extension never uses eval() or new Function(), and it never loads scripts from a URL. All logic is compiled into the local package.
Does the extension include analytics or trackers?
No. The extension contains no third-party analytics SDKs, no advertising libraries and no tracking probes of any kind.
What are credits and how does billing work?
Each automated step consumes one credit, settled atomically through an in-flight escrow as the task completes. Your plan provides a monthly credit allowance; the popup shows your remaining balance in real time.
Which permissions does the extension request, and why?
The store build requests only storage, activeTab, scripting, downloads, alarms and tabs — the minimum needed to perform automation on pages you choose. Host access is limited to the Operun API, local loopback, and a fixed allow-list of seven business domains. There is no <all_urls> access.
taobao.com— Taobao merchant analytics and reporting.tmall.com— Tmall merchant analytics and reporting.jinritemai.com— Douyin E-commerce merchant reconciliation.oceanengine.com— Ocean Engine / Qianchuan advertising financial flow.xiaohongshu.com— Xiaohongshu creator backend data management.zhipin.com— BOSS Zhipin recruitment and candidate pipeline reach.bing.com— Search engine benchmarking and connectivity validation.
What is the operator build?
The operator build is a separate artifact for developers and power users driving their own browser. It adds the debugger permission to enable an in-memory, operator-initiated network capture of a single tab. It is not the store build and is distributed separately.
Is Operun compliant with store policies?
Yes. The store build follows Google's Limited Use policy and the Microsoft Edge Add-ons store privacy requirements, and is designed around Manifest V3 and the principle of minimum reach.
Still stuck?
Our team is here to help with setup, billing and anything in between.
support@operun.app