Getting Started
Start with the local browser path. It is the most distinct ThinkRun workflow and does not require an account.
Use your real Chrome browser in local mode
Local mode connects the CLI and MCP server to your own Chromium browser through the ThinkRun extension and native host. It is the right path for logged-in sessions, extension debugging, and browser work that should run against the real desktop browser.
1. Install the browser extension
Add the ThinkRun Chrome extension first. The local workflow depends on the extension talking to the native host.
1. Install the ThinkRun extension from the Chrome Web Store 2. Open the extension side panel 3. Use Settings if you need the local-mode install/recovery guide
2. Install the native host
Start with the MCP doctor if you are setting up from the landing page. It tells you whether the extension, native host, bridge port, or cloud fallback is missing. Then install/register the native host explicitly.
npx @thinkrun/mcp doctor npx @thinkrun/mcp install-native-host npx @thinkrun/mcp doctor
The install command writes the ThinkRun native-host binary/config and browser native-messaging registration under your user profile. CLI users can also run npm install -g @thinkrun/cli and thinkrun setup. If the bridge is not reachable, go straight to Local Mode for install and recovery steps.
3. Attach to your browser
After Chrome, the extension, and the native host are running, list tabs and attach to the one you want to control.
thinkrun tabs thinkrun attach <tabId>
4. Drive the page
Once attached, the core browser commands work against the live desktop tab.
thinkrun navigate "https://example.com" thinkrun snapshot thinkrun click "button.submit" thinkrun screenshot --output page.png
5. When to use cloud instead
Use cloud sessions only when you specifically need a remote browser or the REST API. That path requires an API key and is covered in the Sessions and Browser Control references.