Skip to content

Glimmervoid v0.29.0

Choose a tag to compare

@johncwaters johncwaters released this 04 Oct 20:23
· 3054 commits to main since this release

Added

  • Workflows: write rules under workflows.rules in config.json that act on pull request events in the repositories you name. Each rule has one trigger (opened, checks-failed, review-requested, approved, commented or merged), optional filters (mine for your own pull requests, teamReviewRequested for a review requested from your Team review team, authors, labels and baseBranches), and one or more actions: notify sends you a notification, label adds a label, comment posts a comment, and spawn starts a sandboxed agent session on a local copy of the pull request from your prompt template ({{repo}}, {{number}}, {{title}}, {{url}}, {{author}}, {{base}}, {{head}}, {{trigger}}) with the same limits as Keep mergeable, except that nothing it does is pushed. A spawn action never runs on a pull request from a fork unless its rule also filters on authors or mine, at most 2 sessions run at once and up to 20 more wait for a free one; editing rules leaves running and waiting sessions alone. Rules start disabled and do nothing until you set enabled: true. Glimmervoid checks each repository every 5 minutes and remembers what it saw in workflows-state.json, so the first check of a repository only takes stock and fires nothing, and an event fires once even across restarts. At most 20 actions run per check. Settings > Workflows turns workflows or a single rule on and off and changes the session and action limits. A workflows block that does not validate runs no rule at all and the server log says why.

  • Keep mergeable: toggle Keep mergeable in Reviews > Mine to have a sandboxed agent fix merge conflicts or failing checks on a local copy of that PR. The agent has no network access to GitHub, can write files only inside its own working folder, skips the repository's git hooks, and pushes nothing itself. Glimmervoid checks its commit and pushes the verified repair commit to the PR branch, so the PR itself becomes mergeable, but only when that branch still points at the commit the repair started from, so it never overwrites other work; if the branch moved while the repair ran, the push is rejected, logged and not retried. Pull requests from forks are never repaired or pushed, and a PR that closed or merged meanwhile is not pushed. Its shell cannot read your credential and tool config folders (~/.ssh, ~/.aws, ~/.config, ~/.claude, ~/.codex, ~/.glimmervoid and similar). A repair that edits anything under .github/ or adds a credential-like file (.env, *.pem, *.key, id_rsa, .npmrc, .netrc, credentials*) is not pushed, and the server log names each commit and branch it pushes. A repair stops at the Keep mergeable deadline (30 minutes unless you change it in Settings), or when you turn the flag off or the PR leaves the list. The flag survives restarts, each head commit is attempted once (a repair cut short by turning the flag off or by a restart is tried again), a repair commit Glimmervoid pushed is never repaired again, so a check still failing after a repair waits for your next push, saved flags are removed when the PR leaves the list, and work folders a crash left behind are cleaned up when My PRs starts. Behind branches still use the existing global auto-rebase setting.

  • Merge when ready: toggle Merge when ready on one of your pull requests in Reviews > Mine to add it to Glimmervoid's own merge queue; the status beside the toggle shows its place in line among the queued pull requests of the same repository. On each poll Glimmervoid merges at most one pull request per repository, the first queued one that is ready to merge, with your default merge method and only at the head it just polled. A queued pull request that GitHub reports as behind its base is updated even when global auto-rebase is off, and a pull request updated during a poll waits for the next poll before it is merged. The queue never merges a commit Keep mergeable pushed: that pull request shows Repair pushed, waiting for you, and is merged by the queue again only after you push a new commit, or you can merge it yourself with Merge. A failed merge is logged and the pull request stays queued, but that head is not tried again until a new commit lands. Merged or closed pull requests leave the queue, and the queue survives restarts. Drafts, pull requests with conflicts or failing checks, and those already in GitHub's merge queue are skipped without holding up other repositories.

  • Settings switches: Team review gains Keep mergeable and Merge when ready on/off switches (default on) and a Keep mergeable deadline (5 to 120 minutes, default 30); turning a feature off hides its toggle and pauses it while keeping each PR's saved choice. Workflows gains a master switch (default on), limits for concurrent agent sessions (1 to 5, default 2) and actions per poll (1 to 50, default 20), and an on/off switch per rule; editing a rule's other fields still happens in config.json.

  • Review request priorities: Reviews > Team includes pull requests requested directly from you, labels Direct and Team requests, and puts blocking reviews first with chips for author changes, failing checks, running checks and drafts.

  • Stacked pull requests: Reviews > Mine groups dependent pull requests beneath their parent, including across readiness sections, so you can follow a stack in order.

  • Reviews retry and refresh: when GitHub cannot be reached, Reviews > Mine and Team now retry after 10 seconds, 30 seconds and 90 seconds before falling back to the regular schedule, and the notice counts down to the next try. A Refresh button beside the tabs checks GitHub right away, except while GitHub's rate limit asks to wait. Team now shows when it cannot reach GitHub instead of failing silently.

  • Benchmarks (opt-in): compare agent setups on frozen cases. Turn on Settings > Benchmarks to show the Bench tab, then put a suite (a suite.json naming its arms, subject prompt and judge) under benchmarks/<suite>/ in the Glimmervoid home. Mine lists merged pull requests with review comments as candidates; move the ones you approve into the suite's cases folder, then choose Run. Each case runs once per arm in a fresh detached checkout of the reviewed commit, an LLM judge matches the findings against the review comments, and the tab shows paired recall per case, overall and per human and bot reviewers. One run at a time, and Cancel stops it. Arms authenticate with your Claude Code login, read from the keychain or ~/.claude/.credentials.json, or with GLIMMERVOID_CLAUDE_OAUTH_TOKEN; the token is passed only to benchmark sessions and never written to a run record.

  • Approve without comments: a ready team review now has an Approve button beside Comment and Approve and comment. It posts only the approval, stating it was made by hand, with no review body and no inline comments.

  • What a PR is for, at a glance: a team review now opens with About this PR, stating the pull request's goal and what it changes, above the verdict. The goal also shows when you hover the PR in the list. Reviews made before this update show it after Queue review.

  • Usage on session cards is now opt-in: turn on Show usage on session cards under Settings > Appearance to see each card's token count and estimated API list-price cost. It is off by default.

  • Status color reference: Settings > Shortcuts now shows a Status colors legend above the version line, listing every session status with its glyph, color and a one-line meaning, Monitoring included. The colors follow the active theme.

  • Sandbox check on Linux: Claude Code's sandbox needs bwrap (package bubblewrap) and socat on Linux. Glimmervoid now checks for both once at start and logs one warning naming the affected features when either is missing. Team review, Keep mergeable repairs, workflow spawn sessions and benchmark runs then refuse to start, saying which binary is missing and how to install it (for example sudo apt install bubblewrap socat), in the team review status, the Keep mergeable log line, the workflows log line or the benchmark run error, instead of failing inside Claude Code. Team review starts no reviews while the check fails, so no pull request uses up its review attempts or gets an error draft, and interrupted reviews wait to resume. glimmervoid doctor gains a Sandbox section with found or MISSING per binary plus the install hint, and npm install prints the same hint on Linux when either is missing. Restart Glimmervoid after installing them.

  • Merge from My PRs: a pull request of yours that is ready to merge now has a Merge button under Merge readiness on the Reviews > Mine tab. It asks you to confirm, then merges on GitHub with your default merge method for that repository, only while the pull request is still at the head you saw. Glimmervoid does not delete the branch, though GitHub still does when the repository deletes head branches on merge. Where the base branch requires a merge queue or auto-merge, the status beside the button says the pull request was queued or set to auto-merge rather than claiming a merge. Drafts, pull requests in a merge queue, with conflicts or with failing checks are never merged; the reason shows beside the disabled button.

  • Compact sidebar status: hide status words under Appearance and alerts to keep only colored status glyphs in the sidebar. The setting shows example sidebar sessions that update as you flip it. Monitoring now has a distinct color across themes, sidebar, phone screens and session cards.

  • Session tasks: each card shows what the session is working on beside its name, taken from the agent or the first prompt, with no extra model calls. Click that space to write your own task; clear it to go back to the automatic one. Rename still changes the session name itself.

  • Anonymous telemetry: Glimmervoid now sends anonymous usage and error data so it can be improved: the version, platform, when the server starts, a daily count of live sessions, when sessions start and end with their agent kind, how they exited and running time, server and dashboard errors as their type, error code and scrubbed stack frames (a crash is sent on the next start), and, while the usage lane runs, each session's token counts, models (a model name not in the pricing table is sent as unknown) and estimated cost, all under a random install id with no person profile. It never sends error messages, paths, repository or branch names, prompts, model output or terminal output. A notice prints once in the terminal on first start, and the dashboard shows a one-time notice until you dismiss it. Turn it off under Settings > Privacy, or set GLIMMERVOID_TELEMETRY=0 or DO_NOT_TRACK=1; it is always off when CI=true. Every event also says whether it came from a development install (a git clone, a source checkout or a non-default GLIMMERVOID_HOME), so maintainers can filter their own use out, and a published version carries its PostHog release id so errors link to the release they came from and a fixed error that comes back reopens. At start, once a day and when telemetry is turned on, Glimmervoid checks the telemetry-enabled flag so the maintainers can stop all sending if ever needed, by setting that flag's rollout to 0% (deactivating or deleting the flag does not stop installs); a stopped install stays stopped across restarts until a check returns the flag enabled, and a failed check or a missing flag changes nothing. The full event list is in docs/configuration.md under Telemetry.

  • Install without the npm registry: until the glimmervoid package is on npm, every GitHub release carries an installable package, so npx --allow-remote=root --allow-scripts=node-pty https://github.com/johncwaters/glimmervoid/releases/latest/download/glimmervoid.tgz installs the current release on Windows, macOS and Linux. The README and the new website at https://johncwaters.github.io/glimmervoid/ show the same command. To upgrade later, run the versioned command the update banner shows (or the versioned URL from the release page), because npx keeps rerunning the copy it cached first for the command above.

  • Flying animals settings: a new browser settings section previews every animal, lets you choose which may fly and launch one on demand, and offers timing, size and phone layout controls under Advanced. Animals now fly by every 20 to 40 seconds by default, down from every 4 to 20.

  • Keep my pull requests rebased: a new Team review setting, Keep my pull requests rebased (off by default), rebases each of your open, non-draft pull requests onto its base branch on GitHub whenever it falls behind, checked on every My PRs poll. It waits while checks are still running so CI can finish, leaves pull requests with conflicts alone, and only rebases the head it last saw, so it never overwrites a push you just made. A failed rebase is shown on the pull request's Auto-rebase row and is not retried until you push again. Pull before pushing from a local checkout of a rebased branch.

  • Approve after commenting: when you post a team review as Comment, its Reviews screen now keeps an Approve button, so an approve-with-nits review can be posted as comments first and approved after. The approval posts on its own without repeating the inline comments, and only while the pull request is still at the reviewed head.

  • Avatars in the Reviews tab: pull request authors, GitHub reviewers and requested reviewers now show their GitHub avatars on both the Team and Mine tabs, and the Team tab header shows your review team's name and avatar. Each reviewer avatar carries a colored dot for their latest review (approved, requested changes or commented), and hovering it reads the review and its age. Avatars load straight from GitHub, so when GitHub is unreachable or the account is a bot, a letter stands in with no layout shift.

  • PostHog light and dark themes: Settings > Theme now offers PostHog (Light) and PostHog (Dark), built from the palette and surface tokens on posthog.com: the warm off-white and tan surfaces with a burnt-orange accent in light, and the charcoal surfaces with the PostHog orange accent in dark. Session states and terminal colors use the same brand palette.

