Repository navigation
Glimmervoid v0.31.0
Added
-
Intents can carry their tickets: a
factory-queue-intentrequest accepts an optionalticketslist (id, objective, criteria, dependsOn, writeScopes). The factory writes those tickets into the ledger itself when the intent becomes the active one, with their dependencies and the intent's risk and boundary, and the orchestrator dispatches exactly those tickets. Such an intent can be queued behind an open one, and two of its tickets may write the same path only when one depends on the other. An intent queued without tickets is still decomposed by the orchestrator. -
The factory verifier sees what changed: the verifier that closes an intent now receives the diff of everything that landed on the integration branch since work on that intent began, so it can judge criteria about what changed and what stayed the same.
-
Factory decision log: the factory now keeps a local decision log at
<glimmervoid home>/factory/<projectId>/decisions/<YYYY-MM-DD>.jsonl, retained for 14 days. -
Anonymous factory outcomes: telemetry now includes one
factory_decisionevent per factory decision, carrying only the kind of decision, how it came out, the class of failure, its duration and attempt number. It never carries an objective, a reason, check output, a path or a repository name, and it follows the same switches as all other telemetry (telemetry.enabled,GLIMMERVOID_TELEMETRY=0,DO_NOT_TRACK=1). The first-run notice, the Privacy setting anddocs/configuration.mdname it. -
Factory projects are trusted for Claude Code automatically: before the factory starts an orchestrator, it marks the project's repository root as trusted in your Claude Code config (
.claude.json, or the legacy.config.jsonwhere Claude Code still uses one, honouringCLAUDE_CONFIG_DIR), so the orchestrator no longer stops on the folder trust dialog. It sets only that one project'shasTrustDialogAcceptedkey, under the same lock Claude Code uses, and records the grant in the decision log. With telemetry on, the grant is also counted as an anonymous factory outcome that carries no path or folder name. When the config is missing, unreadable or stays locked, nothing is written and the factory raises an exception naming the folder. A project whose git directory is not a plain.gitfolder (a bare repository with worktrees, a separate git dir, a submodule) is left untouched and still needs the dialog accepted once by hand. -
Merge celebrations wait for you: a merged pull request no longer pops a celebration on its own. It lands in a trophy button just left of + Session, which turns green with a count of how many are waiting (and sits neutral when nothing is), and clicking the trophy plays them one after another, oldest first, so none go off while you are away. The tray keeps the latest 20. Celebrations now have sound: a whoosh as the banner drops in, a thump on the scene impact, then a short brassy level-up jingle. Each click of the trophy starts from the first of five jingles and steps through them, each one a step higher, so back-to-back celebrations never repeat one, and the confetti starts smaller and grows with each one. The Alert sounds switch mutes them.
-
Issues know their sessions and pull requests: each issue shows the session you opened for it, with a Go to session button and no duplicate sessions, plus the pull requests linked to it with their state.
-
Shared GitHub teams: Settings gains a GitHub teams list (org/team) that team review searches across; an existing teamReview org and team keeps working unchanged.
-
Knowledge graph (experimental): turn on Settings > Lanes > Knowledge graph to use
glimmervoid kg, a typed, offline graph of your projects, tasks, notes, references and research questions, kept in one file under the Glimmervoid home. Fields and links are checked as you write them, so a task cannot block itself in a loop and a link only joins the kinds it is meant for.glimmervoid kg nextlists unblocked tasks by priority, andglimmervoid kg trackpoints a task or note at a ticket, decision, blocked report or conjecture in a repo's Coherence ledger, after whichglimmervoid kg deltashows where your status and the ledger disagree, completed work with no verification, and retracted decisions. It only reads ledgers and never changes a repository, its git index included. Off by default. -
Connecting indicator: while the dashboard reconnects after you come back to it, each terminal shows a Connecting label with one of your flying animals running on its trail, the startup loading screen shows one too, and the header dot pulses until the logo arrow flashes green, so a terminal that is catching up no longer looks frozen. Anything you type meanwhile is still delivered once the connection is back.
-
Factory tab: turn on the Factory setting to get a Factory tab that shows the coherence ledger of each repo whose integration branch holds a coherence.config.json as a live floor: the active intent and its criteria, the queue, working agents, review, watch and shipped work. Glimmervoid ships the
@danilocampos/coherenceledger CLI (0.37.1) for it. Experimental and not yet reliable end to end: queue an intent from the tab and a master orchestrator session per repo breaks it into tickets and dispatches workers. Glimmervoid admits only tickets inside the intent write scopes and under the risk ceiling, live-worker cap and daily budget, then merges a worker change only after the write-scope fence, the repo checks (run in a clean checkout of the worker commit with an allowlisted environment) and an independent reviewer pass; a change too large to review fails the attempt. Post-merge watch windows check mapped PostHog projects for new error-tracking issues (an unmapped project is recorded as unwatched, and a failed query carries the window forward), and an independent verifier closes each intent, recording a rejection as a ledger defect shown on the floor. Only intents you queue from the tab are ever worked: the orchestrator may add tickets only under its active intent, and any other ledger write it leaves pending is discarded and raised as a factory exception. The clean checkout for the checks is staged with git hooks off and the same allowlisted environment, and a staging failure is redacted before it reaches the worker. Pausing a repo also holds merges and new dispatches, and a daily budget refuses dispatch while usage tracking is off. Settings:factory.maxRisk,factory.maxLiveWorkers,factory.checks,factory.protectedPaths,factory.reviewerModel,factory.watchWindowMinutes,factory.watchProjects,factory.dailyBudgetUsd,factory.verifierModel. Factory sessions never stop on permission prompts, and a stalled or never-started factory session raises a factory exception. Factory sessions run in Claude Code's sandbox, which blocks writes outside the session's own checkout, the temp directory and the git data a worker needs to commit (never the repository's hooks, config, packed refs, replace refs or integration branch) and blocks all outside network, but allows the local Glimmervoid port, so code a worker runs can still reach Glimmervoid itself. A ledger landing refuses, with an integration branch moved outside the factory exception and without pushing, while your local integration branch holds commits its origin branch lacks that the factory did not put there; when a factory merge or ledger landing reached your local integration branch but its push failed, the next landing pushes it first instead of stalling. They also always run with the Sane YOLO hook, and the factory refuses to start them, with a Sane YOLO is unavailable exception, when cc-safety-net is missing. The repo must already be trusted in Claude Code. When a dispatch is refused for a passing reason, such as the live-worker cap, the idle orchestrator is told once the last refused ticket can be dispatched again; Glimmervoid never dispatches it by itself. A daily budget refuses dispatch until usage history has finished its first scan, after which later partial scans keep spend known, and it refuses without that notice while usage history cannot be read. Changingfactory.checks,factory.protectedPathsorfactory.maxRiskrestarts the factory sessions so none keeps the old permissions; other factory settings apply without a restart.
Factory Git operations suppress repository commands and keep server secrets out, ledger landings reject concurrent forged factory records, and failed breach landings keep their watch until the defect lands.
Changed
- Linux sandbox check also needs ripgrep: the sandbox check at startup,
glimmervoid doctorand the install notice now look forrg(ripgrep) besidebwrapandsocat, because the sandbox runtime refuses to start without it. With any of the three missing, team review, Keep mergeable repairs, workflow sessions and benchmark runs refuse to start and say which binary is missing; install all three withsudo apt install bubblewrap socat ripgrep. - Tickets, not work orders: Factory and knowledge graph text now says ticket wherever it said work order or order: the Factory tab, settings descriptions,
glimmervoid kghelp and errors, dispatch refusal reasons and the prompts factory sessions receive. A ticket is still a Coherence work record, socoherence workcommands andwrk-ids are unchanged. - Roomier phone header: on the phone layout the top bar drops the ?, mute and power buttons, leaving the + Session button and the merge celebration tray. Mute moves to a new Alert sounds switch under Settings > Appearance and alerts (it also flips the desktop note button), Restart lives under Settings > Updates, and shortcuts and version under Settings > Shortcuts and about.
- Issues tab redesign: Issues now uses the Reviews layout: scope tabs for all, yours, your teams and your projects, search and filters, live session status on every row, and a detail pane that loads the description and opens or jumps to the issue's session.
- Pull request status icons: pull request statuses in Reviews (Team and Mine) now use GitHub's own Octicons, one per meaning (merged, draft, conflicts, behind, checks failing or running, changes requested, threads, waiting on a reviewer, your turn, queued, from a fork, out of date and more), instead of five shapes shared across every status. Color still shows urgency. The help page (the ? button) lists every icon under Pull request icons. Octicons are used under the MIT License, shipped as octicons-LICENSE.txt.
- Issues load on their own: the Issues tab now polls GitHub in the background for your configured projects' open issues plus issues assigned to you or mentioning your GitHub teams, keeps the last results across restarts, and shows them as soon as the dashboard opens.
- Reviews Refresh at the bottom: the Refresh button and its status now sit in a footer at the bottom of the Reviews queue, on both Team and Mine, and a long refresh status wraps instead of being cut off.
- Review panel on Focus only: the review panel now shows only on the Focus tab, so Issues, Usage, Radar, Visions, Hooks, Trace, Bench, Factory and Settings get the full width.
- Quieter review panel: the review panel says each thing once. In Diff, the Committed section names the branch it merges into only when the headline does not already, and the header drops its combined file and line totals because each section shows its own (Map and Notes keep them while the branch has changed files). An empty worktree shows only the headline in both Diff and Map, and a still-loading one only the headline in Diff, instead of a second line saying the same thing. Each Map repo card drops its file count, which its committed and uncommitted counts already add up to. A disabled Merge no longer adds a line repeating that the session ended or that the base branch needs a manual resync, and a base branch with no upstream, or an unknown sync state, no longer gets a second line restating its label.
- Merge celebration: when a pull request merges, the celebration now drops in as a banner near the top of the screen instead of covering the middle, plays a random sports-highlight moment in the banner itself (a bowling STRIKE!, a basketball SWISH!, a darts BULLSEYE!, an FPS HEADSHOT!, or a poker ROYAL FLUSH!) before the title slams in where it played, with confetti, and stays for about seven seconds so you can read which pull request merged.
- CommitMono everywhere: the dashboard and its terminals now use the bundled CommitMono font, so text looks the same on every machine instead of depending on which monospace fonts happen to be installed. CommitMono is used under the SIL Open Font License 1.1, shipped beside the font files.
- Monospace everywhere: the dashboard no longer falls back to a sans font for text without its own font rule, such as session task descriptions, header buttons, the update and telemetry banners, and the Focus empty state. In the focused card the task description and its timer now match the name's 12px size.
- Quieter header: the green connection dot next to the Glimmervoid logo is gone while the dashboard is connected. The dot and its label still appear while connecting, after a disconnect, or once the server shuts down. When the connection comes back after a drop, the arrow before the logo pulses green twice.
Security
- Factory sessions cannot write git data: factory workers, the factory orchestrator and read-only lanes now get no write access to the repository's git folder at all, where a worker could previously write most of it apart from a short list of protected files. Workers no longer commit: when a worker stops, Glimmervoid commits everything it left in its worktree under a
factory: <objective>subject and then runs the fence, checks and review on that commit, so a stray file a worker leaves behind is judged like any other change. The review always reads changes as text, so a binary file counts toward the review size limit. Glimmervoid refuses to commit a nested git repository, a shared host file such as.envthat the repository does not track, or an empty placeholder file the sandbox leaves while a command is still running, and tells the worker what to fix instead. - Factory collects a worker's files inside the check sandbox: when a worker stops, the step that reads its worktree into a commit now runs in the same sandbox as the close-out checks, so it can read only what a check can read, plus that worker's worktree wherever worktrees are kept, and write only the commit data. A close-out therefore needs the sandbox to start even when a project configures no checks. A project whose repository sits inside Glimmervoid's own folder, an agent's home folder or a credential folder cannot close out.
- Glimmervoid keeps its own working folders out of the shared temp folder: the folders Glimmervoid makes for a close-out check checkout, a reviewer or verifier run, a ledger landing and each session's settings file now live under
scratchin Glimmervoid's own folder, which agent sessions cannot write, where they used to sit in the system temp folder that every lane can write. A check folder left behind by a crash stays there until it is deleted by hand; session settings folders older than a day are still swept at startup. - Sandboxed agent sessions cannot read Glimmervoid's own folder from the shell: a factory worker, the factory orchestrator and a read-only review lane could run a shell command that read Glimmervoid's config, its secrets file or another session's settings. The shell sandbox for those sessions now hides the whole folder and keeps only its
binandfactory/bintool folders, plus the session's own working folder when it sits inside, readable. A project whose check commands read a file from Glimmervoid's folder will see that file as missing. A config file kept outside that folder with--configorGLIMMERVOID_CONFIG, and the files stored beside it, are not hidden by this change. - Sessions talk to their own port: agent sessions now send hooks and agent API calls to a separate loopback listener that serves only those two routes, on a port Glimmervoid picks at startup, instead of the dashboard port. On Linux, where the sandbox enforces it, a sandboxed lane is allowed to reach that one port only, so code it runs can no longer reach the dashboard's control channel; macOS is unverified.
- Factory checks run sandboxed: the checks a factory close-out runs on a worker's commit now run inside Anthropic's sandbox runtime (new dependency
@anthropic-ai/sandbox-runtime) with no network, writes limited to the check checkout and its temp folder, and credential folders, agent homes and Glimmervoid's own state unreadable. A close-out fails instead of running checks when the sandbox cannot start. Linux needsbwrap,socatandrg(ripgrep) on PATH; macOS uses the built-in sandbox and is untested, and a check there that listens on a loopback port fails; Windows cannot run factory checks yet. - Judge lanes without a shell run inside the sandbox runtime: the benchmark judge, the team review thread judge, the change map narrative and the task title lane, when they run on Claude Code, now start inside the same sandbox runtime as factory checks, on Linux and macOS. Such a lane can reach only Anthropic's API and its one session port, cannot read credential folders, other agents' homes or Glimmervoid's own folder, and its file tools can write only its own work folder, Claude Code's own session records and its login file. A lane refuses to start, with the reason, when the sandbox cannot start (Linux needs
bwrap,socatandrg), so on a Linux machine missing one of them these lanes stop working until it is installed. The factory reviewer and verifier and every Codex lane keep their current confinement, and on Windows these lanes run as before. Linux is verified live; macOS is unverified. - Factory checks share one sandbox policy builder: the policy a factory close-out check runs under now comes from the same builder every sandboxed session will use. Checks keep no network and writes limited to the check checkout and its temp folder, and can additionally no longer read cloud credential folders (
.aws,.azure,.config/gcloud,.kube,.docker,.gnupg),.netrc, the npm token file (.npmrc), or the Claude config file and the copies of it that sit beside it in the home folder when the check starts. Policy files moved fromfactory-check-policiestosandbox-policiesin Glimmervoid's own folder. - Factory protected paths understand wildcards: an entry in
factory.protectedPathsmay now use*inside one path segment, such asserver/factory-*, which used to match nothing. An entry the fence cannot match blocks every change rather than silently protecting none: one using?,[],{},!or a**other than a leading**/, a**/not followed by a single file name with no slash (such as**/dist/), or one that resolves to the repo root or outside it. The close-out feedback names each such entry.
Fixed
-
Reviews no longer carry the last action onto the next pull request: after Approve or Comment moves you on, the next pull request opens without the previous one's green "Approved on GitHub" line above it. The acted pull request's queue row still shows the outcome. A warning about the action still shows, and the view stays on the acted pull request when it does.
-
Factory reports an orchestrator that stopped with nothing running: when the orchestrator ends its turn while its project has no live worker, no ticket under watch, no verification in progress and no dispatch waiting on budget, worker cap or a scope overlap, nothing would ever wake it and the factory sat idle without saying so. After two minutes in that state the Factory tab now shows "factory orchestrator ended its turn with nothing running" and the project sends its usual stall notification. A paused project is not reported.
-
A factory intent no longer blocks its own tickets: the ledger reports two runnable tickets that claim the same path as a write conflict, and an intent's write scopes were recorded there as a claim of its own, so an intent scoped to a single file was blocked together with the first ticket created for that file and the factory then sat idle. Glimmervoid now keeps an intent's write scopes in its own lane state as the bound its tickets must stay inside, and records no claim for the intent in the ledger. An intent write scope is now a relative path, where a folder covers everything under it, or
**for the whole repository; a scope with any other wildcard, including a trailing/**, is refused when the intent is queued. An intent queued before this change keeps its claim in the ledger, so one that was blocked this way stays blocked until it is cancelled and queued again. -
Factory no longer stops on the orchestrator's own calibration sample: the coherence stop hook appends a calibration sample to the ledger whenever an orchestrator session that created tickets ends its turn, and the factory refused to land it and raised an exception. The sample that hook appends now lands with the orchestrator's other ledger writes, while a rewritten, deleted or forged one is still refused, as is one that carries a clean or defect verdict or sits in a file named for a different session.
-
Factory dispatch on Linux: a factory orchestrator on Linux could not start its workers, because its sandbox has a network of its own and
glimmervoid dispatchgot "fetch failed" trying to reach Glimmervoid directly. The session commands (dispatch,spawn,attention,board) now go through the sandbox's own local proxy when the direct connection is refused inside the sandbox. Outside the sandbox, and with any proxy that is not the sandbox's own, nothing changes. -
Usage catch-up on a fresh home: transcript scans keep their short continuation timer when another scan is running, so catch-up finishes without starting overlapping scans.
-
Factory worker ledger discard: committed worker ledger files are discarded even when the folder's capitalization differs from
.coherence, so they do not block close-out or reach the integration branch. -
Sleeping until chip: the "sleeping until" chip on a session card now clears on its own once the scheduled wakeup has passed, follows the latest wakeup instead of an earlier one it replaced, and clears when the session stops its loop.
-
Git errors in the review panel: when git cannot read a session's worktree, the review panel now says Could not read changes and shows git's error instead of an empty diff that looked like no work, the Map names the error for each repo it could not read, and a base branch sync check that fails says so with its error instead of staying on Checking branch sync. Once git can read the worktree again, the panel refreshes on the next change in the worktree or when you select the session again, and every failure is written to the server log.
-
No late ping for a turn you watched finish: a session that finishes a turn and stays open while you are in it no longer sends a browser notification when you leave and a Telegram message
phoneEscalationMslater. The dashboard now dismisses the finished turn on the spot, the same as clicking the terminal, when it lands in the session open on the phone Terminal screen, or on desktop in the terminal you are typing in with the window focused. A finished turn in any other session still waits for you and still reaches your phone, and a session whose process exits when its work ends is unchanged and notifies as before. -
One Telegram ping per Needs input: a session left on Needs input no longer messages your phone again every 5 minutes. Telegram now gets one message per notification, sent right away when no dashboard is open or after
phoneEscalationMswhen one is, and the next message comes only when the session asks again. Browser notifications still repeat every 5 minutes until you answer. A Telegram message that fails to send is now retried every minute until it is delivered, for up to 6 hours, instead of waiting for the next restart. -
Dormant session identity: worktree badges and workspace review controls stay intact when a session becomes dormant.
-
Bench on phones: the Bench screen now uses phone padding, full width and readable text instead of desktop panel styling.
-
Factory on phones: the Factory screen now uses phone panel padding instead of desktop spacing.
-
Turning telemetry off prevents queued events, shutdown batches and flag checks from being sent after an install-state wait.
-
Automatic update checks start or stop when their setting changes, without requiring a server restart.
-
Repository roots must be existing directories; an invalid root rejects the settings save with a clear error.
-
A notification debounce of zero now disables repeated-category suppression at startup and after settings reloads.
-
Calculate cost mode now uses calculated transcript costs on session chips instead of CLI-reported costs.
-
Restarted sessions now apply the current RTK compression setting to their hooks.
-
Settings: replay-buffer: Align replay buffer validation at 64 to 16384 whole KiB; loading legacy subminimum or fractional values normalizes them.
-
Settings: usage-daily-budget: Describe daily budgets as estimated-spend alert thresholds that do not stop spending.
-
Settings: usage-monthly-budget: Describe monthly budgets as estimated-spend alert thresholds that do not stop spending.
-
Settings: telegram-session-notifications: Explain immediate off-dashboard delivery and delayed unacknowledged escalation with a dashboard open.
-
Settings: telegram-bot-token: Show environment ownership and disable token editing when GLIMMERVOID_TELEGRAM_BOT_TOKEN supplies it.
-
Settings: usage-fetch-pricing: Describe startup pricing loads and the one-day cache rather than promising continuous daily refresh.
-
Settings: usage-retain-days: Disclose the current-month transcript retention extension when a monthly budget is configured.
-
Settings: file-record-signals: Explain full-capture signal recording and the session recreation requirement.
-
Settings: file-trace-enabled: State that trace capture changes require a server restart.
-
Settings: file-detect-background-agents: State that background detection changes require session recreation.
-
Settings: file-detect-scheduled-wakeups: State that scheduled-wakeup configuration requires a server restart and newly created sessions.
-
Settings: file-worktree-auto-rebase: State that worktree auto-rebase changes require session recreation.
-
Settings: file-worktree-rerere: State that conflict-resolution reuse changes require a server restart.
-
Settings: file-post-turn-checks: Disclose project and rule overrides that can select fixes under global Report mode.
-
Settings: file-anti-slop-prompt: Describe the built-in Claude Code quality note and the session recreation requirement.
-
Settings: file-integration-branch: Explain that changing the integration branch does not retarget existing sessions.
-
Settings: file-worktree-root: Explain session recreation and that changing the root does not relocate existing worktrees.
-
Settings: file-worktree-share: Explain that a new share list applies to future worktree preparation by newly created sessions.
-
Settings: file-port: State that listener port changes require a server restart.
-
Settings: file-branch-gc-prefixes: Explain that cleanup prefixes filter remote branches and local worktrees.
-
Settings: usage-scan-interval: Describe periodic transcript polling and scans triggered by session activity.
-
Settings: calm-layout: Describe attention prioritization while acknowledging ready and working indicators.
-
Settings: update-installed: Distinguish the running version from commit and branch information in the current disk checkout.
-
Settings: update-summary: Give computed update rows separate virtual paths so persisted paths retain one editable control.
-
Settings: session-usage-chips: Distinguish CLI-reported costs from calculated API list-price estimates.
-
Settings: compact-status: Explain that hiding phone status words preserves the Plan ready badge.
-
Settings: repository-roots: Keep case-distinct repository-root spellings instead of discarding entries by unconditional case folding.
-
Settings: sane-yolo: Disclose executable availability and trusted-hook prerequisites for permission-skip protection.
-
Settings: post-turn-checks-mode: Describe Report and Fix as defaults subject to project and individual rule overrides.
-
Settings: visions-model: Document the actual opus alias fallback for a blank model override.
-
Settings: visions-projects: Display unavailable selected projects so every stored selection can be removed.
-
Settings: visions-auto-fix: Describe automatic edits to eligible open Markdown buffers, including inactive buffers.
-
Settings: visions-activity-max-per-hour: Show the effective activity cap and reserved edit slot; require whole-number caps and migrate legacy fractions on load.
-
Settings: posthog-api-key: Show environment ownership and disable editing when GLIMMERVOID_POSTHOG_API_KEY supplies the credential.
-
Settings: posthog-projects: Use shared validation and serialization for positive safe integer ids, reject empty comma entries, and support none as an empty list.
-
Settings: posthog-min-users: Explain investigation exemptions and require whole affected counts, rounding legacy fractional thresholds up on load.
-
Settings: posthog-max-investigations: Require whole concurrency limits, rounding legacy fractions up on load to preserve effective capacity.
-
Settings: posthog-traffic-multiplier: Allow fractional traffic spike multipliers supported by the consumer.
-
Settings: visions-enabled: Describe setup for supported detected editors.
-
Settings: visions-quiet-delay: Explain immediate save and blank-line review triggers; require whole milliseconds and normalize legacy fractions on load.
-
Settings: visions-cooldown: Explain per-document cooldown and orientation exemptions; require whole milliseconds and normalize legacy fractions on load.
-
Settings: visions-dispatch-timeout: Require whole timeout seconds and normalize legacy fractional values on load.
-
Settings: visions-intent-thread-ttl: Require whole lifetime milliseconds and normalize legacy fractional values on load.
-
Settings: ingest-enabled: Explain that enabling Visions preserves an explicit ingest opt-out.
-
Settings: posthog-interval: Allow fractional polling minutes.
-
Settings: posthog-investigation-timeout: Allow fractional investigation timeout seconds.
-
Settings: posthog-escalation: Require whole affected-count escalation thresholds and round legacy fractions up on load.
-
Settings: posthog-fix-timeout: Allow fractional fix timeout seconds within the existing bounds.
-
Settings: posthog-traffic-min-users: Describe the initial-spike threshold and alert exemptions; require whole affected counts and round legacy fractions up on load.
-
Settings: posthog-traffic-cooldown: Allow fractional cooldown minutes and explain immediate escalation, recovery and duplicate suppression even at zero.
-
Settings: posthog-traffic-baseline: Require whole baseline days and truncate legacy fractional windows on load.
-
Settings: factory-enabled: Describe the current Coherence report polling and status view.
-
Settings: knowledge-graph-enabled: Clarify that Coherence ledgers stay unchanged while --db controls where graph writes occur.
-
Settings: workflows-max-concurrent-sessions: Disclose the twenty-entry deferred spawn queue and logged overflow drops.
-
Settings: rtk-compression: Show unsupported-platform installation refusal and conditional retries after the ten-minute failure cooldown.
-
Workflows stop switch: turning workflows off aborts running workflow sessions, clears queued spawns, and stops remaining actions in the current poll. Actions that already ran are recorded, so they are not repeated and the stopped ones are not run later.
-
PostHog investigation slots: issues deferred while investigation slots are full remain eligible when a slot becomes available.
-
PostHog investigation minimum: an issue first seen below the configured minimum is investigated once its affected count reaches it. Issues recorded before this release are left as they were.
-
Visions model comments: enabling Visions leaves model dispatch off unless explicitly enabled.
-
Visions project selection: selecting a later project sharing a repository path now accepts that project's buffers.
-
Visions project reloads: adding, removing, or relocating a project Visions watches refreshes the live buffer scope. Changes to other projects leave open editor connections alone.
-
Visions hourly budget: reloading Visions or ingest settings preserves the rolling dispatch budget.
-
PostHog host default: monitoring uses the displayed US cloud host when no host is saved.
-
Team review rebase suppression: failed auto-rebases remain suppressed across restarts until the pull request head changes, and the failure note stays on the pull request for as long.
-
Git never waits on a password prompt: every git command Glimmervoid runs in the background, such as repo refreshes, update checks, pull request lookups and change history, now fails right away when a remote asks for credentials, instead of some of them sitting on a prompt nobody can see until they time out.
-
One loading screen at startup: opening the dashboard no longer shows the startup loading screen and then a second Connecting screen on each terminal. The loading screen now stays up until your sessions and their terminals are connected, for at most 2.5 seconds, so the dashboard appears ready in one step.
-
Command output no longer cut off in a pipe:
glimmervoidsubcommands such aspair,visionsandagentcould stop after 64 KiB when their output went into a pipe, while still reporting success. They now finish writing before exiting. -
Global options before a command:
glimmervoid --config <path> <command>and--portwritten before a command now run that command with those options, instead of starting the server. Anything written after a command's name belongs to that command, so--helpor--versionamong its arguments no longer prints Glimmervoid's own help or version.doctor,pairandvisionsstill accept the global options after their name. -
Needs input holds while you answer: a Claude Code card stays on Needs input while you move through or scroll a question or permission prompt, and changes once the question is answered. Escape at any prompt, or Enter or an option number key at a permission or plan prompt, moves the card on right away, so rejecting a prompt no longer leaves it stuck on Needs input. Moving through the prompt still quiets its notification, so it does not escalate to your phone while you are at it.
-
Hide status words now works on a phone: with Hide status words in sidebar on, the phone Board rows drop the status word and keep the colored status mark, the same as the desktop sidebar. The setting is saved per browser, so turn it on in the phone's browser too.
-
Phone More menu matches the desktop tabs: every tab you have turned on now has a screen under More on a phone. Factory and Bench were missing there, and PR reviews is now called Reviews, the same as its desktop tab.
-
Reconnecting status fits small screens: on a phone or a window under 900px wide, the header shows only the blinking status dot while the connection recovers, instead of a "Reconnecting" label that overlapped the + Session button. Screen readers still announce the status.
-
Session titles survive a Glimmervoid restart.
-
Phone terminal reconnect: the phone keeps its fitted grid claim across reconnects, so a temporarily unavailable size measurement on resume no longer leaves the terminal clipped to a desktop-sized grid. Touch scrolling also keeps working in applications such as Claude Code after reconnecting.
-
Idle compaction settles correctly: Claude Code cards no longer stay working after compacting while idle, and the dashboard shows when a session is compacting. A notification that was waiting on you still escalates to your phone after an idle compaction.
-
Keep mergeable repairs commit again: a repair session could not write inside its checkout's
.git, so every merge failed and the Reviews tab showed "the session committed nothing" even for a conflicted pull request. The session can now commit (.git/hooksand.git/configstay locked), and when you sign your commits, Glimmervoid signs the repair commits itself before pushing, because the sandbox cannot reach your SSH agent. -
Keep mergeable heals on its own: a repair that failed or changed nothing is retried 6 hours later, then after 12 and 24 hours and every 48 hours after that, even when nothing new is pushed. Before, it waited for the base branch to move as GitHub reports it, which only updates on a push to the pull request, so a stuck repair never came back.
-
Keep mergeable hands off large pull requests: a repair that committed a merge could still fail with "could not read the session commit" when the pull request had earlier commits whose file contents Glimmervoid never downloaded. Repairs also no longer stall on a merge that brings in a changed workflow file from the base branch. A repair still never pushes its own change under
.github. -
Keep mergeable reads the repair branch: a repair that committed its merge on the keep-mergeable branch but left the checkout elsewhere was reported as "the session committed nothing". Glimmervoid now always pushes what is on that branch.
-
Recordings survive a restart: after you restarted a session or started a new task on it, its signal recording in
~/.glimmervoid/recordingsstopped until Glimmervoid itself restarted, so a missed status such as Needs input could not be traced. The respawned session now keeps recording, starting a fresh recording file for each run so an old run can still be pruned. -
Claude Haiku 5.5 is priced: the Usage tab no longer reports "No price for 1 model: claude-haiku-5-5" and counts its cost as zero. Haiku 5.5 is priced at its two rate cards, $0.10 / $0.50 per million tokens up to a 100K-token prompt and $0.50 / $2.50 above, and the bundled price list also gains Opus 5.5, Sonnet 5.5, Fable 5.1 and Mythos 5.1 so offline installs price them correctly instead of borrowing an older model's rate.