Resources01 · Changelog

CHANGELOG / RELEASE TIMELINE

Every version explains exactly what changed this time

Organize changes by date, version, and affected area so readers see what was fixed before deciding whether to inspect implementation details

  1. v0.10.4

    Fix delayed archival after long-running tasks finish

    PATCH RELEASE

    This patch aligns task completion, final replies, and history-list updates so completed sessions no longer remain marked as running

    • AGENT

      Terminal state now comes only from durable commits; the interface no longer infers completion from the final message

    • UI

      The session list refreshes as soon as the terminal projection arrives while retaining tool and approval records for the turn

    • RECOVERY

      After restart, the app restores from the same commit sequence instead of creating a second state copy

  2. v0.10.3

    Release composable IM and Agent client entry points

    MINOR RELEASE

    The same desktop client can enable IM or Agent independently, or combine them across an explicit data-exchange boundary

    • CLIENT

      The app composition root creates one supervised AgentService and gives the visible interface a typed handle

    • IM

      Messages, groups, and collaboration remain independent; they receive an Agent artifact copy only after explicit sharing

    • DEVTOOLS

      Developer tools observe commits, views, and receipts read-only and do not own business writes

  3. v0.10.2

    Complete tool-call receipt, cancellation, and recovery paths

    PATCH RELEASE

    Tool start, result, failure, and unknown states now share one replayable path, preventing dangerous actions from repeating after restart

    • TOOLS

      Each call uses a stable identifier to connect its start, receipt, and final state

    • CANCEL

      Cancellation enters a controlled lifecycle instead of being simulated by hiding UI or dropping messages

    • REPLAY

      Non-repeatable actions remain unknown when terminal state is missing and are never replayed automatically

  4. v0.10.1

    Tighten the data boundary between local content and the remote control plane

    SECURITY RELEASE

    Regular Agent content stays in local storage; remote services handle only accounts, catalogs, policy, billing, and content-free control state

    • PRIVACY

      Prompts, reasoning, tool arguments, outputs, and file content do not enter the regular server synchronization path

    • IDENTITY

      Missing or conflicting identity fails closed and is never inferred from cache, prior output, or defaults

    • AUDIT

      Documentation, source, compilation, app runtime, and production delivery are recorded separately; static checks are never presented as runtime acceptance