Ogma Browser
The built-in browser lets you browse a target through Ogma's proxy without any manual proxy configuration.
Opening a URL
- Click Browser in the left navigation or the browser icon in the top bar.
- Type a URL into the address bar and press Enter.
- Browse the target normally.
- Captured traffic appears in HTTP History as you navigate.
The proxy is pre-configured. You do not need to set a proxy address, install a profile, or adjust browser network settings.
Browser Modes
| Mode | When to use |
|---|---|
| Embedded | Keep the browser inside the Ogma window while you work alongside HTTP History or Replay |
| Separate window | Open the browser in its own window when you need more screen space |
The Browser view has a button to open a separate browser window. The embedded toolbar supports multiple tabs, an address bar, back/forward, and reload/stop. Use + to open a new tab and the tab's close button to close it.
What Gets Captured
The desktop browser is configured to use Ogma's proxy without manually installing a browser profile. Capture still depends on the active listener, scope/capture settings, TLS bypass rules, and WebSocket capture settings. A bypassed TLS connection does not expose decrypted HTTP content.
Built-in Browser vs. External Browser
| Built-in browser | External browser | |
|---|---|---|
| Setup | None | Configure proxy + install CA |
| Engine | Chromium supplied by Electron | The engine of your chosen browser |
| Extensions | None | Full extension support |
| Best for | Quick checks, initial enumeration | Complex JS apps, sites requiring specific extensions |
Use the built-in browser for fast access when you want to start capturing immediately. Use an external browser when the target requires extensions or a particular browser profile. The embedded Browser requires the desktop app; a browser-only Ogma UI cannot create Electron browser views.
Browser Automation
An MCP client can inspect snapshots, fill forms, click controls, wait for outcomes, and correlate browser actions with captured traffic. It can also manage isolated browser contexts and authentication state. These are MCP operations, not buttons in the Browser toolbar. See Browser automation with MCP for the sequence and permissions.
For multi-account testing, explicitly choose the tab or context and verify the logged-in identity before comparing access. A successful click alone does not prove authentication succeeded.