DMUT Agent 1.0 Release Notes

Page updated: 6 September 2026

DMUT Agent 1.0 provides a local-first Project workspace, conversations, tools, workflows, multi-agent collaboration, BYOK/local model connections, software authorization and DMUT-owned updates.

1.0.13 update

  • Fixes the remaining 1.0.12 Settings failure where Z.AI (GLM) was configured and callable by the backend while the concrete model list remained empty.
  • Normalizes legacy and display aliases such as glm, z-ai, z.ai, zhipu and zai, and prefers the populated usable catalog when duplicate provider rows exist.
  • Coalesces backend provider rows case-insensitively and safely restores the audited built-in catalog when an authenticated built-in provider's live catalog unexpectedly returns empty.
  • Aligns the shipped Z.AI and plugin fallbacks on the same curated 12-model GLM catalog so different UI paths cannot disagree.
  • Adds regression coverage through the real Settings component and real backend route, including DMUT's own .env, instead of relying only on fully mocked intermediate layers.

1.0.12 update

  • Fixes the remaining model-catalog failure in 1.0.11: when an API key was stored in DMUT's own .env, authentication and actual requests succeeded while provider discovery checked only the process environment, leaving concrete models for providers such as Z.AI/GLM as “No models found.”
  • Makes provider discovery, login status, Base URL resolution and model caching use the same dotenv-first credential resolver as the runtime, preventing UI and backend decisions from diverging for the same key.
  • Includes .env API-key and Base URL changes in the model-cache fingerprint so rotating credentials causes a real catalog refresh.
  • Applies the repair to every API-key provider in Global and CN, with regression coverage for Z.AI, DeepSeek, Gemini, OpenAI, Alibaba Cloud and mismatched CN configuration contexts.
  • Continues to bundle audited Python 3.11 and Git for Windows/Git Bash runtimes in both Windows x64 offline installers; no separate Git installation is required, and both installers carry the company signature and a trusted timestamp.

1.0.11 update

  • Fixes stale provider catalogs after adding or rotating an API key, which could leave providers such as Z.AI/GLM selectable while their concrete model list remained empty or unusable.
  • Forces a fresh provider-catalog request from every model picker when needed, preserves the last usable catalog across transient empty responses, and exposes a visible retry path.
  • Normalizes legacy provider aliases used by configuration and UI surfaces, including Z.AI, Gemini, xAI, Kimi and LM Studio, so backend and frontend identifiers cannot silently diverge.
  • Applies the fix to both Global and CN and regression-checks the other providers, Settings, first-run onboarding and runtime model switching.
  • Continues to bundle the audited Git for Windows/Git Bash runtime in both Windows installers and signs the installers with the company code-signing certificate and a trusted timestamp.

1.0.10 update

  • Bundles a version-, signature-, architecture-, license-, and file-hash-audited Git for Windows PortableGit runtime in both Global and CN offline installers, removing the clean-machine prerequisite for a separately installed Git Bash.
  • Makes the desktop prefer runtime\git\bin\bash.exe inside the installed payload and exports the same location to Python tools so startup preflight and terminal execution cannot disagree.
  • Fixes strict-CN startup after overseas cloud-browser plugins are physically removed: the runtime no longer requires plugins.browser to exist, retains local browser automation, and does not restore the excluded overseas services.
  • Requires the bundled Bash and Git executables, upstream license files, and independent Git audit report before signing or activating an offline payload.
  • Advances the version to 1.0.10 so the immutable-payload guard on an installed 1.0.9 build does not reject the repair as a same-version, different-hash replacement.

1.0.9 update

  • On 2 September, the signed Windows 1.0.9 installers were replaced to fix a packaging defect that persisted only the updater EXE and omitted the adjacent WebView2Loader.dll, causing later updates to fail during Windows process loading.
  • The installer now persists and validates the complete updater layout. The desktop checks the dependency before stopping its backend, and PostInstall acceptance verifies the updater, the Microsoft-signed loader, and a headless self-check.
  • Users who installed the earlier 1.0.9 package and encounter update failure must download and run the latest full installer once from the authorized download page. An updater that cannot start cannot install this repair by itself.
  • Ships the actual discoverable bundled-Skills tree in the Windows payload, fixing installed clients that were prompted to load dmut-agent but could not find it; Global also carries the optional Skills catalog.
  • Applies a strict CN Skill allowlist and replaces the Global product guide with a CN-specific guide; overseas platform Skills, plugins and SDKs are physically removed and recorded in build evidence.
  • Adds literal=true plain-text mode to search_files; invalid regular expressions now return an actionable retry hint instead of exposing only a raw grep/rg failure.
  • Silently skips unconfigured optional auxiliary providers such as OpenRouter and LOCAL QDS; normal False tool-readiness probes move to debug logging while probe exceptions remain warnings.
  • Preserves valid Windows file:// URLs during diagnostic redaction and stops reporting the Desktop-owned TERMINAL_CWD value as a stale .env setting.
  • Keeps the active Profile's state.db as the single authoritative conversation store and locks list, detail, message, search, rename, archive, restore and resume behavior with HTTP/WebSocket acceptance coverage.
  • Records the source commit and worktree state in build evidence while retaining the single signed EXE, in-place update, bounded backend recovery, actionable diagnostics and user-data preservation controls.

