v1.5.17

DeepScientist v1.5.17 is primarily about making the path from install to real use more reliable.

If v1.5.16 made Copilot a real first-class mode, v1.5.17 hardens the layers around launch, recovery, Windows compatibility, connector delivery, and operator-facing diagnostics.

The result is a release that feels less fragile at the exact moments that matter most:

• first launch
• onboarding and launch-mode selection
• stalled-turn recovery
• Codex compatibility and bootstrap
• connector delivery and workspace continuation
• local runtime troubleshooting on real machines

Around that core hardening work, this release also expands local-model guidance, adds a real workspace-mode switch in quest settings, improves maintainer docs, and refreshes the public README and startup docs so they match current runtime behavior more closely.

Highlights

1. Launch and onboarding are more reliable

v1.5.17 improves several early-user-path surfaces that were still too easy to confuse or break.

Key changes include:

• fixes for the onboarding launch dialog and demo canvas flow
• improved launch-mode behavior in the workspace and settings surfaces
• a new workspace-mode switch in quest settings
• better startup and continuation handling around the current project shell
• stronger launch and onboarding E2E coverage in the web UI

This matters because the launch path is where DeepScientist has to make its operating model legible immediately.

2. Runtime recovery and direct-turn routing are more disciplined

This release continues the recovery hardening work in the daemon, quest service, and prompt path.

Important changes in this line include:

• better recovery for stalled running turns when new user messages arrive
• follow-up fixes so recovery respects stop and pause correctly
• more stable stale-state handling during recovery watch flows
• refined direct-turn routing behavior
• warmer and clearer style guidance in the interaction path without weakening execution discipline

The practical effect is that DeepScientist is less likely to get stuck in an awkward half-running state and more likely to resume from the current truth cleanly.

3. Windows and local runtime compatibility improved substantially

A major theme in v1.5.17 is making the local runtime behave better on real user machines, especially mixed shell and Windows-adjacent setups.

Notable work in this release includes:

• fixing Windows pop-up / console-window behavior for Codex runner launches
• hiding unwanted runner console windows on Windows
• fixing launcher wrapper home resolution
• sanitizing conda environment state during uv bootstrap
• adding a code-only uninstall flow for cleaner local removal
• tightening launcher and install behavior around managed runtime expectations

This matters because DeepScientist is a local-first product; install and runtime rough edges hurt trust quickly.

4. Connector and Codex compatibility got another important pass

This release also improves the bridge between DeepScientist and the external runtimes or channels it depends on.

Included work in this range:

• fixes across Feishu, Telegram, and WhatsApp connector paths
• Weixin text-send retry handling for stale-context ret=-2 failures
• fixes for MiniMax profile shadowing inside Codex probe homes
• fixes for MiniMax chat-wire MCP tool batching
• better Codex compatibility handling in config, runner, and doctor flows

These changes reduce the gap between “the system is installed” and “the system actually works reliably with the provider or connector I use.”

5. Local model guidance and maintainer docs expanded a lot

v1.5.17 also ships a meaningful documentation step forward.

New or heavily updated areas include:

• a dedicated local model backends guide in both English and Chinese
• updated Quick Start, Doctor, Settings, and Codex provider setup docs
• stronger maintainer-facing development documentation
• README refreshes in both English and Chinese
• clearer startup guidance for non-default homes and local runtime management

This is important because the product surface is broad enough now that missing docs translate directly into user friction.

Detailed change areas

Workspace and web UI

The workspace line received targeted usability and correctness work:

• onboarding launch dialog fixes
• demo runtime / canvas fixes
• workspace mode switch support in quest settings
• file tree and workspace layout improvements
• connector settings form refinements
• stronger client-side API coverage for quest files and session compatibility

Daemon, quest, and launcher runtime

Core runtime layers changed materially in this release:

• daemon app and API updates
• quest service recovery improvements
• launcher and install path fixes
• doctor and diagnostics expansion
• Codex compatibility improvements in runner and config paths
• better bootstrap and runtime-environment handling around local Python / uv / conda

Connectors and provider behavior

The connector/runtime bridge got another stability pass:

• Feishu / Telegram / WhatsApp fixes
• Weixin retry hardening
• MiniMax compatibility fixes
• improved recovery guidance around tool and interaction handling

Docs, README, and release-facing polish

This release also includes broad documentation and repository polish:

• README refresh
• updated startup, doctor, settings, and provider docs
• new local model backend guide
• improved maintainer docs for development and release checks
• npm package @researai/deepscientist@1.5.17 published

Testing and verification

Coverage improved across several layers:

• onboarding and launch-mode E2E tests
• launcher runtime tests
• daemon API tests
• doctor tests
• Codex compatibility tests
• config testing and shared-contract coverage

Why this release matters

v1.5.16 made DeepScientist easier to choose.

v1.5.17 makes it easier to trust after you choose it.

The biggest value in this release is not one single new screen. It is the cumulative reduction in launch friction, runtime ambiguity, recovery fragility, and local-environment surprises.

That is what makes the system feel more like a dependable research operating system instead of a promising but temperamental one.

Version

• npm package: @researai/deepscientist@1.5.17
• npm release: published
• git tag: v1.5.17