OpenSquilla 0.5.4

Overview

OpenSquilla 0.5.4 is a feature and maintenance release for the 0.5 stable line. It introduces a beta for versioned, single-file HTML editing in Electron Desktop, optional Runtime Packs with slimmer installers, per-chat model routing, and a more resilient C3 multi-model fusion path. It also improves chat continuity, Desktop startup and recovery, provider behavior, Skills, attachments, process lifecycle handling, and the Web interface.

Existing gateway configuration, chats, Agents, memory, and scheduled jobs stay in place. The Gateway applies additive database migrations automatically; no manual data transfer is required. Users upgrading from 0.5.3 should quit the running Desktop app or gateway, install 0.5.4 directly over the current installation, and restart OpenSquilla.

✨ What’s Improved

HTML document editing beta

0.5.4 introduces an early beta for editing single-file HTML attachments and deliverables in Electron Desktop. It provides Preview, Source, Versions, and Changes views, selected-element instructions, and Agent-assisted candidate edits. The workflow is intended for evaluation and may still require manual source review, retry, or revert.

• The beta is limited to single-file UTF-8 HTML. It does not cover project trees, Office or PDF documents, WYSIWYG editing, or collaborative editing.
• Candidate changes remain separate until the user chooses to commit. Review Preview and Changes before accepting an edit.
• An Agent-assisted attempt may return no change or need another instruction; committed changes can be reviewed by version and reverted as a whole.
• Native element selection requires the current Electron bridge. Browser clients and older Desktop bridges remain view-only for this beta.

Runtime Packs and slimmer Desktop installers

• Python, Node.js, and Windows Git Bash are now optional Runtime Packs managed from Settings → Security & Privacy → Sandbox → Runtimes. Installing a component enables it automatically.
• Downloads use an immutable catalog with GitHub and Beijing OSS source fallback, exact integrity checks, resumable transfers, cancellation, removal, and cache discard. System-installed runtimes are never modified or removed.
• Desktop installers still include the Gateway and Vue control console but no longer bundle developer runtimes, reducing installer size. The 0.5.3 bundled runtimes are intentionally not migrated; install the Runtime Packs you need after upgrading.

Model routing, Ensemble, and providers

• Each chat can keep its own Direct, Router, or Ensemble strategy. The global strategy remains the default for new chats, and existing chats adopt the current global strategy atomically on first use.
• C3 can use the shared multi-model fusion plan with resilient fixed-model fallback, independent image routing, transactional tool attempts, and clearer setup and activity presentation.
• Fresh and managed TokenRhythm configurations use DeepSeek V4 Flash 0731 for C0, DeepSeek V4 Pro 0813 for Direct and C1, Kimi K2.7 Code for C2, and GLM 5.2 B5 fusion for C3. Existing custom inline tiers are not migrated.
• Qwen prompt caching, Zhipu reasoning endpoint matching, Gemini CSV schemas, generic custom pricing, routed cost breakdowns, reasoning-only retries, and Ensemble usage and fallback behavior are more reliable.

Chats, tasks, and attachments

• Web chat confirms durable turn saves without delaying the answer or disabling input. Activity ordering, router panels, steering boundaries, task ownership, clocks, pending input, and scroll position recover more consistently across reconnects and session switches.
• Stop acknowledges promptly for provider and ordinary tool work while letting in-flight filesystem mutations settle safely before the terminal turn is published.
• Large attachments use the complete request capacity during routing. Uploaded images remain available to vision-capable models and are also materialized for workspace tools.
• Session history pagination, first-query session lookup, transcript reads, prompt-cache continuity, slash-command input, Composer paste behavior, and repeated-output handling have been hardened.

Desktop, Web, and platform reliability

• Desktop startup is decoupled from Gateway readiness and now reports monotonic milestones. Recovery starts faster, macOS Keychain failures have a guided retry path, and Windows process-tree helpers and installer progress are more reliable.
• Settings are organized into ten stable destinations, including combined Security & Privacy controls and a first-level Memory page. Existing Settings deep links continue through compatibility aliases.
• Sidebar interactions, long-session scrolling, Workbench resizing, activity details, usage expansion, automation empty states, memory import, and global controls are more consistent.
• Windows Safe execution, process-tree cancellation, Gateway shutdown, Skill-catalog digest verification, and CLI error exits now fail more predictably across supported platforms.

Downloads

Recommended desktop downloads:

• macOS desktop installer: OpenSquilla-0.5.4-mac-arm64.dmg
• macOS desktop zip: OpenSquilla-0.5.4-mac-arm64.zip
• Windows desktop installer: OpenSquilla-0.5.4-win-x64.exe

Users in Mainland China can use the stable direct installer links on the Alibaba Cloud OSS mirror:

