#133 - P1 — migrate CLI and desktop surfaces onto the daemon client with reconnect and session continuity - nsaspy/zara

lost-rob0t commented

2026-08-21 23:42:15 +00:00

(Migrated from github.com)

Parent epic: #127
Depends on: #129, #130, #131
Voice path additionally depends on: #132
Research: docs/research/001-daemon-zeromq-voice-service.md

Goal

Make Zara's supported user-facing surfaces consume one reusable daemon client library rather than starting duplicate assistant runtimes, while preserving an explicit standalone fallback during migration.

CLI behavior

Define and implement:

zara --connect <endpoint> ...
zara --standalone ...
zara ...                 # daemon-capable default after parity gate

Expected daemon-capable default flow when enabled:

resolve configured endpoint;
load client identity/server pin;
perform bounded connect + hello handshake;
select/resume the correct principal session/conversation;
execute through the shared daemon client;
surface a clear disconnected/auth/protocol error when unavailable;
use standalone fallback only according to an explicit configured policy.

Never silently start a second mic-owning runtime when another daemon may already own the assistant service.

Desktop integration

desktop Quick Copilot/Full Chat continue using existing conversation models and runtime events;
replace in-process runtime ownership with an adapter backed by the shared daemon client library;
do not create desktop-specific wire message types;
keep Qt main thread free of blocking ZeroMQ/provider/Prolog/audio work;
desktop tray shows connected/authenticating/reconnecting/degraded/disconnected state;
existing tool approval/context/voice controls map to canonical daemon commands/events.

Reconnect/session continuity

bounded exponential reconnect/backoff;
reconnect does not duplicate submitted side effects;
durable conversation survives daemon/client restart;
client may request session.resume where the negotiated protocol supports it;
in-flight audio/model turn is not falsely represented as resumed unless daemon explicitly confirms it;
stale events from an old connection/session cannot mutate the active conversation;
explicit user-facing distinction between transport reconnect and conversation continuity.

Identity UX

client/device key enrollment/configuration is shared across CLI/desktop library boundaries;
selecting another user/principal requires actual credentials/key material, not editing a user_id string;
diagnostics show safe principal/device/session identifiers without private keys/secrets.

Background behavior

daemon remains alive when normal desktop windows close;
client can disconnect without killing daemon runtime unless explicitly authorized to request daemon shutdown;
wake/background voice behavior uses the local client audio edge from #132;
daemon administrative shutdown/restart is a separately authorized action.

Tests

CLI text turn through daemon;
explicit standalone mode remains functional during migration;
missing daemon and configured fallback policies;
auth/protocol mismatch rendering;
desktop adapter receives the same event semantics as current RuntimeHost-backed UI;
repeated reconnect does not duplicate messages/tool side effects;
daemon restart preserves durable conversation;
stale old-session events ignored;
two clients for one principal and two distinct principals behave according to defined session policy;
closing desktop leaves daemon alive;
client disconnect releases audio/device resources;
focused client migration script plus full repo/Nix gate.

Acceptance

CLI and desktop can use the same authenticated daemon/client service boundary with reliable reconnect and durable conversation continuity. No supported client surface needs a private parallel provider/Prolog/memory runtime.

Non-goals

no removal of standalone mode until #134 proves parity;
no separate Qt-specific networking protocol;
no implicit user impersonation based on a string/flag;
no client authority to shut down the daemon unless explicitly granted.

