ZeroLog
Private preview
EN DE

264 entries · August 2026 – November 2026

Newsroom

Product changes, pricing and privacy updates, and what each one changes for you. Newest first, with release notes and links to press and directory listings.

Subscribe to the feed Press and listings

Filter by category

Gray to violet: background to important changes. Editorial user impact, not security severity.

  1. Product

    New chat screen with moving waves

    The new-chat screen in the default dark theme now follows the crystal design, with a central ZeroLog logo and a moving wave background. People starting a chat in the default dark theme see the new crystal layout and moving waves. Reduced motion remains available. No action is needed.
  2. Product

    Daily log: 6 November 2026

    A small improvement to image annotation. For people marking images, answering builder questions or copying code: less repeated rendering and fewer idle updates. Controls, exports and active deadlines stay the same; no action needed.
  3. Product

    Memory locking stays consistent

    Locking encrypted memory now also cancels memory preparation that is still running. No setting needs to change. For encrypted-memory users: locking or switching accounts discards pending memory preparation. No action needed.
  4. Product

    Copy feedback waits for confirmation

    Copy controls in chat now show success only after text reaches the clipboard. A blocked copy leaves the control ready to try again. For people copying research reports, messages, code or file previews: success now requires a confirmed clipboard write, and failed copies stay retryable. No action needed.
  5. Product

    A lighter chat start stage

    The chat start page now plays a pre-rendered video loop, which uses much less GPU and battery. The logo keeps its original colours and the seam is gone. Chat users on the start page: the start stage plays as a pre-rendered video loop (less GPU and battery), the logo shows its original colours, and the seam is gone. Reduced motion shows a still image. No action needed.
  6. Product

    An icon rail beside the chat panel

    The sidebar is now a slim icon rail with the chat panel next to it, and workspaces moved into a compact chip. All app users: the sidebar becomes a 56 px icon rail with a chat panel beside it, and workspaces move into a compact chip with a dropdown. Nothing removed, bookmarks keep working. No action needed.
  7. Product

    A shorter sidebar

    The app sidebar now has five entries, and the chat list scrolls on its own. All app users: the sidebar is regrouped into five top-level entries, and Overview, Billing, Business, Compute, zerocode, Builder and Admin moved into Settings. No page was removed, bookmarks keep working. No action needed.
  8. Product

    Daily log: 5 November 2026

    A small improvement to chat transitions. For chat, settings and documentation users: less repeated UI work, confirmed copy feedback, protection for in-flight memory operations and alerts when the outbound abuse protection fails. No action needed.
  9. Product

    Less measuring when leaving chat start

    The chat view avoids a repeated height measurement around an empty message box when sending or opening a conversation. For chat users: less repeated measurement around an empty message box during send/open transitions. All messages stay rendered. No action needed.
  10. Product

    A bigger box for new chats

    On the start screen, all tools now sit above the message box, which has far more room for text, images and files. For everyone who starts a chat: the tools move above a much larger message box. No action needed.
  11. Product

    More room for your conversation

    The chat header is smaller, with one model selector by the message input and a quieter workspace status. For chat users: a smaller header and subtler status leave more room for messages. Model selection stays by the input. No action needed.
  12. Product

    DeepSeek tool calls reach the workspace again

    DeepSeek chats could generate a valid tool call and still receive a tool-not-loaded error. Text-formatted calls now keep the offered-tool checks through conversion. For DeepSeek chats using tools: valid text-formatted calls no longer fail because request conversion discarded their offered-tool list. Retry the request in the existing chat. Permissions still apply.
  13. Product

    Model selection stays ready while you search

    Recent model lists appear immediately. Changing filters or loading another page no longer leaves the picker stuck or replaces pages you just loaded. For model picker users: recent lists appear immediately and searching or paging no longer gets stuck or replaces loaded pages. No action needed.
  14. Product

    4 November: accessibility fixes on the news pages, jobs and previews now survive updates

    The news pages fix their skip link and closing note, and two new entries cover jobs and previews that carry on through updates. The skip link and the closing note on the news pages are fixed for keyboard and screen reader users. The rest is internal; protection limits now persist across updates. No action needed. Chat input rendering and optional animated backgrounds use less repeated drawing work. No action needed. Model selection is faster to reopen and stays stable during searching and paging. No action needed. The chat start artwork is sharp again on desktop screens. No action needed.
  15. Product

    4 November: updates no longer end app previews, and the tunnel service updates without dropping connections

    A live preview of an app in your container, the one-click drive, SSH and ZeroLog Link stay connected during an update. If you watch a live preview of an app in your container, or use a one-click drive, SSH or ZeroLog Link, an update of ZeroLog no longer interrupts it. No action needed.
  16. Product

    4 November: scans, website changes and UltraSite runs now carry on through a server update

    Security scans and their fixes, website revisions with the background polish, and UltraSite runs no longer start over when we update. If you have a security scan or fix, a website change or an UltraSite run in progress, a ZeroLog update no longer restarts it. No action needed.
  17. Product

    ZeroLog Code remote turns keep their text during server updates

    If you watch or start a ZeroLog Code session from the web while we ship an update, the reply from your laptop now arrives in full. If you use ZeroLog Code remote control from the web, a server update no longer drops parts of the reply from your laptop. No action needed.
  18. Product

    The extension is on Firefox Add-ons

    Firefox now installs the ZeroLog extension in one click from Mozilla's add-on store, and keeps it up to date. Firefox users of the extension: it now installs in one click from Firefox Add-ons and updates itself. No action needed; switching from the file is optional.
  19. Security

    3 November: revoke API tokens one at a time

    Each sign-in now has its own client token for the API and ZeroLog Code. You can see your tokens in the settings and revoke one of them, or all. The API reference also has its own link in the site header now. People who use the API or ZeroLog Code: each sign-in now has its own token, listed under Settings, ZeroLog Code, and revocable one by one or all at once. Existing tokens keep working; no action needed.
  20. Product

    Approval requests in background runs survive server updates

    When a /goal run, Ultracode or a sub-agent is waiting for you to approve a command and the server is updated, the request now stays open. You answer it as usual, and the run continues on the new worker. If you approve commands for /goal, Ultracode or sub-agents, a server update no longer pauses the run while a request is open. No action needed.
  21. Product

    Design runs keep their progress through server updates

    A /design run no longer starts again at the plan when the server is updated. It hands over between two rounds and continues with the round, scores and versions it already has. If you use /design, a server update no longer restarts a running design and no longer creates duplicate versions. No action needed.
  22. Product

    Updates of the vault service no longer cut your connections

    We can now update the service that holds your vault values without cutting git, API or database connections that run through it. Long answers through a vault entry no longer stop halfway. If you use vault entries set to use only or locked, updates of the vault service no longer cut your git, API or database connections, and long answers no longer stop halfway. No action needed.
  23. Product During an update the browser extension now moves to the new copy of ZeroLog in about two seconds, ZeroLog Link stays connected, and one-click drives also survive updates of our front door. If you use the browser extension, ZeroLog Link or a one-click drive or SSH session, an update no longer cuts it off or leaves the extension unreachable. No action needed.
  24. Product

    Commands in your workspace finish during server updates

    When the AI runs a command in your workspace while we ship an update, the command now finishes and its output reaches the chat. If the AI runs commands in your workspace, a server update no longer cuts a running command off or loses its output. No action needed.
  25. Product

    Goal runs, Ultracode and the site builder keep going through server updates

    Background jobs no longer stop for a server update. They finish their current step, hand over to a new worker that is already running, and continue from there without asking you to confirm anything. If you run /goal, Ultracode, agents or the site builder, a server update no longer pauses them for your approval or makes new jobs wait. No action needed.
  26. Product

    Terminals, drives and job progress keep running through updates

    When ZeroLog rolls out an update, an open terminal, a drive or SSH session connected with one click, and the progress card of a running job now carry on. Until today each of them broke off or froze. If you work in the terminal, use a one-click drive or SSH connection, or watch a running job, an update no longer interrupts it. No action needed.
  27. Product

    Git through vault entries no longer breaks off halfway

    Git and other HTTPS requests that use a vault entry set to use only or locked could stop with a TLS error. That is fixed. No action needed. If you use a vault entry set to use only or locked for git or HTTPS from your workspace, those requests no longer stop halfway with a TLS error. If one failed, run it again. No other action needed.
  28. Product

    Your own CLI replies, uploads and approval cards survive server updates

    A reply from your own Claude Code or Codex account, a running upload and an open approval card now carry on when we update the server. Nothing starts over and nothing is lost. If you use your own Claude Code or Codex account, upload files or approve tool calls, a server update no longer cuts these off. No action needed.
  29. Product

    Stopping a Deep Research run now stops it

    The Stop button on a research card set the job to stopped, but the run itself kept going in the background and kept calling models. It now ends at the next step. If you stop a Deep Research run, it now really stops at the next step and makes no further model calls. No action needed.
  30. Product

    Deep Research keeps going through server updates

    A research run no longer starts over when we update the server. It hands over to the new worker and continues at the step where it stopped, without paying for finished steps again. If you run Deep Research, a server update no longer throws your run back to the start or bills finished steps twice. No action needed.