Skip to content

Glimmervoid v0.34.1

Choose a tag to compare

@johncwaters johncwaters released this 13 Oct 22:38
· 2821 commits to main since this release
ee91149

Added

  • Paste or drop screenshots into a session from any browser: pressing Ctrl+V or Cmd+V with an image on the clipboard, or dropping files onto a session's terminal, now uploads them to Glimmervoid and types the saved path into the session, the way the phone's Image and File keys already did. This works when the dashboard is opened on a different machine from the server, such as through a Coder port-forward URL, where the agent cannot read your local clipboard. A paste that carries text still pastes the text.
  • Add or remove repositories in a workspace: a workspace session's restart menu now has Edit repositories, which lists its current repositories alongside the ones found under your repo roots. Saving restarts the session in the same folder and resumes its conversation: a new repository gets its own worktree on the workspace branch, a removed one has its worktree deleted while its branch keeps any committed work, and the workspace AGENTS.md map is rewritten to match unless you edited it. Removing a repository with uncommitted changes is refused until you commit or discard them.

Changed

  • Update checks read the latest release from npm: a release-channel check now asks the npm registry for the published version on every install, including a git clone, instead of reading GitHub tags, so the version it offers is always one you can install. The main channel still compares a clone with its upstream branch.

Fixed

  • Check for updates shows that it is working: clicking Check for updates under Settings, Updates now disables the button and shows "Checking for updates." beside it until the result arrives, and says when the dashboard is not connected, instead of appearing to do nothing.
  • Guardrails only block what they list: an ordinary session still ran under the sandbox runtime's allow lists for everything but writes, so tools broke in ways sessions blamed on "the sandbox". File watchers failed with EMFILE (fs.watch, @parcel/watcher, Vite), node-pty failed with posix_spawnp failed, the macOS keychain looked empty (so coder login, git-credential-osxkeychain and other keychain logins failed), open and browser-based logins could not launch the browser, and Unix sockets were refused on Linux. Sessions with guardrails can now reach any macOS system service, any Unix socket and any terminal device, send Apple Events, and read and write the keychain. The credential folders and Glimmervoid's own state stay blocked for the session's own processes. The standard level guards against accidents rather than containing a hostile session, because an app it launches through Apple Events runs outside the guardrails. Lanes that read untrusted input (team review, PostHog fixes, the factory, benchmarks) keep their strict limits.