DeepCube™ 1.23.1¶

Everything since 1.18.8 lands in this Steam update. Launching from Steam signs you in with Steam, so link Steam to your DeepCube account first, and the app keeps you signed in between launches. Tessa asks before she clears the service map, runs a Shoebox or changes a preference. Preferences are rebuilt, a service is one platform however many instances serve it, and phantoms are drawn only once they have been judged. Spans that recorded an exception, or answered with an HTTP 5xx or 429, now count as failures, so some services may show a higher error rate than before.

What's New¶

• One sign-in that stays: launch from Steam and the app signs you in with Steam, with no login screen. Before your first Steam launch after this update, link Steam to your DeepCube account at https://id.deepcube.ai/account: the Steam sign-in comes first, and a Steam account that is not linked signs you in to a separate, new account. Outside Steam, or if Steam sign-in does not work (no ticket within 10 seconds, or refused), the app uses your saved session; otherwise press Start and sign in with your DeepCube account in your browser, with the same method you used before; on the next launch the app signs you straight in while your session is still valid. If you sign in inside the app instead, you sign in at each launch. If you signed in with a Microsoft work or school account, your account, grids and subscription are unchanged. Sessions from earlier versions do not carry over. Log Out takes you to the Login screen, and the app does not sign you in again by itself until you press Start or restart it; the next Steam launch signs you in with Steam again.
• Tessa asks first: before she clears the service map, builds or runs a Shoebox, requests a replay or changes a preference, she shows you what she wants to run. One yes covers that kind of action for the session. Sharing a Shoebox and using the web ask every time. Reading your telemetry never asks.
• Preferences, rebuilt: press F9 in a grid to open them, grouped into World, Display, Effects, Assistant and Advanced. Rendering quality is a dropdown of six levels, from Ray Tracing (Realtime GI) down to Minimum; a fresh installation starts on Medium, and an existing one keeps the level it had. Each control now sits beneath its name, and the mouse wheel moves the list further per notch.
• Tessa reads and changes your preferences: ask what a setting is set to, or ask her to change it. Rendering settings, sign-in and redaction stay yours to set.
• Frame-rate prompt: if the frame rate stays under 30 for ten seconds, the app offers to drop rendering quality one level. Don't Ask Again switches it off; turn it back on under Assistant in Preferences.
• Instances on the nameplate: a service's nameplate counts the instances this app has seen since it started, for example "2 live" or "1 live, 1 quiet", or "instances unknown" when its spans do not say. Ask Tessa which instance is failing, or to open the newest error from one.
• One platform per service: a deploy or a restart no longer starts a new platform with fresh history, so a grid with many replicas draws fewer platforms.
• Phantoms, judged before they are drawn: a service too new to judge no longer appears as a phantom and then clears itself. Calls to a public host name that none of your reporting services uses, and calls to databases, are drawn as external dependencies, not phantoms. The line to a phantom narrows toward it, and a phantom names its most recent callers.
• Forty skies: the full-range HDR skies are back, listed by name under Skybox, with a new Sky movement setting. Clouds now drift; set it to 0 to keep them still.
• /node-ids: type it in the chat for a list of every node on the grid and its instances, also saved to the app's logs folder. It names your services, and Demo mode does not hide them, so check it before you share it.
• Shoebox, checked before it runs: Tessa checks your diagram first, tells you what she assumed, and reports loops and services nothing calls. Paste a screenshot of an architecture diagram and ask her to run it. Anything you send to the Shoebox lands in a public sandbox, so leave out anything proprietary.
• One voice across clients: Tessa's voice is saved to your account, so you hear the same one in DeepCube Web.
• New defaults: a fresh installation keeps blocks on the grid for at least five minutes, draws up to 500 blocks per frame, and keeps connections for 160 seconds after their last call. An existing installation keeps the values it has; Reset To Defaults takes the new ones, but it also resets every other setting, including rendering quality to Minimum and Demo mode to Off, and it does not ask first.
• The chat window collapses: double-click its header to shrink it, and again to bring it back.
• Tidier log files: logs roll over, are capped in size, and are deleted after 30 days. The first launch after this update deletes every log file earlier versions wrote.
• Lighter busy grids: blocks and the service graph do less work every frame.
• Demo screens on platforms: turn on Show demo screens on platforms (Advanced) to fill three tables per platform from demo-screen-1.csv to demo-screen-3.csv in the app's Demo folder.
• Security fixes to grid access and data isolation.
• Security update: a bundled component is updated to fix a high-severity vulnerability (CVE-2026-26127) that could affect the app's availability.

Fixes¶

• Fixed teleporting off a moving platform carrying you with it, and falling when the platform you stood on was removed.
• Fixed a phantom showing no name or tags, and consumed queues showing a phantom consumer.
• Fixed one third-party API sometimes appearing as two nodes, and a new service's first traces drawing no connections.
• Fixed text with angle brackets garbling rows on in-world screens.
• Fixed the interface drawing too large on ultrawide monitors, and the camera turning while you resized the chat window.
• Fixed two copies of the app getting in each other's way at sign-in, and the chat staying blank when two copies ran at once.
• Fixed the chat waiting forever when one sentence of speech failed.
• Fixed Tessa offering her alert summary as a way to tell whether anyone is being notified or paged. Nothing is notified or paged: the summary is a check of the grid's current health against fixed thresholds.

Known Issues¶

• Demo mode hides only the grid's name. Hosts, URLs and database names are shown as your services report them. Check what is visible before you demo or share your screen.
• Phantom after (Advanced, in Preferences) is still listed, but changing it no longer changes when a phantom is drawn. Phantoms are now judged over a fixed window of about a minute.
• A call nothing answers, or a queue nothing consumes, that was already happening when the app started may not be drawn as a phantom. Check that service's connections and error rate rather than waiting for one.
• An approval prompt left unanswered can time out, and Tessa may report that you declined. Ask again and answer it.
• The chat handles one conversation at a time and is not saved between sessions.
• An open Preferences screen does not refresh when Tessa changes a setting. Close and reopen it.
• If the preferences file cannot be written, a change still applies for the rest of the session but is gone after a restart, with no warning.
• After her tools have run, Tessa's written answer can occasionally come back empty; ask again.
• At the start of a conversation, "a shoebox of 5 microservices calling each other" can get an answer about writing code. Remind Tessa that a Shoebox is the sandbox.
• Asking Tessa to clear the service map does not remove trace blocks.
• On a platform you have already visited, reloading the demo screens refreshes their rows and titles only. A change to a file's columns, or a file deleted or fixed since your visit, needs an app restart.
• The fix for being carried off a platform as you teleport does not yet apply in VR.
• macOS support is experimental and may lack full feature parity with Windows.