Dots Desktop 2.3.1 — More reliable tool calling

Dots validates and repairs tool-call formatting before execution, recovers missing actions and file verification, and supports models or routers that reject or ignore native function calling through an explicit JSON tool transport.

• Validates required arguments, types, permitted names, and unknown fields before descriptions, approvals, or execution. Repairs complete JSON fences, double encoding, and trailing commas without guessing missing content.
• Supports legacy calls, object arguments, missing/duplicate IDs, streamed argument snapshots, and mixed native/JSON fallback responses. Incomplete tool responses never execute; complete final answers retain successful status even with a length finish reason.
• Missing action evidence triggers correction, then JSON fallback if native calls are ignored. Your explicitly configured fallback models can continue after repeated protocol failures, retaining successful work.
• Suppresses duplicate calls and known replays, retains custom denials and approvals, and keeps protocol payloads out of draft answers.
• Automatic mode retains tools and provider response lengths without preset tool/token quotas. Genuine command failures remain available for repair. The existing design, accessories and their colors, project previews, teamwork, and router catalog improvements are included.

Verification: 164 passing unit tests (one existing Windows symlink test skipped), build/type checks, and real Electron desktop smoke checks for tool recovery, coding/refinement, automatic work, approvals, accessories, and teamwork. Provider recovery is exercised with local adversarial fixtures; live cloud credentials and paid requests are not part of this release verification.

Execution checks are conservative and cannot guarantee correct reasoning or verify every requirement for every model. Persistent protocol failures surface as failed tasks instead of silent success. This recovery layer applies to OpenAI-compatible API providers; Codex manages its own tool executor.

Windows x64 installer and portable build are attached with SHA-256 checksums. Install over an earlier version to retain local Dots, settings, and workspaces.

Dots Desktop 2.3.0 — A clearer home, faster work

A clearer home and a faster daily workflow across Dots Desktop.

• Refined light and dark themes, compact Dot cards, clearer task states, Overview search and filters, consistent paused indicators, and calmer Teamwork/settings surfaces.
• Long conversations load earlier messages in small pages without losing the reading position. Search every message in history, filter tasks needing attention, and jump to the latest result.
• Live text updates independently of the sidebar and project pane; durable events batch together and flush immediately on completion, cancellation, or failure. Finished answers retain rich Markdown.
• Resizable per-Dot Project pane, keyboard file navigation, virtualized file lists and source rows, faster shared workspace scans, and previews that retain their state when the conversation changes.
• Completed-turn snapshots now clear stale streaming text, including edited conversation branches and late duplicate events.
• Fixed Copy for answers, memory, team results, and entire files; clipboard access is write-only through the trusted main renderer. Corrected stale preview errors and keyboard focus in large file lists.
• Existing accessories/colors, Dots communication defaults, automatic tool budgets, provider catalog discovery, and multi-agent Teamwork are retained.

Verification includes unit tests and isolated Electron checks using local fixture providers. A 14,000-line source file renders fewer than 60 visible rows; a 953-file project renders fewer than 50 file rows. The renderer stress fixture delivers 500 draft chunks with zero unrelated AppContext renders and retains 2,000 durable events in one batched publication. These measure local rendering/workspace behavior; provider response speed depends on the selected service.

Windows x64 installer and portable build included. Install over your previous version to retain local Dots, settings, credentials, and workspaces. SHA256SUMS accompanies the downloads.

Dots Desktop 2.2.1 — One conversation, optional project panel

Each Dot now has one Conversation tab. Its project is an optional panel rather than a second conversation tab.

• Removed the universal Build tab. Open or close Project in the Conversation header, or open project files with the composer's folder button.
• Project panels start closed and belong to each Dot separately. Opening a project for one Dot does not change other Dots. Closing it preserves the conversation, draft, and referenced files.
• Fixed duplicate React keys for the conversation and project panels. Switching Dots no longer leaves an old conversation/composer on screen.
• Keeps all 2.2.0 coding features: code inspection, changed files, interactive static previews, local dev-server connections, actual command output, coding actions, and implementation/check/repair guidance.

Validation: TypeScript and production build passed. The packaged Windows app passed 21 end-to-end coding/navigation checks, including one Conversation tab, no separate Build tab, optional panels per Dot, one composer after Dot switching, draft/reference preservation, real file tools, failed-check repair, interactive previews, local dev-server embedding, isolation, and narrow layouts.

Windows x64 installer and portable app are included with SHA-256 checksums. Existing Dots, accessories, provider credentials, and workspaces are preserved.