Parent epic: #127 Depends on: #129, #130, #131 Voice path additionally depends on: #132 Research: `docs/research/001-daemon-zeromq-voice-service.md` ## Goal Make Zara's supported user-facing surfaces consume one reusable daemon client library rather than starting duplicate assistant runtimes, while preserving an explicit standalone fallback during migration. ## CLI behavior Define and implement: ```text zara --connect <endpoint> ... zara --standalone ... zara ... # daemon-capable default after parity gate ``` Expected daemon-capable default flow when enabled: 1. resolve configured endpoint; 2. load client identity/server pin; 3. perform bounded connect + `hello` handshake; 4. select/resume the correct principal session/conversation; 5. execute through the shared daemon client; 6. surface a clear disconnected/auth/protocol error when unavailable; 7. use standalone fallback only according to an explicit configured policy. Never silently start a second mic-owning runtime when another daemon may already own the assistant service. ## Desktop integration - desktop Quick Copilot/Full Chat continue using existing conversation models and runtime events; - replace in-process runtime ownership with an adapter backed by the shared daemon client library; - do not create desktop-specific wire message types; - keep Qt main thread free of blocking ZeroMQ/provider/Prolog/audio work; - desktop tray shows connected/authenticating/reconnecting/degraded/disconnected state; - existing tool approval/context/voice controls map to canonical daemon commands/events. ## Reconnect/session continuity - bounded exponential reconnect/backoff; - reconnect does not duplicate submitted side effects; - durable conversation survives daemon/client restart; - client may request `session.resume` where the negotiated protocol supports it; - in-flight audio/model turn is not falsely represented as resumed unless daemon explicitly confirms it; - stale events from an old connection/session cannot mutate the active conversation; - explicit user-facing distinction between transport reconnect and conversation continuity. ## Identity UX - client/device key enrollment/configuration is shared across CLI/desktop library boundaries; - selecting another user/principal requires actual credentials/key material, not editing a `user_id` string; - diagnostics show safe principal/device/session identifiers without private keys/secrets. ## Background behavior - daemon remains alive when normal desktop windows close; - client can disconnect without killing daemon runtime unless explicitly authorized to request daemon shutdown; - wake/background voice behavior uses the local client audio edge from #132; - daemon administrative shutdown/restart is a separately authorized action. ## Tests - CLI text turn through daemon; - explicit standalone mode remains functional during migration; - missing daemon and configured fallback policies; - auth/protocol mismatch rendering; - desktop adapter receives the same event semantics as current RuntimeHost-backed UI; - repeated reconnect does not duplicate messages/tool side effects; - daemon restart preserves durable conversation; - stale old-session events ignored; - two clients for one principal and two distinct principals behave according to defined session policy; - closing desktop leaves daemon alive; - client disconnect releases audio/device resources; - focused client migration script plus full repo/Nix gate. ## Acceptance CLI and desktop can use the same authenticated daemon/client service boundary with reliable reconnect and durable conversation continuity. No supported client surface needs a private parallel provider/Prolog/memory runtime. ## Non-goals - no removal of standalone mode until #134 proves parity; - no separate Qt-specific networking protocol; - no implicit user impersonation based on a string/flag; - no client authority to shut down the daemon unless explicitly granted.

nsaspy referenced this issue

2026-08-28 03:31:13 +00:00

docs: research Zara daemon and ZeroMQ voice service #135

nsaspy referenced this issue

2026-08-28 03:31:16 +00:00

RAGE #132: record final gate and merge evidence #187

nsaspy referenced this issue from a pull request that will close it,

2026-08-28 03:31:16 +00:00

RAGE #133: migrate CLI and desktop onto ZaraClient #188

nsaspy referenced this issue

2026-08-28 03:31:16 +00:00

RAGE #133: record merge closeout #189

nsaspy referenced this issue

2026-08-29 10:40:44 +00:00

[ORDER] ZARA-000 — Repository repair and real-time voice roadmap #1

nsaspy referenced this issue

2026-09-02 17:27:43 +00:00

P1 — migrate the zara wake listener onto the daemon ZARA/1 voice client with principal-scoped memory #227

nsaspy referenced this issue

2026-09-04 14:39:03 +00:00

P1 — RAGE research the post-client-split semantic intent architecture and freeze an IntentFrame contract #154

nsaspy referenced this issue

2026-09-04 14:39:04 +00:00

P2 — RAGE Android Prolog/ZeroMQ/NDK/WASM feasibility bakeoff and architecture decision #170

nsaspy referenced this issue

2026-09-04 14:39:04 +00:00

P2 — add the in-repo Android project skeleton with reproducible Gradle/SDK/NDK CI #171

nsaspy referenced this issue

2026-09-04 14:39:04 +00:00

P0 research gate — Samsung assistant role and Android integration architecture #195