Repository navigation
Testing Browser
Joro can launch a browser that is already pointed at the proxy with Joro's CA trusted. There is nothing to configure and nothing to install into your operating system's trust store.
Three ways to start it:
- The window icon in the top-right of the app header. Launches immediately using the saved landing URL.
- Settings → Testing Browser → Launch.
- The Connection Check wizard, which walks you through proxy, browser, and first capture. Reachable from the first-run setup flow and from the CA card in Settings → Testing Browser.
Chromium-family only. Joro looks for Chrome, Chromium, Edge, and Brave, in that order, and uses the first one it finds. Detection works on Linux, macOS, and Windows.
The Settings card shows what was detected. If nothing supported is installed, the launch button disables itself and says so — use the manual path in Getting-Started instead.
Firefox and Safari are not launchable this way. They still work fine as testing browsers; they just need the manual proxy and CA setup.
Joro starts the browser with the proxy already set, including for loopback targets, and pins its CA by public-key hash for that session only. Your system trust store is never touched, and no other browser or application is affected.
Traffic flows through the proxy exactly as it would from a manually configured browser, so scope, the noise filter, Match & Replace, Custom Data, Intercept, and any upstream SOCKS proxy all apply unchanged. Requests land in History and feed Detect the same way.
Each project gets its own browser profile under ~/.joro/browser-profiles/, keyed on the active project name. Cookies, storage, and sign-ins never cross between engagements — switch project in the header, launch the browser, and you get a clean, separate session.
With no project loaded, the browser uses a scratch profile that is wiped when the browser exits. If you want the session to persist, create a project first. See Projects.
Clear Cookies in Settings removes cookies from the active project's profile only, leaving history and other site data alone. The browser must be closed for this to take effect — Chromium holds the cookie database open and rewrites it on exit, so clearing while it runs is silently undone.
Deleting a project takes its profile with it, with the same caveat: close the browser first, or the profile is left in place. See Projects.
Settings → Testing Browser holds:
- Landing URL: where the browser opens. Leave it blank for a blank page.
- Clear Cookies: as above.
- Setup Check: opens the Connection Check wizard.
- Download CA: the same CA certificate download offered elsewhere, for when you need to trust it in something other than the managed browser.
- Getting-Started — first-run flow, and the manual setup for other browsers and clients
- Projects — profiles are keyed on the active project
- Settings — scope, noise filter, and the rest of the traffic controls that apply to this browser