Changed

  • Team reviews no longer run with permission checks bypassed: the review session can only write its own result files, can read just the pull request checkout, and is refused edits to .git and .claude.

  • Benchmark subject sessions no longer bypass permissions: they may read only their staged checkout, write only their result file, and are refused edits to .git and .claude.

  • Your approval still counts, so no re-review: a teammate pull request you approved no longer comes back as Re-review after new commits (such as a stack rebase) when GitHub still counts your approval. It moves to No review needed and is not reviewed again. Where the repository requires approval of the latest push, GitHub reports review required and it still comes back.

  • Clearer re-reviews: a team pull request you already approved that came back with new commits now carries a Re-review tag in the list and a line under its title saying when you approved it and that it has new commits since.

  • Simpler plan review: read, compare and edit from one view control, with a compact phone sheet. Comment directly under each section, then send feedback or approve; pending comments must be sent or removed before approval. Accept edits is now a checkbox.

  • Restart asks which kind, and the three-dot menu is gone: the restart icon on a session card now opens a menu with Restart, which keeps the conversation, Restart fresh, which ends it and starts a new one, and Resume conversation, so a click can no longer wipe a conversation by accident. The card's three-dot menu is gone: rename by double-clicking the name, pressing F2 on it, or tapping it on a phone, Plan is the header Plan button, Trace is a header icon in debug mode, and Remove is a header icon that still asks first.

  • Quieter review header: the Review sidebar says each thing once. With no changes it drops the zero file counts and the Merge button; an in-sync branch shows its sync state on hover instead of a line of its own; a resync that changes nothing no longer adds a sentence; and the Diff view no longer prints No committed changes above the uncommitted files or repeats their counts in the header. The branch sync text is now the resync control: click it to fast-forward, push or check again, with the action named on hover.

  • Connection status by the logo: the Connected pill left the header's button cluster. A small dot beside GLIMMERVOID shows the server connection, with Connected on hover, and the word Reconnecting appears next to it only while the connection is down.

  • Less repetition on team reviews: the verdict box no longer repeats the severity counts the inline comments already show, the verdict reads the same in the list and the detail (request changes, not suggests changes), and the line beside the posting buttons that restated what they post is gone.

  • Sidebar shows names only: the left sidebar no longer prints each session's task beside its name, where it crowded and truncated the name. Hover a session to see its task; cards still show it.

  • Tidier Shortcuts and about page: shortcut groups sit in an even grid with keys left-aligned and every description starting on the same line, each section gets a ruled heading and room to breathe, and the status color legend and version line line up with them.

  • Calmer session card header: the "resumed" and "N agents" badges are gone (Monitoring status is unchanged), and a restart menu sits in the header.

  • Approve and comment: on a ready team review, the approve button now reads Approve and comment, since it has always posted one approving review carrying the review body and the ticked inline comments. After a Comment post, Approve approves without posting the comments again.

  • Approvals say they were made by hand: every team review approval posted to GitHub now starts with "Approved by hand after checking the automated review.", so it does not read as a bot rubber stamp. Comment posts are unchanged.

  • Discard and Queue review in a More menu: on a ready team review, and on a commented one awaiting approval, Discard and Queue review moved off the posting row into a More menu in the review heading, so the footer holds only the buttons that post to GitHub.

  • Nits start unticked: low-severity inline comments start unticked on a ready review. Tick one to post it.

  • Shorter comment locations: each inline comment on a team review shows just the file name and line, so its preview has room. Hover the location for the full path.

  • Review sidebar starts closed: the review sidebar beside a focused session is now closed by default, so the terminal gets the full width. The Open review button on the closed rail opens it, and the dashboard remembers your choice from then on. It closes once for everyone on upgrade, because the old saved open state is no longer read.

  • Calmer session review: the sidebar groups status and change totals above one primary action, with resync and discard in a More menu. Map, Diff and Notes tabs live in the header at equal width, Diff opens first until you pick another tab, and Send notes appears only while notes are drafted. The closed rail shows change counts, with the review status on hover, while leaving room for the terminal. The status reads as text alone, with no colored dot. The header no longer repeats the session name.

  • Usage budgets work on an unattended server: the usage scan, and the budget alerts that run on it, no longer pause while no dashboard is connected, so a server running agents overnight still scans their transcripts and alerts when a daily or monthly budget is crossed.

  • Background lanes no longer all start at once: after a restart, My PRs, Team review, PostHog and branch cleanup each wait a random 30 seconds to 5 minutes before their first poll instead of all hitting GitHub and PostHog in the same moment. A lane restarted later by a settings change still polls straight away.

  • Quieter on GitHub and PostHog when they push back: when GitHub reports an exhausted rate limit, My PRs and Team review wait until the limit resets instead of retrying on their normal schedule, and a PostHog poll that fails now backs off instead of retrying every interval. My PRs also fetches every pull request's review threads in one GitHub query per poll instead of one call per pull request.

  • A hidden dashboard tab stops working in the background: the once-a-second refresh of session timers and ages pauses while the tab is hidden and catches up the moment you return.

  • One GitHub clock for the PR lanes: My PRs and Team review now share a single 5-minute clock and take turns on it, so their GitHub calls never overlap; Team review still runs every 15 minutes. My PRs also fetches how far each open pull request is behind its base in one GitHub query per poll instead of one call per pull request.

  • A calmer dashboard: the dots on the Reviews, Usage, Radar and Visions tabs now sit steady instead of pulsing, and running sessions in the rail no longer breathe. When a session starts waiting on you, its card and toolbar stripe pulse three times and then hold a steady amber; the header's disconnected dot blinks three times and then stays red. Waiting sessions in the rail and on the phone board stay amber without animating.

  • Team reviews are much less text to read: a review now opens with its verdict, severity counts and one-sentence summary, followed by the inline comments that will post to GitHub. Each comment is a one-line card showing its severity, file and first sentence; high and critical ones start open, the rest expand on click, and the include checkbox works without opening the card. The review body, your note and the coverage notes (what the pull request changes, what the review checked, what it could not cover) sit in collapsed sections below; older reviews without coverage notes label that section Review audit. File and line references read as quiet text instead of highlighted chips, and suggested code shows as a scrollable code block. Queue rows take two lines instead of three, with one age beside the title and the verdict, author, severity counts and reviewer avatars underneath; hover a row for its other ages, GitHub review details and any attention reason. Severity counts appear on reviews that run after this update; drafts reviewed earlier show them once they are reviewed again.

  • My PRs shows each unresolved thread: selecting a pull request with unresolved review threads lists every one under Unresolved threads, with its file and line (linked to the comment on GitHub), who opened it, the start of the comment, how many replies it has, who replied last and when. Each thread says Waiting on you when someone else spoke last, or Waiting on reviewer when you did, and threads waiting on you come first. The Threads row under Merge readiness now reads, for example, "3 unresolved, 2 waiting on you".

  • Reviews show how old each pull request and review is: on the Mine tab, each pull request row says when it was opened, and the detail pane adds a Reviews list naming each reviewer's latest review (approved, requested changes or commented) and how long ago they submitted it, plus an Opened time beside Updated. On the Team tab, rows and the detail pane show when the pull request was opened, when the automated review finished and when it was posted, and each GitHub review listed there carries its age. Reviews finished before this update pick up their pull request's opened time on the next poll.

  • Team re-reviews pick up where the last review stopped: when a pull request Glimmervoid already reviewed gets new commits, whether you queue it again or the poller picks it up on its own, the reviewer now gets the earlier review's verdict and comments and the range of commits pushed since. It looks hardest at the new commits, says for each earlier finding whether it is resolved or still open, and does not repeat resolved ones. When the earlier review was posted, the new review body opens as a follow-up. After a force-push the reviewer covers the whole pull request instead. The Team tab labels these as a re-review of changes since the earlier head.

  • See which team reviews are waiting: the Team tab has a Queued section listing pull requests picked for review that are waiting for one of the two review slots, just below In review, which now sits right after Ready. When a review finishes, the next queued pull request starts right away instead of waiting up to 15 minutes for the next poll.

  • Team reviews post a bare review body: the body posted to GitHub no longer carries a summary, verdict line, recap of the change or "See inline comments". It holds only the automated-review note, your own note if you add one, and findings that cannot be placed on a changed line, one short bullet each. The plain summary still shows in the dashboard for you.

