Lataa AgentsDock 1.0.11

AgentsDock 1.0.11
This release promotes the desktop/server functionality shipped in
1.0.11-beta.12, source ab95ad3284f91997c2b249ac413b155f99c09ce6.
It does not incorporate later changes from main. The desktop app, npm runtime,
short CLI and signed legacy server bridge share version 1.0.11.
Changes since stable 1.0.10
- Add the Gemini API backend on desktop and server, using the supported Gemini
CLI runtime. Google/CLI sign-in is not included.
- Improve large-history loading, repair-record visibility and provider-session
recovery. Fix Claude running-chat forks with fractional-second timestamps.
- Add terminal pairing QR output and improve server address selection and
connection recovery.
- Group desktop chats into Unread and Running sections while retaining saved
folders and pins.
- Improve CLI setup and managed server lifecycle behavior; expose Codex goal
status in server summaries for compatible mobile clients.
- Extend privacy-limited desktop and shared-chat usage reporting.
Validation and distribution
The desktop app is build 1268. macOS uses Developer ID signing and Apple
notarization. Windows uses the existing unsigned distribution policy and may
show security warnings. Linux x64 and ARM64 packages are included.
- Four-platform package verification
and paired CLI native checks passed.
- Eleven Mac upgrade/recovery journeys
completed, including stable 1.0.10 and beta.12 upgrades, legacy bridge updates,
offline-server reconciliation, shared updates across two clients and retained
update-channel preferences. Two Apple network failures were retried with the
unchanged signed packages.
- Linux rollback and retry
passed with both supported legacy installation-root permission modes.
- Separate local tests with genuine Codex and Claude conversations retained
original events and native session IDs, contextual follow-ups, an attachment,
an unsent draft and settings. Replacing the app while the server kept running
retained a pending Claude approval and executed its queued follow-up once.
These checks cover specific scenarios. The local populated-history test used
an idle server upgrade through the exact signed package installer, followed by
app replacement and cold start. Hosted automatic-updater fixtures used synthetic
history and retain their original blocked provider-history checks. Server
replacement during active/queued work, logout/reboot survival, normal app quit,
and the native Windows updater remain outside this validation. The old local
test app required forced termination. See the
validation record.
Later main fixes, including Codex model-switch compaction recovery and subsequent
mobile queue recovery, are outside this frozen source. Mobile builds are separate.