Browser tabs in the GoodQA desktop app

The desktop Browser window lets you browse in persistent profiles and lend a tab to the agent in your active one-click remote session. An agent can also open isolated hidden tabs. The Chrome extension remains available for your existing Chrome profile.

Choose Browser… in the app menu or tray. Use the address bar, tab strip, back/forward, reload and DevTools. The Default profile and named profiles keep cookies, local storage and logins on this computer across restarts. The profile manager shows size and last use, with clear/sign-out and delete controls. Profiles belong to the selected organization and account; they are never exported or uploaded.

Choose Lend to agent, select exact sites, and grant the capabilities needed for this session. The one-click session determines the organization, computer and agent. Persistent profiles require the separate signed-in permission. Hidden tabs otherwise use an isolated session partition. Sessions last at most 30 minutes and the app permits at most eight tabs. The tray lists active tabs and Stop controls. Stop agent immediately fences local input and ends the existing remote session.

Take back pauses agent input. Hand back checks the current site and permissions before restoring control. A hidden tab can be revealed without recreating its page. On platforms where hidden native surfaces cannot be captured, its offscreen frames are shown in the Browser window and local mouse/keyboard input reaches the same page. Passwords, two-factor codes and payments require user takeover; arbitrary JavaScript, cookie reads and raw CDP are unavailable.

Uploads, downloads, local networks, scoped file access, microphone, camera, recording and fake media each start off. File uploads use an authorized GoodQA attachment or a file picked by the person (256 KiB maximum). Folder access uses an opaque handle for a separately picked folder; list/read/create stay inside that folder, including symlinks. Existing files cannot be overwritten in this version. Downloads are bounded to 20 MiB and include size and SHA-256; executable and active file extensions require another permission. Actual microphone/camera requests require a further site prompt naming the agent. Test media uses a generated canvas and tone without touching devices. Recording currently produces a bounded sequence of timestamped PNG frames.

Screenshots (viewport, full page or element), page text and accessibility structure are available to the agent. Results are labeled untrusted page data. The command and control transitions are audited; navigation includes a PNG. Browser evidence can be attached using the existing GoodQA file workflow. Automatic download/recording upload to tickets and video recording are follow-ups, not available in this version.

Agents use the existing Machines REST endpoint, POST /v1/machines/{machineId}/commands, or MCP browser tools. Supply the chosen online machine, its control lease, and args.surface (desktop_visible or desktop_hidden). Entry tools can also select chrome_extension; the existing Chrome tool arguments remain supported. Examples:

{"kind":"browser_open","autoLease":true,"args":{"surface":"desktop_hidden","url":"https://example.com"}}

{"machineId":"<desktop-machine-id>","leaseId":"<control-lease-id>","args":{"surface":"desktop_visible","tabId":1,"selector":"button.submit"}}

Tools include browser_open, browser_list, browser_navigate, browser_click, browser_type, browser_keys, browser_scroll, browser_screenshot, browser_read, browser_close, browser_reveal, browser_console, browser_network, browser_evaluate (fixed page reads only), browser_upload, browser_downloads, browser_files, browser_fake_media, browser_record, and browser_profile_list/create/clear.

• API reference: /v1/openapi.json.
• MCP tools: Browser Control tool reference.
• Runbook: Browser Control.