1.0.8 maintenance update

  • Fixes an update hand-off failure where a verified payload was downloaded, the desktop exited before the installer actually started, and backend recovery returned the client to the old version.
  • Requires a one-time nonce and updater PID acknowledgement after the installer enters its update stage; legacy installers are accepted only through log records appended by the current launch.
  • Pauses backend crash recovery and automatic restart during hand-off, deliberately stops old processes, and waits for the installation tree to become writable.
  • Restores the current backend and removes the owned update marker when the updater cannot start, exits early, or misses its acknowledgement deadline.
  • Adds sanitized update-failure details including the error code, exit code, launch command, installer-log location and Windows process error.
  • Applies the single-instance update marker to the signed offline-update path as well, preventing a backend relaunch during file replacement.
  • Preserves configuration, authorization, databases, memory, Skills and Project data during in-place updates; Global and CN feature and compliance boundaries remain unchanged.

1.0.7 maintenance update

  • Unifies Desktop chat RPC and history HTTP endpoints on the same durable conversation database, restoring history lists, details, messages and continued conversations.
  • Correctly handles legacy non-UUID conversation IDs instead of routing them through UUID-only handlers and returning HTTP 422.
  • Restores /api/sessions/search by preserving static-before-dynamic route ownership.
  • Adds end-to-end regression coverage for listing, reading, searching, renaming, archiving, restoring and resuming historical conversations over WebSocket.
  • Preserves configuration, authorization, databases, memory, Skills and Project data during in-place updates; Global and CN retain their existing complete-feature and strict-domestic compliance boundaries respectively.

1.0.6 maintenance update

  • Opens each historical conversation against its owning Profile database and fails explicitly when that store is unavailable instead of falling back across Profile boundaries.
  • Runs status, Profile and tool-catalog control work outside the event loop so long-running turns do not freeze health or control requests.
  • Bounds backend startup, reconnect, address resolution and secondary-Profile connection waits instead of leaving the client indefinitely stuck in a starting state.
  • Adds a lightweight backend liveness probe: idle broken connections reconnect immediately, while in-flight work receives a confirming second probe before reconstruction.
  • Applies changed context-compression settings to a live Desktop/TUI session on its next turn without requiring a backend restart.
  • Excludes display-only operational notifications from compaction focus so the active user objective remains anchored.
  • Converts configuration values to floating point only when the decimal value is preserved exactly, preventing silent mutation of long numeric identifiers or credentials.
  • Keeps the CN edition on strict domestic model, messaging, plugin and dependency allowlists while Global retains the complete feature set; experimental Hermes Relay and overseas platforms are not added to CN packages.

1.0.5 maintenance update

  • Shows the current model-request iteration during long-running turns instead of leaving the interface without status feedback.
  • Logs provider, model, request count and aggregate token usage for every model iteration without logging tool arguments or results.
  • Records WebSocket disconnections and event-delivery failures instead of silently dropping streamed or terminal events.
  • Uses an explicit backend turn-final marker to release a stuck waiting state and rehydrate the saved response when the terminal event is lost.
  • Forces redaction on real turn errors shown to the client and keeps ordinary heartbeat snapshots from being mistaken for completion.
  • Migrates only stable user data during an in-place update, skipping managed runtimes, dependency trees, Git metadata and temporary directories that could otherwise stall or race on first launch.
  • Adds regression coverage for model progress, lost-terminal recovery, heartbeat races and event-delivery failures.

1.0.4 maintenance update

  • Fixes historical conversations that were visible after an in-place update but could not be loaded or continued.
  • Coordinates backend restart with a single-instance guard, stale-process and stale-port cleanup, and forced reconstruction after startup timeout.
  • Bounds recovery retries and clears latched failures to prevent restart races and infinite loops.
  • Shows sanitized exit codes, startup commands, stderr and tail logs in installation or startup details.
  • Safely migrates the previous database, configuration, memory and Skills during an in-place update, preserving backups without overwriting new data.
  • Keeps DMUT Agent in the system tray when the main window is closed.
  • Ports the applicable session-activity, history rebind and database-migration improvements from Hermes Agent 0.20.5.
  • Keeps the CN edition on a strict domestic allowlist while Global retains the complete feature set.

Availability

  • Platform: Windows is available now; macOS is in preparation and is not yet available
  • CN: no installer is currently listed on the public download page
  • Global: contact and authorization only
  • Hosted Model plan: not for sale
  • A file not listed on the official website is not an official public installer

Highlights

  • Project-scoped conversations, files and tasks
  • Controlled file reading, creation and precise editing
  • Terminal, document and external tools with permission boundaries
  • Installable Skills, workflows and automation
  • Parallel subtasks with consolidated results
  • User-supplied cloud keys and local loopback models
  • Invitations, plans, two-device control, unbinding, revocation, expiry and offline grace
  • Update checks and installation from DMUT’s own service

The CN edition permits only mainland-China model endpoints and local loopback connections. Its default provider is DeepSeek and default model identifier is deepseek-v4-flash. The client may migrate or hide retired identifiers.

Data and known limits

Project files, conversations and model keys are handled on the device where possible. BYOK requests normally go directly to the selected model provider and are not proxied by the authorization service. Online services handle account, invitation, device hash, entitlement, consent, quote, update and necessary log data as described in the Privacy Policy.

Model outputs may be wrong or insecure; third-party availability is outside DMUT control; complex documents, OCR, fonts and layouts need page-by-page review; unattended work may pause for high-impact decisions; local model weights are not included; only the download page controls official signing and hashes.

Current Windows requirements are listed on the download page. The macOS support scope and availability will be announced on the official website. Updates are installed from Settings → Software Update and normally do not require manual uninstall. Back up important Projects before updating.

  • Product: support@localqds.com
  • Privacy: privacy@localqds.com
  • Security: security@localqds.com