Skip to main content

DesireCore v10.0.89

Release Date: 2026-07-17

New Features​

  • Per-agent file security toggle: File access protection now defaults to not blocking. You can enable workspace directory restrictions per agent in agent configuration, avoiding excessive disruption to daily operations.
  • Checkpoint governance panel: A new “Rollback & Checkpoints” management page has been added under Settings → Data & Privacy. You can view checkpoint usage, configure retention periods, safely purge archived old data with one click, and control history recording toggles for each operation type.

Fixes​

  • Fixed an issue where approval cards for operations like file editing lacked a progress bar and could not auto-decide when delegating tasks or creating sub-sessions, causing the workflow to hang permanently.
  • Fixed a critical issue on macOS where the system Keychain permission prompt caused the app to freeze on startup, leading to permanent local service connection errors and the agent list failing to load.
  • Fixed an issue where clicking the retry button in the sidebar agent list occasionally did nothing after a loading failure, and added a friendly “Auto-retrying…” prompt during automatic retries.
  • Fixed an issue where all requests with tool calls would fail with a 400 error when going through certain API gateways (e.g., new-api forwarding DeepSeek).
  • Fixed an issue where, within the same conversation turn, after the agent first added a workspace directory and then read/wrote files, the operation could fail due to incorrect tool execution order.
  • Fixed an issue where file read/write permissions were not updated in time or stale precise authorizations remained across multi-turn conversations, causing operations to be unexpectedly denied or allowed.
  • Fixed a cosmetic flaw on the agent profile page where some ordinary headings and description text were incorrectly rendered as tags.
  • Fixed a false alarm in the conversation rollback checkpoint preview where files written with relative paths were incorrectly reported as “not backed up.”
  • Fixed an issue in scenarios such as task delegation or follow-up conversations where multiple chat bubbles on the chat interface would stack and overlap, making content hard to distinguish.
  • Fixed a critical issue where, when a conversation retry was triggered by faults like network errors or context overflow, previously successful tool calls (e.g., file writes) could be re-executed, causing side effects.