Fixed

  • Settings save failures are reported: when a settings save could not be written because the config file could not be read, no longer validated or looked wiped by another program, the dashboard now gets an error saying the settings were not saved instead of no reply. The server log names the cause.

  • PostHog status when PostHog is off: with PostHog disabled or not fully set up, the dashboard no longer logs Dropped invalid server message for the PostHog status and shows the lane as off.

  • Radar fixes never push a workflow change under an unusual file name: a PostHog auto-fix that touches .github/workflows/ through a file name with accents, tabs or quotes, that renames a workflow out of that folder, or that replaces .github or .github/workflows itself (for example with a symlink), is now held for you instead of pushed.

  • Terminal links open once: clicking a link in a session's terminal no longer opens two browser tabs when Glimmervoid was started from Ghostty or Warp. Sessions stop inheriting the launching terminal's identity, which made Claude Code open every clicked link a second time; Claude Code sessions keep clickable links. Restart Glimmervoid so sessions pick this up.

  • The update check recognizes npx launches: when you start Glimmervoid with npx, Settings > Updates and the update banner no longer suggest npm install -g glimmervoid, which installed a copy you never had. They now show the npx command for the new release (with the flags npm 12 needs to fetch the release and build node-pty) and explain that the dashboard cannot update an npx launch: stop Glimmervoid and run the command shown.

  • Visions works again in VS Code-family editors: since the 0.28 builds, the Visions extension failed to start in any newly opened editor window with "Cannot find module './tools/vscode-visions/visions-lsp-core.js'", so those windows sent nothing to Visions and showed no findings. The relay the extension starts also exited as soon as it launched and restarted every 15 seconds without ever connecting. Restart Glimmervoid to reinstall the fixed extension, then reload open editor windows. On macOS, Visions also ignored every document when the editor spelled the project folder with different letter case than Glimmervoid's project list (for example projects against Projects); those documents are now reviewed.

  • Light themes no longer show a black Focus area: with Compleated or PostHog (Light) selected and no session focused, the middle of the Focus view was black with dark text you could barely read. The page background now follows the theme.

  • Terminal text no longer goes missing after the browser sleeps: on a phone, returning to Chrome after it sat in the background for a while could leave the terminal showing only scattered letters until new output redrew each row. The dashboard now rebuilds every terminal's cached glyphs when the page becomes visible again, so the full screen comes back at once.

  • Radar no longer shows a finished investigation as still running: a browser that was disconnected when an investigation finished (for example, a phone in the background) reconnected to a status that still said "investigating, 0 steps" until the next PostHog poll, up to 15 minutes later. The status now updates as soon as the investigation finishes, so reconnecting shows its verdict and the completed investigation right away.