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
Sessions can wake themselves later. Claude Code, Codex and Kimi Code sessions can run glimmervoid wake in 15m <text>, glimmervoid wake at 14:30 <text> or glimmervoid wake cron "0 9 * * 1-5" <text>, or use the new wake MCP tool, to have Glimmervoid type a prompt into the session later, such as checking on a rollout instead of polling. The prompt goes in once the session is idle and you are not typing, framed as Glimmervoid wake w3 (you set it at 14:05): <text>. Times use your timezone. wake list shows a session's pending wakes and wake cancel <id> removes one. A session holds up to 10 pending wakes, each due within 7 days, and a cron wake keeps firing for 7 days. A malformed time, a bad cron pattern or empty text is refused with the reason. Wakes share the limit spawned sessions have when they wake their parent: after 10 wakes with no input from you, wakes stop and the session flags you until you type in it. A wake that comes due while Glimmervoid is down or the session is busy still fires once if it is less than 30 minutes late; a later one is skipped as missed, with a note on the session's card, and a cron wake moves on to its next run. A wake for a session left stopped after a restart resumes that session's conversation with the prompt. When it cannot, because the session has no saved conversation, its agent has exited, or the resume does not start, the session gets a note on its card instead. Removing a session cancels its wakes. The session card shows the time of its next wake beside its name; click it, or choose Wakes in the Session actions menu, to see every pending wake and cancel any of them. On a hosted server, a wake due within the next 20 minutes keeps the server from asking to sleep, and the doorman's watcher wakes a sleeping server when one of its wakes comes due. A doorman too old to know wakes keeps working; it just cannot wake the server for one. A wake whose session no longer exists is dropped once it is 30 minutes late.
Resize the width of a board card you open full screen. A picture, video or HTML page opened from a whiteboard now has a handle on its right edge: drag it to narrow or widen the card, and an HTML page lays itself out again at the new width, like resizing a browser window. Arrow keys move the focused handle, and a double click on it returns the card to its fitted width. The handle hides while you are zoomed in.
Wide HTML pages fit the full-screen board viewer. A page whose content, such as a wide table, is wider than the viewer now opens scaled down so the whole thing shows, with no sideways scrolling, including content the page draws after it loads. A page never shrinks below an eighth of its size, so zooming all the way in always brings text back to full size; anything wider still scrolls sideways. Dragging the width handle keeps that scale and lays the page out again at the new width, and a double click on the handle fits it again.
Changed
Days follow your timezone, even on a hosted server. The dashboard now tells the server your browser's timezone, kept as operatorTimezone in config, and Usage days and the Your day recap count from your midnight instead of the server's. A server in UTC no longer starts your Yesterday at the wrong hour. Until a dashboard connects, the server uses its own timezone. Commit answer times and Your day peak hours use your timezone too, and Radar day labels read as English month and day, like the rest of the dashboard. Times in the session debug overlay now show as 24-hour HH:MM:SS.
Fixed
A vault secret request no longer covers the terminal. The request to allow an agent's secrets now sits on the session card above the terminal instead of floating over its newest output, so you can read what the agent said about the request while you answer it. The terminal gets shorter while the request waits and returns to full height once you allow or deny.
A board the browser has stopped drawing now says how to get it back. After repeated graphics card resets, Chrome can block graphics for the whole site, and reloading the page does not lift that block. The board used to offer a Reload page button that did nothing. It now says the browser blocked graphics and that quitting and reopening the browser brings boards back. Every time a board loses graphics, gets them back or finds them blocked, including a board opened while the block is already on, the server log gets a [dashboard] board-graphics: line. It shows how many times this has happened on the page, how long the board stayed blank, how many terminals were using the graphics card and how many dashboard tabs were open at the same address, the board's image textures and canvas size, and the browser's GPU name and error text, so the cause of the resets can be found. With telemetry on, the same facts, without the board, are sent as a board_graphics_reset event.
HTML pages on a board load their images, styles and scripts on a paired phone too. A page card opened on a paired remote device showed without the files beside it, because browsers leave the pairing cookie off requests a sandboxed page makes. A page card now opens at an address carrying its own key, handed out only to a paired device or the local dashboard, and the page's files load by that key, the same way at the desk and on a phone. Keys last until Glimmervoid restarts; a card reopened after that gets a new one.
glimmervoid vault no longer reports its connection file as malformed while Glimmervoid is starting. Glimmervoid now writes the file whole in one step, so a vault companion started at the same moment reads either the old file or the new one, never a half-written one.