* Codex worktree snapshot: startup-cleanup Co-authored-by: Codex * fix(browser): close malformed proxy connections without a reply * feat(browser): embed host browsing in terminal side panels * style(browser): blend compact browser chrome into terminal panels * feat(browser): open terminal links internally with a system browser preference * fix(browser): retain the first terminal link during panel mount replay * fix(browser): release contexts when their split pane closes * style(browser): remove the downloads panel shadow * fix(browser): ignore late downloads after panel closure * fix(browser): mount browser content on terminal auto-open * fix(browser): preserve empty-vault recovery with bookmarks * fix(browser): expose actions for supported terminal types * fix(browser): retain open requests before the panel mounts * fix(browser): align vault actions with supported hosts * fix(browser): share download controls across host contexts * fix(browser): keep vault browser requests on visible sessions * fix(browser): release contexts after workspace detach * fix(browser): enforce WebRTC routing on page contents * fix(browser): skip unsupported sessions in open requests * style(browser): encode glyphs in ASCII-safe source
6.9 KiB
WaveTerm embedded browser and remote localhost
Checked 2026-09-29. Scope: WaveTerm's own website/docs, GitHub discussions/issues, and the 2026-09-25 source commit c58bf7f346d0a638f3e5d7c77b2688122d36fede. No runtime verification.
Confirmed user workflow
- Wave has an inline web browser for sites, dashboards, and apps. Its website says web views can be arranged alongside terminals and editors. The docs say the right-side widget bar adds a web widget to the current tab; widgets can be moved, resized, and magnified. Website · Widgets
- A user can enter a URL in the web widget, or run
wsh web open <url>from a Wave terminal.wsh web opencreates a web block;-mmagnifies it and-r <blockid>replaces an existing block. The docs' local development example starts a server and then openshttp://localhost:3000in a web block. wsh overview · wsh reference - Web navigation has a URL field, back/forward, reload, in-page find, and bookmarks; the documented shortcuts include
Alt+L,Alt+Left/Right,Alt+R,Alt+F, andAlt+O. A home page can be set globally or per widget.web:openlinksinternally=falsesends web links to an external browser. Key bindings · Custom widgets · Configuration
Remote 127.0.0.1: not established as automatic
- Confirmed: Wave's SSH connection picker opens a remote terminal. With
wshinstalled, the remote can also back file-preview and system-info widgets, and a remote shell can control Wave widgets. The Connections page does not list the web widget as a connection-backed widget. The wsh overview putswsh web open http://localhost:3000under Development Workflow and lists SSH under a separate Remote Development example; it does not say the first command retargets localhost to an SSH host. - Best reading, still an inference: entering
http://127.0.0.1:<port>in Wave's web widget addresses the machine running the desktop app unless the user has separately made the remote port reachable. Do not describe SSH remote loopback as auto-forwarded from these docs. A May 2026 feature request explicitly asks for a port-forwarding widget to avoid typingssh -L 3000:localhost:3000 user@server; it was still open with no linked closing PR when checked on 2026-09-29. That request supports the gap but is not, by itself, proof of current behavior. - Candidate manual workflow, inferred from that request: create a local SSH tunnel such as
ssh -L 3000:localhost:3000 user@server, then openhttp://127.0.0.1:3000in Wave's web block. This requires a working tunnel and an available local port; the reviewed docs do not present it as an integrated Wave flow. Port-forwarding request · wsh web command - Different forwarding path: the Connections troubleshooting guide says SSH server TCP forwarding settings can affect
wsh; a GitHub discussion reportswshfailing where stream-local forwarding is denied. Neither source establishes automatic forwarding of arbitrary HTTP ports to the browser.
Source-code check at the pinned commit
wsh web opencreates a web block containing the supplied URL. It does not resolve the current SSH host or request a forward in this command path.- The web block uses Electron's
<webview>to load its URL; its navigation path normalizes the scheme and passes the resulting URL directly to the webview. Inference from these paths:localhostresolves on the computer running Wave, even whenwsh web openis invoked in an SSH terminal. This is not a live acceptance test. - The web block implements address, back/forward, reload, external-open and load-error feedback. Popups are intercepted by the host tab and converted into Wave's link-opening flow.
- Wave uses an Electron
<webview>tag. Electron's current guidance advises considering alternatives such asWebContentsView; Netcatty should copy the workspace interaction, not assume the exact embedding mechanism is the best current choice.
Security and limits of the evidence
- The website says Wave stores user data locally and needs no account; that is a general product statement, not a browser-specific guarantee about cookies, site isolation, permissions, or proxying. The browser docs found here do not specify those protections or a remote-URL trust policy. Website · Configuration
- Web links can be opened externally, but an older GitHub report said the external-browser button picked Chrome instead of the system default on Ubuntu; it is version-specific and should not be generalized. A v0.14.5 macOS report describes unresponsiveness when switching between two web blocks; it is a report, not a confirmed universal limitation.
Practical conclusion: the documented product is a browser block beside terminal blocks. The reviewed first-party material does not confirm automatic SSH forwarding for a service bound to remote 127.0.0.1; treat that behavior as unverified until tested in the app or confirmed by a direct WaveTerm statement.
For Netcatty issue #2972, the reusable product idea is a resizable web pane beside the terminal, with address, navigation, expand, and clear load errors. The distinct requirement is automatically connecting that pane to the selected SSH host's private web service, showing which host 127.0.0.1 refers to, and releasing the temporary access path when the pane closes. These are design recommendations, not claims about Wave's behavior.