Files

T

Bohdan Triapitsyn a5aa32446d feat(browser): replace the preview proxy with a real browser panel and an agent web tool (#2883 )

The preview panel worked by proxying a dev server through OpenChamber's own
origin and rewriting the HTML that came back. Anything the rewriter did not
anticipate broke, and pages that refuse to be embedded never loaded at all.
This deletes the proxy (-1604 lines and its tests) and merges the preview and
browser panels into one surface backed by a real Chromium view.

What the panel is now

- A `<webview>` in its own session partition: logins and cookies persist, hot
  reload works because nothing is rewritten, DevTools are one click away.
- Annotation: pick one element, drag a region, or draw freehand, write a note,
  and it reaches chat with a screenshot of the visible page with the marks on it.
- Toolbar: hard reload, page zoom, device sizes, a light/dark switch that
  applies to the page rather than the app, and cookie/cache clearing scoped to
  the panel alone.
- Several pages at once, each tab showing the page's own favicon, and an address
  bar that suggests pages already visited in this project.
- Dev servers are listed from what is actually listening on the machine, checked
  against what a project announced, so a server is offered no matter how it was
  started. One that is still starting is waited for instead of failing.

Remote dev servers

The desktop app binds a local port and pipes raw bytes to the OpenChamber host
over the existing authenticated connection, so the page keeps its own origin at
the root of its own host. The reachable set is exactly what discovery reports
and is re-checked per connection, so an authenticated client cannot dial
arbitrary local services on the host. Links and redirects to another loopback
port stay on the machine that served the page. A tunnel that cannot be opened is
reported; it is never replaced by the plain loopback URL, which would answer
from the user's own machine under a remote address.

Agent control

Browser actions are a separate `openchamber_web` tool: open, snapshot, click,
type, scroll, inspect computed styles, resize between mobile/tablet/desktop, and
capture a screenshot into `.openchamber/screenshots/` in the project. The
existing `openchamber` tool keeps sessions, worktrees and scheduled tasks. Each
has its own setting in the new Settings -> General -> OpenChamber Tools section,
and the plugin is not injected at all when both are off.

Capability belongs to the connected client, not to configuration: a client
declares on its event stream that it can drive a page, which only a Chromium
host does. Exactly one client performs each request — it claims the request
before acting, and the first claim wins — because deciding by whose result
arrives first would be too late for a click that already happened. No client
listening is answered immediately with an explanation rather than a timeout.

Runtime boundaries

Web tabs get a plain iframe that can display a page but not inspect one. The
VS Code extension no longer offers the surface at all, since nothing that makes
the panel worth having works there. Mobile is unaffected.

Native boundary

Camera, microphone, location and device-picker requests from panel pages are
denied — Electron grants them by default when no handler is set, and the panel
loads whatever address the user types. Page capture, appearance emulation and
storage clearing verify that their target belongs to the panel's own session
instead of trusting a web-contents id from the renderer.

Persisted state

Stored `preview` tabs migrate to `browser` (v13 -> v14). Context panel tab
limits are now per surface, so filling one surface no longer evicts another's
tabs. Address history is stored per project and per runtime.

Documentation

`preview.mdx` and `desktop-browser.mdx` rewritten across all locales, the agent
tool settings path corrected, new `DOCUMENTATION.md` for the browser-control
broker and the dev tunnel, and the `ui-api-decoupling` skill updated where it
still described the deleted proxy.

2026-08-13 22:44:13 +03:00

2.6 KiB

Raw Permalink Blame History

Browser Assets And URL Authentication

Choose By Request Owner

Request shape	Correct path
UI can fetch a small authenticated asset	`runtimeFetch`, read `blob()`, render an object URL
Browser must own a URL (`iframe`, download/open link, large/raw image, rewritten subresource)	`getRuntimeUrlResolver().authenticatedAsset(...)`
SSE	`getRuntimeUrlResolver().sse(...)` and owning transport
WebSocket	`getRuntimeUrlResolver().websocket(...)` plus `openRuntimeWebSocket` where required

Do not prebuild a browser URL and then immediately call runtimeFetch with it. Ordinary HTTP callers pass route paths to runtimeFetch; browser/realtime consumers use resolver URLs.

Object URLs

Key caches by runtime identity, entity ID, update/version, and render options.
Bound caches by count and bytes when values can be large.
Revoke evicted object URLs with URL.revokeObjectURL.
Render a deterministic fallback while loading or after display-only failure.

URL Tokens

Browser-owned URLs cannot attach the normal Authorization header. Use short-lived scoped oc_url_token minted through runtime auth helpers.

Never manually append oc_url_token.
Never place a long-lived client bearer token in a URL.
Treat oc_client_token query use as legacy stripping/rejection only.
Add browser-readable GET or realtime paths to the narrow allowlist in packages/web/server/lib/ui-auth/ui-auth.js.
Add allowlist tests; never allow arbitrary /api/* URL-token access.

Showing Somebody Else's Page

OpenChamber does not rewrite third-party HTML to display it. Rewriting a page to serve it under our origin and a path prefix breaks every absolute URL on it, and recovering from that means encoding knowledge of each framework's dev-server internals — which ages badly and fails silently.

The in-app browser renders a real Chromium <webview> (packages/ui/src/components/browser/).
A dev server on a remote OpenChamber host is reached by binding a local port and tunnelling raw bytes (packages/web/server/lib/dev-tunnel/), so the page keeps its own origin at the root of its own host.
Runtimes without a Chromium host fall back to a plain iframe that can display a page but cannot inspect one. State that limit; do not emulate around it.
Do not use postMessage('*'); target a known origin.
Re-resolve browser URLs after runtime switches; do not retain URLs minted for an old runtime.

Security Tests

Prefer focused coverage in:

packages/ui/src/lib/runtime-url.test.ts
packages/ui/src/lib/runtime-auth.test.ts
packages/web/server/lib/ui-auth/ui-auth.test.js
packages/web/server/lib/dev-tunnel/tunnel.test.js

2.6 KiB Raw Permalink Blame History