Dots Desktop 2.2.0 — Build, preview, and refine

Build, inspect, preview, and refine an app beside your Dot's conversation.

• New Build workspace with a searchable file list, source viewer, changed-file filter, and current-turn command results.
• Interactive static HTML previews load relative local CSS, JavaScript, modules, and assets. Desktop/mobile widths and refresh controls are included. Connect an explicit running localhost dev server for framework apps.
• Reference selected files in your next message without uploading duplicate or stale contents. Drafts and references survive switching sections and reloading the window. Coding metadata remains separate from your editable message and persists through conversation branches.
• Build, Fix, Polish, and Test shortcuts. All providers, including smaller API models, receive an inspect → implement → check → repair workflow matched to Economy, Balanced, or Thorough. Checks are reported from actual command output; no new rigid token/tool budgets were added.
• Static previews are served read only on loopback and run in a sandbox without access to Dots IPC or the parent UI. File inspection enforces real workspace boundaries, including symlink checks and bounded reads. Hidden paths are not served.
• Includes all earlier accessory colors, additional accessories, automatic Dot communication, teamwork, automatic tool budgets, and complete 9router/OpenCode Free model discovery.

Framework dev servers must already be running. Some apps need a normal browser for cookies or APIs that disallow opaque origins. Model behavior still depends on the selected provider; guidance does not guarantee a model will always complete or test a task.

Validation: 95 unit tests passed (one existing Windows-only symlink test skipped), TypeScript and production build passed. The packaged Windows app passed the coding flow with a deterministic compatible-provider fixture: real file creation, failed-check repair, interactive CSS/JS preview, isolation, file references, continued conversation, drafts, local dev-server embedding, mobile width, and narrow-window layout. Additional packaged regression checks cover accessories, automatic tools, teamwork, and full local 9router model discovery. No paid model requests were needed.

Windows x64 installer and portable app are included with SHA-256 checksums. Existing Dots, provider credentials, workspaces, and accessories are preserved during installation.

Dots Desktop 2.1.5 — Complete 9router model catalog

Dots now shows the complete local 9router catalog, including OpenCode Free models that its standard /v1/models endpoint omits when other providers are connected.

• Adds a guided 9router preset and reads the installed router's authenticated catalog client at its standard loopback endpoint. Router credentials stay in the main process and are never forwarded to remote hosts or other ports.
• Preserves every unique routing ID, groups router models by provider, and labels models needing setup as Enable in 9router.
• Removes the 60-result cutoff in provider setup. Adds Refresh models to profile and new-Dot pickers while preserving the selected model.
• Recognizes router tool/context metadata and OpenCode Free models, including free models without a -free suffix. Discovery failures now appear instead of silently showing only the default model.
• Includes all earlier accessories, separate accessory/glasses colors, teamwork, work styles, automatic token/tool limits, and completed-answer fixes.

Verified against the user's live 9router catalog: all 1,148 unique model IDs and all six OpenCode Free models are present. Typecheck and production build pass; 87 unit tests pass (one skipped). The Windows package passes 67 checks covering live model discovery, all three model pickers, provider setup, teamwork, accessories, and full file writing past old preset cutoffs. No paid chat requests were used for discovery verification.

Complete catalog discovery uses an installed 9router CLI on the standard local port 20128. Remote routers and installations without that CLI use the standard API model list. Listed models may still need router setup, account access, or tool support.

Dots Desktop 2.1.4 — Automatic work without preset cutoffs

Automatic work is now the default for new and existing Dots. Preset token totals, tool-step counts, and output caps no longer force agents to stop before completing their deliverables. Compatible routers use their own response lengths; context compaction expands when required and can retry with less history if the provider rejects the context.

Economy, Balanced, and Thorough still give explicit behavioral instructions. Custom token/tool caps are an opt-in profile setting. File tools support appending chunks, with guidance to write and verify the actual file rather than reporting a plan. Time limits, cancellation, permissions, provider limits, and explicit shared team allowances remain in effect.

Validation: 83 unit tests passed, production build, and packaged compatible-router file-writing and settings checks. Windows installer and portable build included.

Dots Desktop 2.1.3 — Keep completed answers

Fixes a false token cutoff error after Codex had already completed and displayed an answer. Terminal usage reports are now identified as completed-turn accounting and no longer cancel a successful answer.

Genuine provider failures, user cancellation, and live token budget enforcement remain in effect. Codex budget guidance now explains that final usage is reported after completion.

