OpenWork Browser extension.
Requirements
- Use the OpenWork desktop app.
- Keep
OpenWork Browserenabled inSettings > Library.
How control works
A session can use the browser without asking: it can navigate allowed websites, read pages, scroll, click, type and run website tools (WebMCP) in its own tabs. Organization restrictions still apply. Keyboard automation requires a directly focused native field, button, or link; embedded and custom editors with unverifiable focus require you to take over. Choose Take over at any time to pause browser operations. Sign in directly in the page, then choose Resume browser to hand control back. Browser control does not reach your regular Chrome profile or other conversations’ tabs. Tabs opened or restored for browser work stay protected untilbrowser.release_tab declares all running and queued work complete. Release does not suspend or invalidate the current target; there is no automatic reclamation. For later work, browser.restore_tab checks conversation ownership and returns a fresh protected handle to use.
Keyboard shortcuts
In the desktop app, these shortcuts apply when a built-in browser page, its URL field, or its browser controls have focus:
The native app menu’s Close command also closes the focused browser tab before closing the window.
Reopening creates a fresh page from a URL kept only in memory, not a saved page snapshot. It does not restore form input, scroll position, or page history, and closed-tab URLs do not survive an app restart.
After closing the last browser tab, press the reopen shortcut immediately. Clicking elsewhere, pressing
Tab, or changing conversations clears that immediate browser context. With the chat composer focused, Cmd+T / Ctrl+T still cycles conversations instead of reopening a browser tab.