Skip to content

v0.5.10 — first installable release

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 Aug 02:41
v0.5.10
62684f9

First installable release. Everything since v0.0.2 (July) — main was 30 versions behind and has been brought current.

Install

Download cobrowser-0.5.10.vsix below, then:

cursor --install-extension cobrowser-0.5.10.vsix   # Cursor
code   --install-extension cobrowser-0.5.10.vsix   # VS Code

Reload the window, then run Cobrowser: Open Browser Panel. No Chrome setup needed — a dedicated Chrome-for-Testing downloads on first run.

Highlights since v0.0.2

  • Chrome-for-Testing on first run — pinned by buildId, installed into globalStorage, independent of your daily Chrome. Falls back to system Chrome.
  • Multi-tab — one window per tab, each panel streaming at full 60fps, with instant tab restore across editor reloads.
  • Browser survives reload — reconnects to the kept-alive Chrome over its DevTools endpoint, tabs intact, instead of relaunching.
  • Sharper, faster panels — binary frame transport, per-monitor density tracking, real drag-to-select, and an opt-in uncapped frame rate (cobrowser.uncapFrameRate).
  • Per-workspace profile isolation, passkey fail-fast, and hung-tab resilience.
  • Less bot-flagged — the headless UA token no longer leaks from pages that skip page prep, and headless reports an ordinary desktop screen size.

Packaging fix

.cursor/mcp.json and .mcp.json are generated at activation and carry a live localhost MCP port and Bearer token. They are git-excluded, but vsce does not read .gitignore, so they were being swept into the package. This release excludes them and no published release has ever shipped one — but a VSIX you built locally from an earlier checkout may contain a token, so rebuild rather than share those.

Experimental — opt-in, off by default

cobrowser.backend: "container" (Docker-backed browser) and cobrowser.videoPipeline (hardware H.264) are still settling. The container path's native-sizing fix is verified in isolation but not yet confirmed in a live editor panel. The default local backend is unaffected.

Known limits

macOS only for now; Windows/Linux launch paths aren't done. Not yet on Open VSX or the VS Code Marketplace.

Assets 3
Loading