Validation: 80 unit tests passed, production build, and isolated Electron/Codex subprocess completion checks. Windows installer and portable build included.

Dots Desktop 2.1.2 — Behavioral work styles

Economy, Balanced, and Thorough now give the agent explicit workflows, work depth, verification requirements, and stopping criteria. Every compatible model request and fresh or resumed Codex turn receives these instructions; provider reasoning settings are not required. Team members follow their own style.

Work style is saved independently of editable token limits, preserving older preset selections. API agents receive progress checkpoints and an explicit wrap-up request as limits approach. Explicit user scope always takes priority.

Validation: 76 unit tests passed; 23 packaged workflow and provider setup checks. Windows installer and portable build included; existing Dots and settings retained.

Dots Desktop 2.1.1 — Overview cleanup

Removes the duplicate 'Put your dots on the same team' button from Overview. The remaining button opens Teamwork as intended.

Windows installer and portable build included. Existing Dots, settings, and workspaces are retained.

Validation: production build and packaged Overview navigation check.

Dots Desktop 2.1.0 — One goal, a team of Dots

Dots Desktop 2.1.0 — One goal, a team of Dots

This update adds coordinated team tasks, token controls, and guided setup for hosted routers and local models.

Teamwork

• Choose two to eight Dots, write a goal, edit individual assignments, and choose a lead.
• Work in parallel, pass work along a sequence, or have the last Dot review earlier contributions.
• Dependencies receive completed results automatically. The lead produces one combined answer.
• Each Dot keeps its own provider, model, workspace, and permissions. Execution follows the existing concurrency setting and runs one task at a time per Dot.
• Follow live progress, inspect contributions, open conversations, and copy the final result.
• Stop a whole team task. Resume unfinished work while keeping successful contributions and cumulative usage; add token allowance when needed.
• Team plans and results persist locally. Restarted tasks are marked interrupted and wait for Resume.
• Coordinated assignments cannot start recursive teammate messages or wakeups. A worker failure blocks pending assignments before the next execution slot opens.

Token efficiency

• Economy, Balanced, and Thorough presets in Profile → Model & computer and the new-Dot dialog.
• Context, response, task, duration, and tool-step allowances.
• API requests compact older conversation turns and long tool output, preserving the current user message and valid tool-call/result pairs.
• Compact memory and responsibility context; fresh conversations for team assignments and concise dependency handoffs.
• Input, output, cached, and estimated usage in conversations and team results.
• No extra model call is used to summarize old history.

Easier API setup

• Eight presets: NVIDIA NIM, OpenRouter, Groq, Cerebras, Ollama, LM Studio, OpenAI API, and custom compatible routers.
• Key links, provider setup guides, sensible endpoint defaults, and pasted completion-URL normalization.
• Test unsaved settings and discover models before saving. Search available models, filter free models and confirmed tool support, and inspect context metadata.
• Keyless local endpoints, encrypted credentials, and saved-key reuse restricted to the original endpoint.
• Optional explicit fallback models at the same endpoint after rate-limit or service errors; retry progress is visible.
• Direct setup shortcuts from onboarding, Connections, and a Dot draft. Escape closes provider settings while preserving the draft.

Validation

• TypeScript checks and production build passed.
• 71 unit tests passed; one existing Windows symlink test was skipped.
• The packaged Windows executable passed 20 new end-to-end checks using seven deterministic local API requests, including different providers, dependency review, lead synthesis, encrypted keys, token presets, cancellation/resume, and persisted results.
• Packaged regression checks passed for messaging defaults and replies, accessory colors and persistence, and the desktop companion's Open Dots behavior.
• The staged website passed 27 responsive, motion, and playback checks. Electron suites reported no renderer errors.
• Installer, portable executable, update metadata, blockmap, and SHA-256 checksums are included.

Provider and execution limits

NVIDIA NIM offers trial access subject to its account limits and terms. OpenRouter's free router selects compatible free models, subject to provider limits; other model and fallback choices can be paid. Cloud account keys are supplied by the user. Connection tests list models rather than generating a completion or proving every model's tool support. Cloud configuration was checked against provider documentation and tested through compatible local fixtures; no live cloud credentials were used.

Token counts use reported usage when available and estimates otherwise. Context caps are estimated; task allowances stop subsequent work as usage arrives, and an in-flight request can exceed the remaining allowance. Codex manages its own context/output and reports usage separately. Teamwork runs on this computer while Dots is open; it does not add cloud hosting or cross-device sync.

Install the new Windows build over an earlier version to retain existing Dots, settings, and workspaces.