Skip to content

Glimmervoid v0.52.0

Choose a tag to compare

@johncwaters johncwaters released this 04 Nov 03:58
· 1456 commits to main since this release

Added

  • Boxes on a board can hold a video or an HTML page, and SVG pictures. glimmervoid whiteboard attach <path> (or the whiteboard tool's attach action) now also takes SVG, MP4, WebM and HTML files, up to 200 MB, and returns the media to put on a box. The board draws a video's first frame under the box's lines and renders an HTML page live in place inside a sandbox that cannot read the dashboard; a video whose first frame cannot be read shows as a labelled placeholder. Pasting or dropping these files on an open board works too. An attach is refused, so you can attach it again, when the machine ran out of disk space or open files while making a photo's smaller copy or a video's first frame, ran out of memory while making a photo's copy or reading a picture or a video's first frame, could not start ffmpeg for lack of memory or processes, or stopped or timed out reading a video's first frame; a video ffmpeg cannot read, or that crashes it, is kept without a first frame.
  • Play a board video or use a board page right on the board. A video or page box stays still so dragging, panning and zooming work as usual. Press its play or use page mark, or double-click it, and the video plays in place with controls and sound, or the page takes your clicks and typing. Its done mark, a click anywhere outside it, picking another box or hiding the board puts it back, and so does Escape unless you are typing inside the page, which keeps your keys. Its full size mark opens it in the viewer.

Changed

  • Session worktrees start with dependencies on Linux. When a session starts in a worktree, new or resumed, every tracked package folder that has a package-lock.json or pnpm-lock.yaml but no node_modules gets its own install before the agent starts: npm ci --ignore-scripts or pnpm install --frozen-lockfile --ignore-scripts. Tools like Coherence work from the first prompt, and the main checkout's node_modules is never touched. No package scripts run, so native modules such as node-pty stay unbuilt until you or the agent run npm rebuild. An install takes a few seconds with a warm npm cache. Sessions starting together install one at a time. A registry that stops answering fails the install after 30 seconds, with one retry. If an install fails or runs past 10 minutes, its partial node_modules is removed, the dashboard header shows a worktree warning naming the command and its last output line, and the agent starts anyway. A folder with only a yarn.lock or bun.lock is not installed, and the warning says so. On macOS, a folder the copy-on-write clone skips, such as one whose install no longer matches its lockfile, now gets this install instead, and the header no longer shows a warning about the skipped clone. Closing a session while it is still starting stops its install and removes the partial node_modules, so other sessions waiting to start are not held up. Windows worktrees still start without node_modules. worktreeCloneDependencies: false in config.json turns off both this install and the macOS clone. Settings now lists it as Worktree dependencies, describing both.

  • Codex sessions with skip permissions on now run without Codex's own sandbox, like Claude sessions, so they can write outside their worktree (for example to ~/.claude/specs). Sane YOLO, when on, still blocks risky commands and secret reads. Codex sessions with skip permissions off are unchanged.

  • A file attached to a board is now kept exactly as given and is the stored copy itself, served from /whiteboards/assets/<id><ext> with its own type, so you can download it or use it elsewhere; only a photo larger than 1024 pixels also gets a smaller copy for drawing. Boards saved by 0.51.0 load with their pictures, which open at the size the board drew them; the full size copies 0.51.0 kept beside its pictures are left on disk unused.

  • Your pull requests in Reviews now list review comments as one deduplicated list: threads from different reviewers or bots on the same file within three lines of each other show as one item naming every reviewer, each with a priority tag.

  • Each review item on your pull request now has Fix locally, which sends the comment to the live session linked to that pull request, and Dismiss, which posts your typed reason as a reply under your GitHub login and resolves the thread. Handled items move to a Handled list on the pull request, and a dismissed comment stays hidden after new pushes unless its text changes.

  • Rules in prFlows.rules and prFlows.repoRules in config.json now handle review items on your pull requests with no click: the first rule matching an item's source, priority, paths or text dismisses it with the rule's reason or pastes it into the linked session, unsubmitted so you read it before pressing Enter, on the next poll. Each one lands in the Handled list naming its rule, where Undo reopens the item (and its thread on GitHub) and keeps rules off it. The Dismiss form's Save as rule adds a rule for that reviewer and file, and a rule config.json cannot use shows as a warning on the pull request.

  • On a teammate's pull request ready to post, Reviews now lists the unresolved threads other reviewers and bots left, read-only under Other reviewers, and your own finding within three lines of one shows already flagged by that reviewer and starts unticked, so it stays out of your review unless you tick it.

  • prFlows.sources in config.json runs your own commands that report review findings for your pull requests, such as a script that reads a review bot's results. A command runs only after you approve its exact argument list in My PRs, and again after any edit. It then runs without a shell on each new head of each open pull request of yours, with {prUrl}, {repo}, {number} and {head} filled in and Glimmervoid's own secrets removed from its environment. Its findings join the review items under its label with their priority, and its status lines, or its error, show on the pull request. With no sources configured, nothing runs.

  • prFlows.actions in config.json adds your own commands as buttons, under their own labels, on each review item of your pull requests, and a rule can run one with run:<id>. Like a source, an action runs only after you approve its exact argument list, without a shell, with {itemPath} and {itemLine} also filled in and the item as JSON in GLIMMERVOID_ITEM_JSON. It runs at once, one run per action per pull request at a time; the item shows done when it exits 0 (or the outcome its JSON output reports) and failed with its error output otherwise. When the pull request's branch moves while an action runs, the linked live session is told to pull before its next push.

  • glimmervoid pr-flows check checks your PR flows setup: it names each entry of prFlows.sources and prFlows.actions valid or its error and whether it is approved, lists rule problems, runs each approved source once against --pr <url> and prints its findings (a source still waiting for your approval in My PRs never runs), and prints each action's expanded command without running it. glimmervoid settings describe <path> (and the agent settings tool) now shows the JSON Schema and an example for the PR flows settings, so an agent can write them for you.

  • Small icon buttons on desktop, like the session menu, Changes and Shown, are now 28 pixels square instead of 22, with a larger icon, and every whiteboard toolbar button is now that same size. The phone layout is unchanged.

  • Trace's Expand all and Collapse all buttons now match the height of the filter buttons beside them.

Fixed

  • Codex no longer shows your sent prompts on a bright lavender bar. Glimmervoid now answers Codex's terminal color check itself, even when no dashboard is open, using the colors of the theme your dashboard shows, so Codex draws the bar as a light tint of that theme's terminal background, in light themes too. A session started before any dashboard has connected since the server started uses the Phyrexian colors.
  • A Claude Code session now resumes its conversation after a restart even when Glimmervoid had to give it a new worktree folder. Before, the session started a blank conversation whenever its old worktree folder was gone or held another branch.
  • A command that ignores being stopped no longer outlives its timeout. When a git, gh, npm or other command Glimmervoid runs passes its time limit, it is asked to stop as before, and is now force-stopped 2 seconds later if it is still running. Before, a command that ignored the stop request, such as npm waiting on a registry that never answers, kept everything waiting on it blocked until it gave up on its own. A cancelled command is now also finished by the time Glimmervoid moves on, so it cannot keep writing files after its work was cleaned up.
  • Arrows on a board no longer cross when they do not have to. When several arrows leave one box, such as a decision's outputs fanning out to a column of boxes, an arrow drawn early no longer takes the far lane and forces the others across it; only crossings the arrows' order truly forces remain.