Browser Panel
The browser panel opens any page right next to your chat. Open it from the globe button in the app header.
On the desktop app it is a real browser: your logins persist, hot reload works, and developer tools are one click away. In a web browser tab the panel can still display a page, but it cannot look inside one — the annotation tools below are desktop-only. The VS Code extension has no browser panel at all: VS Code is already an editor with a browser beside it, and everything that makes this panel worth having needs the desktop app.
Pages opened here cannot use your camera, microphone, or location: those requests are refused.
The toolbar
The address bar remembers pages you have opened in this project and offers them as you type, matching part of an address or a page title. Arrow keys move through the list, Enter opens the highlighted entry, and the button on a row removes it.
Reload is next to it, along with a hard reload that ignores the cache when a change refuses to show up, and zoom controls that scale the page only.
Clear cookies and Clear cached data apply to this panel alone. Your OpenChamber session and any other window are untouched.
Annotate a page
Press Annotate and a toolbar appears over the page with three tools:
- Element — click an element. Clicking another moves the selection; clicking the same one again clears it.
- Region — drag a box around an area, when what you mean covers more than one element.
- Draw — sketch freehand over the page.
Write what you want in the box that appears beside your mark, and press Attach — or just press Enter. Your chat message gets a card with everything you marked, your note, and a screenshot of the visible page with your marks drawn on it — so you can say “this button, a bit rounder” instead of describing where it is.
The page itself is never modified — annotating marks what is there. Esc cancels and closes the toolbar.
Let the agent drive
The agent can use the browser panel itself — opening a page, reading what is on it, clicking, typing, scrolling, and switching between mobile, tablet and desktop layouts — so it can check its own work instead of asking you to. You will see it happening in the panel.
The agent cannot run arbitrary code in the page. The browser keeps your real logins, so it is limited to the specific actions above.
It can also save a picture of what it is looking at into .openchamber/screenshots/ in your project and show it to you in its reply. That is what makes a before-and-after possible, and the file stays there afterwards to attach to a pull request.
The browser actions are the OpenChamber Web tool, which can be turned on and off on its own in Settings → General → OpenChamber Tools.
This needs the desktop app: a page shown in a web browser tab cannot be driven.
Size and appearance
Press the phone button to open the device bar. Pick a preset or type a width and height, and the page is laid out at that size — scaled down to fit the panel when it is bigger, but still measuring itself at the size you asked for.
The same bar forces the page to light or dark, so a theme can be checked without changing anything on your machine. It leaves DevTools alone; a page can only have one debugger attached, so close DevTools first if it is open.
Developer tools
Press the terminal button in the toolbar to open Chromium’s own developer tools for the page — console, network, elements, everything you would expect.
Related
- Preview & Dev Servers — opening your running app, including on a remote machine
- Agent Control Tool — sessions, worktrees and scheduled tasks from chat