• macOS Apple Silicon: https://opensquilla-releases.oss-cn-beijing.aliyuncs.com/releases/latest/OpenSquilla-mac-arm64.dmg
• Windows x64: https://opensquilla-releases.oss-cn-beijing.aliyuncs.com/releases/latest/OpenSquilla-win-x64.exe

Each alias is replaced only after the published release passes checksum verification. Versioned OSS and GitHub Release files remain available for pinned downloads.

The Windows desktop installer is currently unsigned. See the code signing policy before installation.

Terminal and automation downloads:

• Python wheel: opensquilla-0.5.4-py3-none-any.whl
• Checksums: SHA256SUMS

Updater metadata:

• latest-mac.yml
• latest.yml
• *.blockmap

No Windows Portable assets are published for 0.5.4. Existing 0.4.x Portable downloads remain on their original release pages as legacy sources; do not expect a 0.5.4 Portable zip or a Portable /releases/latest/download/ alias.

Privacy and third-party attribution are documented in PRIVACY.md and THIRD_PARTY_NOTICES.md.

Container users can pull the multi-architecture gateway image:

docker pull ghcr.io/opensquilla/opensquilla:v0.5.4

The versioned image supports linux/amd64 and linux/arm64. The moving latest tag follows the most recently verified release tag.

Upgrading from 0.5.3

Quit the running Desktop app and gateway before upgrading. Back up the active profile first if you may need to recover or roll back.

Install 0.5.4 directly over 0.5.3. Existing configuration, chats, Agents, memory, and scheduled tasks remain in the active profile. Additive database migrations run automatically when the Gateway starts.

The 0.5.4 Desktop app uses optional Runtime Packs instead of the developer runtimes bundled in 0.5.3. Those old bundled runtimes are not copied into the new application. If a task needs managed Python, Node.js, or Git Bash, install the corresponding Runtime Pack from Sandbox settings after the upgrade.

Existing chats keep working with older clients. Their per-chat routing mode is seeded from the current global strategy when first used by 0.5.4. New routing fields and commit receipts are additive, so clients that do not understand them may continue through their existing behavior. The HTML editing beta requires the complete current Electron bridge for native element selection; older or browser-only clients remain view-only for that capability.

[!IMPORTANT] On Windows, users coming from RC3 or an older pre-Preview-4 build must not uninstall that build first: older uninstallers may delete %APPDATA%\OpenSquilla. Back up that directory, then install 0.5.4 directly over the existing installation. Preview 4, 0.5.0, 0.5.1, 0.5.2, 0.5.3, and 0.5.4 installers preserve profile data during a normal uninstall.

On macOS, drag the new app into Applications, eject the DMG, and open the Applications copy.

CLI users can reinstall the published wheel over the current tool environment:

uv tool install --python 3.12 --force --reinstall-package opensquilla \
  "opensquilla[recommended] @ https://github.com/opensquilla/opensquilla/releases/download/v0.5.4/opensquilla-0.5.4-py3-none-any.whl"

Non-user-initiated network observability can be disabled before startup with OPENSQUILLA_PRIVACY_DISABLE_NETWORK_OBSERVABILITY=true or:

[privacy]
disable_network_observability = true

The compatibility variables OPENSQUILLA_TELEMETRY_DISABLED=true and OPENSQUILLA_UPDATE_CHECK_DISABLED=true remain honored.

Acknowledgements

Thanks to the human contributors whose work is newly present in 0.5.4:

• @AmirF194 for tightening Zhipu reasoning behavior to official API endpoints.
• @Kiuyor for restoring pasted Composer input after stale IME composition state.
• @Liu-RK for improving public release repository hygiene.
• @LiuXinchen1997 for the tier-level routing foundation used by resilient C3 fusion.
• @Sanjays2402 for finding existing sessions on the first search query.
• @ab2ence for C3 fusion and Ensemble fallback, provider-state isolation, Qwen prompt caching, usage accuracy, and sidebar refinements.
• @freeaccount-create for Gemini-safe CSV tool schemas.
• @jiaoqingrui for clearer Ensemble trace token labeling.
• @kriptoburak for Skill catalog-path digest verification.
• @lifelmy for preserving routed model cost breakdowns in the CLI.
• @lihongguang-0014 for extensive work on chat continuity, steering, attachments, Desktop startup, process lifecycle, session recovery, provider handling, and CLI reliability.
• @openvictory for publishing the technical report PDFs and making them discoverable.
• @shixi-li for safer Ensemble timeout fallback.
• @xfjsssq for allowing unknown slash-prefixed text to be sent as an ordinary message.

See CONTRIBUTORS.md for the release attribution ledger and pull-request evidence.