You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First-run checklist: until your first session exists, the Focus view (and the Board on a phone) walks you through three steps: an agent CLI Glimmervoid can find, with the install command and a Rescan button; the folder that holds your git checkouts, with one-click suggestions for home folders such as ~/Projects that already hold git repos, or a typed path such as ~/src; and your first session. Only the current step is open, and the list goes away once a session exists.
Factory intents finish without you: a ticket that cannot be done inside its write scopes, blocks three times, or whose worker ends three turns without a change is now parked instead of stopping the run. The orchestrator keeps dispatching the other tickets and never waits on an answer, and when only parked tickets are left the intent ends partial with one notification. The Factory tab shows each finished intent's digest: what merged, what is parked with its exact need, and any flaky tests the factory confirmed. Retry parked in the tab, or glimmervoid factory retry <intentId>, reopens only the parked tickets and keeps everything already merged.
A blocked test file can widen a ticket's scope: when a ticket's own change breaks a test file outside its write scopes, the orchestrator can replace it with a ticket that also covers that file, as long as the file matches the project's widenableScopes (test folders and .test or .spec files by default). Any other missing scope leaves the ticket parked rather than worked around.
glimmervoid factory status and glimmervoid factory retry: any session can print each intent's tickets with their state, attempts, block count, last reason and next action, plus the project's spend today against its budget. retry reopens an intent's parked tickets. A factory worker or reviewer session cannot run retry.
Per-project factory profiles: projects[].factoryProfile sets a project's check commands, its focusedTestCommand and its widenableScopes, falling back to the global factory settings. The first intent queued for a project without a profile runs setup first: Glimmervoid detects the checks from the repository, proves them in a clean checkout, and asks a setup agent only when detection finds nothing that passes. Fields it cannot prove stay unset. The Factory tab shows the profile and has Re-run setup.
Guardrails tag on session cards: a session running with guardrails now shows a GUARDRAILS tag in its card header, next to the worktree tag, so you can tell guarded sessions apart from unguarded ones at a glance.
Answer Claude Code prompts from the Conversation view: a Claude Code permission prompt now shows on the Conversation face as a card with the full request, such as the whole command or the file and its edit, and offers Approve, Always allow and Decline. Always allow appears only when Claude Code suggests a rule, names the rule it adds, and keeps it for this session only. A Claude Code question shows its options as buttons, or as a short form when it asks several questions or allows more than one answer. The terminal prompt stays live, so answering in either place works and the card clears itself. A Claude Code session started before you turned on the Conversation view setting picks this up after a restart. Codex approvals now show commands up to 4000 characters instead of 300 before falling back to the terminal.
Changed
One name for guardrails: messages, glimmervoid doctor output, Settings descriptions and the folders under ~/.glimmervoid now all say guardrails, guarded or unguarded, where some still said sandbox or confined. New sessions use guardrails-temp, guardrails-homes and guardrails-policies; once every session started before this update has ended, you can delete the old sandbox-temp, sandbox-homes and sandbox-policies folders. Sandbox still names the sandbox runtime Glimmervoid is built on and the built-in sandboxes of Claude Code and Codex. The guardrails code moved from server/sandbox/ to server/guardrails/, so update any factory.protectedPaths entry under server/sandbox/ to the new paths: server/guardrails/core/guardrails-roles-core.ts, server/guardrails/core/guardrails-policy-core.ts and server/guardrails/guardrails-launch.ts.
Clearer error for a missing session folder: adding a session, or a workspace repository, whose folder is gone now says "No folder at . It may have been moved or renamed; pick it again or enter its current path." instead of a bare "Path does not exist".
Sessions that were working keep working after a restart: when Glimmervoid restarts or crashes while a session is mid-turn, auto-resume now reopens that conversation and tells the agent to continue where it left off, instead of leaving it idle at the prompt. Sessions that were idle or waiting for your answer resume quietly as before. Turning off Auto-resume sessions on startup turns this off too.
Factory check failures are short and complete: when a check fails, the worker's feedback now starts with the failing test titles and the lint and type errors inside its write scopes, and names a file in its temp folder holding the full output. Ledger and decision-log reasons keep up to 3999 characters instead of 1000. Workers run only the test files they touched with the project's focused test command, then the full checks once before finishing.
A flaky test no longer costs a factory ticket a block: a check that fails at the ticket's head is rerun once in the same checkout, only its failing test files when the project has a focused test command. A pass counts, and the test is listed as a confirmed flake in the intent's digest.
Conversation view shows tool work as one quiet line: each stretch of tool work is now a single line such as "Worked 1m 20s, 14 steps" instead of a list you could expand. The full tool detail stays in the Trace tab.
Clearer glimmervoid --help: commands are grouped into everyday commands, editor integration, commands for use inside a session, and experimental ones, and visions uninstall is now listed.
Clearer startup output: the server now prints a short banner with the version, the dashboard address to open and how to stop it, and on the very first start from a terminal it opens the dashboard in your browser once. Pass --no-open to skip that. The first-run telemetry notice is down to two lines, and the line saying remote mode is off is gone.
Repository roots accept ~: a repository root typed as ~/src in Settings now saves as the full path under your home folder instead of being refused as a missing directory.
+ Session works before you add any repository roots: instead of a dead-end "No projects found", the dialog offers the same add-folder block as the checklist and fills the project list in place once you add one. Advanced options is now labelled "Run in a folder outside your repository roots".
Pull request sessions keep your permission choice: Open in session on a team review pull request now skips permission prompts, with the Sane YOLO hook, whenever the matching repository's session does, or whenever skipPermissionsByDefault is on when no session lists that repository. It used to always start with permission prompts. Prompts are skipped only when the session runs with guardrails, which means it runs Claude Code and the checkout is not under guardrails.unguardedRepos; otherwise it still starts with permission prompts. The session never inherits an unguarded flag.
Reviews and Issues look like the rest of the dashboard: a session linked to one of your pull requests in Reviews, Mine now shows as the same row as in the Focus list, with its name and live status, instead of a large outlined button. Buttons on the Reviews and Issues screens use the dashboard's one button style, and secondary controls (Refresh, Filters, Back to issues, View on GitHub) are a quieter outline. The selected pull request row is a soft highlight instead of a colored stripe on its left edge.
Dependencies: cc-safety-net 2.6.12, so when Sane YOLO refuses a command it cannot parse, such as echo ${, the denial now names the reason (analysis.strict-unparseable) instead of reporting that the check failed unexpectedly. Such commands are still refused.
Fixed
My pull requests no longer shows passing pull requests as failing: a check run that was cancelled and then passed on a rerun used to mark the whole pull request "Checks failing" and start Keep mergeable repairs that had nothing to fix. Each check now counts only its latest run, and pull requests with more than 50 checks are read in full instead of judged from the first 50.
A reopened factory ticket no longer hangs its intent: when the orchestrator reopened a ticket, its new worker could pick up the dead worker's old worktree on an outdated base, and close-out then waited forever without a word. A reopened ticket's worker now always starts from a fresh worktree on the current base, the factory refuses to remove a worktree it did not create, and a worker close-out that cannot find its worktree raises a factory exception instead of stalling.
Telegram stops piling up while you work in another session: an unacknowledged session used to reach your phone after the phone escalation delay (5 minutes by default) even while you were typing in a different session. Now the phone ping waits while you type in any session. If you kept typing for the full delay after a session finished, you had it on the dashboard and moved on, so it never pings. Sessions you left less than the delay after they finished reach the phone once you have been idle for the delay, and pings that come due within a second of each other arrive together in one Telegram message, split only where they would pass Telegram's length limit. Mouse-reported scrolling, focus changes and terminal replies do not count as typing, but scrolling that the terminal turns into arrow keys, as in a full-screen app without mouse support, does.
Codex and Grok keep their hooks for projects inside your home folder: Glimmervoid used to read your own ~/.codex/config.toml and ~/.claude/settings.json as if they belonged to the project whenever the project sat somewhere under your home folder. A Codex project with codexBypassHookTrust on then lost the bypass as soon as your Codex config held any hook entry, including the trust records Codex writes itself, and a Grok session fell back to title-only status whenever your Claude Code settings had hooks. Your own config folders are no longer treated as project settings, so these sessions behave the same wherever the project lives. Hook settings inside the project still turn the bypass and Grok's hooks off as before.
Terminal replies no longer answer a waiting prompt: when a session is waiting on you and the terminal answers a query from the agent on its own (a cursor position, device attributes or color report), that reply no longer counts as your input. Before, it could end the waiting state or clear the session's notification without you doing anything.