> For the complete documentation index, see [llms.txt](https://docs.controltheory.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controltheory.com/controltheory-documentation/dstl8-docs/release-notes.md). # Release Notes What's new in Dstl8 ## October 9, 2026 ### Single Sign-On You can now edit an SSO connection: choose **Edit** from its actions menu under **Organization Settings → SSO**. See [Edit a connection](/controltheory-documentation/dstl8-docs/single-sign-on.md#edit-a-connection). * **Replace a client secret without deleting the connection.** Paste the new secret into the connection's **Edit** dialog and save; users stay linked. Then run **Test Connection**: a new secret needs a new test, as below. * **A new client ID, client secret or issuer URL needs a new test.** Saving one turns an enabled connection off until **Test Connection** passes with the new settings (for OpenID Connect, with a trusted email), which turns it back on. ## October 8, 2026 ### Single Sign-On Your organization's members can now sign in to Dstl8 through your own identity provider. See [Single Sign-On](/controltheory-documentation/dstl8-docs/single-sign-on.md). * **OpenID Connect.** Connect Microsoft Entra ID, Auth0, Okta or another OpenID Connect provider from **Organization Settings → SSO**, alongside your own Google or GitHub app. * **Test Connection** signs you in through your identity provider and checks that it sends a trusted email address. A new connection is enabled by its first passing test, except that a test returning an untrusted email doesn't enable an OpenID Connect connection. * **Every provider is tested first.** New Google and GitHub connections also start disabled, shown as **Not tested**, and need a passing test before they can be enabled. Connections that are already enabled keep working. * A **Continue with** button for your connection appears on your organization's sign-in page: your connection's name for OpenID Connect, **Google** or **GitHub** otherwise. * **Invite-only.** Invited users link their identity provider account on their first SSO sign-in and keep their role and workspaces. * **Unlink.** Admins can unlink a user's SSO account from the **Users** page; the user's next SSO sign-in links the account they use then. ## October 5, 2026 ### Code Graph * **New public GitHub Action.** Push your code graph from GitHub Actions with [`control-theory/dstl8-codegraph-action@v1`](https://github.com/control-theory/dstl8-codegraph-action). It runs on Linux and macOS runners, has a `dry-run` mode for auditing exactly what would be sent, and an optional `fail-on-error`. The previous example pointed at an action path that wasn't publicly available; if you copied it, switch to the new action. See [Code Graph in CI](/controltheory-documentation/dstl8-docs/code-graph/ci.md#github-actions). ## September 29, 2026 ### Memory A new **Memory** page (**Settings → Memory** in any workspace) shows everything Möbius has learned about your workspace, and lets you review and correct it. See [Memory](/controltheory-documentation/dstl8-docs/memory.md). * **Learns from how you close incidents.** Close an incident as **Fixed** and Möbius remembers the problem and its fix together, with an optional **How was it fixed?** note. Close one as **Not an issue** and it learns the pattern as expected noise. * **Grouped into tabs** — Needs review, Known issues, Noise, Dependencies, Components and Guidance — with search, and paging for long lists. * **Review what Möbius suggests.** Approve, edit, retire, restore or pin any fact as guidance. * **Learning timeline and dependency map** show what Möbius has learned over time and how your components depend on each other. * **Keeps itself tidy.** Repeated confirmations strengthen facts, unconfirmed suggestions retire on their own, and duplicates are merged. * **Organization-wide facts** appear on every workspace's Memory page. ### Incidents * **Analysis.** Möbius now writes a structured analysis for each confirmed incident: ranked hypotheses with confidence and evidence, a timeline, the blast radius, and suggested facts for Memory. Rate each hypothesis with a thumbs up or down. See [Analysis](/controltheory-documentation/dstl8-docs/incidents.md#analysis). * **Blast radius** lists each affected component, how it relates to the incident (for example *likely cause* or *hosts the affected workload*), and links to it in your topology. * **Seen before.** An incident that matches a known problem shows the earlier incidents and what fixed them. * **One Actions section.** Next steps come from the analysis when there is one. * **Copy for AI** now includes the full analysis. * **Checked before you see it.** Möbius verifies a new incident's evidence against your telemetry before it appears. * **Recurrences reopen the earlier incident**, so its history and fix stay together. Incidents that go quiet wind down on their own. * **Faster detection.** Möbius checks for new problems more often, so new incidents appear sooner. See the updated [Incidents](/controltheory-documentation/dstl8-docs/incidents.md) page. ### Möbius Chat * `/remember` saves a fact to the Memory page, for the workspace or your whole organization, and `/forget` retires it. Retired facts can be restored. See [Möbius Chat Slash Commands](/controltheory-documentation/dstl8-docs/slash-commands.md). * On an incident page, the chat knows the incident's analysis and actions. * A collapsed chat stays collapsed when you move between pages or reload. ### Canvas **Canvas** is new: dashboards of live panels that you build by describing what you want to see. See [Canvas](/controltheory-documentation/dstl8-docs/canvas.md). * **Ask Möbius for a canvas** from any page — "the cart service's errors and its noisiest patterns over the last hour" — and edit it in chat: resize panels, add a breakdown, narrow to one service, change the time window. * **Ask about what you selected.** Click a heatmap cell, bar or series, then ask "why is this spiking?" or "focus on this". * **Many panel kinds:** time series, bar, pie, treemap, stats and gauges, heatmaps, topology, service dependencies, log patterns and samples, incidents, events, anomalies and notes. * **Other ways in:** **Build canvas** on an incident, **Open in Canvas** from a workspace dashboard or source page, and starter templates. * **Edit by hand, too:** add, move and resize panels; set the time window, the scope and variables such as a service menu. * **Revisions** keep every earlier version, including Möbius's edits, so any change can be undone. * **Share with organization**, or save someone else's canvas as your own copy. ### Code Graph (beta) The **Code Graph** connects what changed to what broke, from your logs alone — without sending your source code to Dstl8. See [Code Graph](/controltheory-documentation/dstl8-docs/code-graph.md). * **Built in your CI.** A one-line CI step (`dstl8 graph push`) maps your repo inside your own build environment and sends Dstl8 only that map: paths, symbol names and log format strings, never file contents. Read the artifact first with `dstl8 graph build --dry-run`. Examples for GitHub Actions, GitLab CI and Jenkins are in [Code Graph in CI](/controltheory-documentation/dstl8-docs/code-graph/ci.md). * **Log patterns link to the code that emits them** — the repo, file, line and function. * **Deploys expand into what they shipped:** the files and log statements each deploy changed. * **Causes with receipts.** When a deploy changed the file that emits an erroring pattern, Möbius cites the deploy, the file and the line together. * **Related Code** on the incident page lists the lines behind the incident's log patterns. * **Blast radius from your code:** symbol search, dependency traversal and third-party SDK inventories, so an outage at a provider maps to the services that use its SDK. * **MCP tools.** `list_code_repos`, `code_for_pattern`, `code_changes`, `find_symbol`, `code_impact` and `service_dependencies` work in Claude Code, Cursor and other MCP clients. See [Code Graph MCP Tools](/controltheory-documentation/dstl8-docs/code-graph/mcp-tools.md). * **Configuration** with `.dstl8.yaml` to declare services and `.dstl8ignore` to exclude files. See [Code Graph Configuration](/controltheory-documentation/dstl8-docs/code-graph/configuration.md). ## July 20, 2026 ### Log Viewer * **Better filtering** — select multiple values within a single dimension, and filter by sentiment. * **Source labels** — every log line now shows which source it came from. * **Drag-to-select improvements** — selecting a time range on the chart now shows the selected time as you drag, adds a reset button to clear the selection, and no longer leaves a gap at the end of the range. * Fixed a vertical spacing issue that could cause log lines to overlap. ### Log detail modal * Active filters are easier to see, and sentiment is now shown. * Source labels appear here too, matching the Log Viewer. ### Incidents * Changing an incident's state now prompts for a reason, so the incident timeline stays complete. * The Sources section is now clickable — jump straight to a source's details page. * The **Investigating** label is now legible in dark mode. ### Topology * A new **Namespaces** section in the resource tree makes it clearer what you're looking at. * Selecting an object now shows its related logs and log patterns right in the details panel. ### Anomalies * Anomalies are now surfaced on the workspace dashboard, source details, and incident details pages. * Each anomaly shows what was detected, why it was flagged, and its related log patterns. * A **View Logs** button drops you into the Log Viewer, pre-filtered to the logs that triggered the anomaly. ### Other improvements * Delete buttons and confirmations are now consistent across the UI. * The workspace list is now sorted alphabetically. * The setup guide's **Need a hand?** button now hides once you've completed the setup flow. * The setup guide has a new **Chat instead** button to jump straight into Möbius Chat. * Sources shown on workspace views are now clickable and link to the source details page — including sources that are still loading. * The **MCP** section in the left navigation is now **MCP / CLI**, with CLI setup instructions added alongside the MCP integrations. * Fixed: the source details page showed the source ID instead of its name. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.controltheory.com/controltheory-documentation/dstl8-docs/release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.