nsaspy/zara
1
0
Fork 0
Code Issues 95 Pull requests 18 Projects Releases Packages Wiki Activity Actions

P2 — implement authenticated Android ZARA/1 client enrollment, reconnect and session continuity #173

New issue
Closed
opened 2026-08-22 21:55:31 +00:00 by lost-rob0t · 4 comments
lost-rob0t commented 2026-08-22 21:55:31 +00:00 (Migrated from github.com)
Copy link

Parent epic: #152
Depends on: #172, #159, #133

Goal

Implement the Android transport/client layer selected by #170 using the same authenticated ZARA/1 semantics as Linux clients.

Scope

  • client key generation/storage using researched Android keystore/file boundary;
  • server public-key pinning;
  • enrollment/rotation/revocation UX and typed failure states;
  • bounded connect + hello negotiation;
  • request/reply/event correlation;
  • session/conversation selection/resume;
  • bounded exponential reconnect;
  • stale connection/session events rejected;
  • action/capability negotiation support from #159;
  • safe diagnostics with no private keys/tokens.

Tests

Correct/wrong server pin, enrolled/unknown/revoked key, daemon unavailable/restart, network loss/reconnect, app/activity recreation, duplicate replies, stale old-session events, malformed/oversized frames, request timeout/cancel, two Android client fixtures and cross-principal isolation. Use deterministic local daemon fixtures; no external network.

Acceptance

Android can authenticate to zara-server, submit/receive ordinary typed turns/events and preserve durable conversation semantics across reconnect without owning a second server runtime.

Parent epic: #152 Depends on: #172, #159, #133 ## Goal Implement the Android transport/client layer selected by #170 using the same authenticated ZARA/1 semantics as Linux clients. ## Scope - client key generation/storage using researched Android keystore/file boundary; - server public-key pinning; - enrollment/rotation/revocation UX and typed failure states; - bounded connect + hello negotiation; - request/reply/event correlation; - session/conversation selection/resume; - bounded exponential reconnect; - stale connection/session events rejected; - action/capability negotiation support from #159; - safe diagnostics with no private keys/tokens. ## Tests Correct/wrong server pin, enrolled/unknown/revoked key, daemon unavailable/restart, network loss/reconnect, app/activity recreation, duplicate replies, stale old-session events, malformed/oversized frames, request timeout/cancel, two Android client fixtures and cross-principal isolation. Use deterministic local daemon fixtures; no external network. ## Acceptance Android can authenticate to `zara-server`, submit/receive ordinary typed turns/events and preserve durable conversation semantics across reconnect without owning a second server runtime.
nsaspy commented 2026-09-08 02:10:16 +00:00
Owner
Copy link

Dependency-prep research note for #173 (no production implementation while #133/#159 remain open): the #170 decision's phrase “Android Keystore-backed storage” needs a precise boundary.

JeroMQ 0.6.0 CURVE config requires the client long-term secret as raw 32-byte key material (or 40-char Z85) via ZMQ.Socket.setCurveSecretKey(byte[]). Android Keystore, by design, keeps AndroidKeyStore secret/private key material non-exportable and out of the application process. Therefore the CURVE private key itself cannot naively be generated as a non-exportable AndroidKeyStore key and then handed to JeroMQ.

Recommended #173 design:

  • Generate the actual CURVE keypair using the selected JeroMQ/CURVE implementation.
  • Generate a separate AES-256-GCM wrapping key in AndroidKeyStore (PURPOSE_ENCRYPT|PURPOSE_DECRYPT, GCM, no padding). Do not require per-use user authentication: the assistant/background reconnect path must be able to reconnect without a biometric prompt.
  • Immediately encrypt/wrap the raw CURVE secret with that Keystore AES key. Persist only {version, public_key, ciphertext, iv/tag} in app-private storage; keep the wrapped credential in noBackupFilesDir and/or explicit backup/data-extraction exclusions so stale device-bound ciphertext is not restored as if it were a portable credential.
  • On connect, unwrap only long enough to configure the JeroMQ socket; keep plaintext lifetime bounded and clear temporary byte arrays where the JeroMQ ownership/copy semantics permit. Never log/Z85-print the secret.
  • Store the server public-key pin as non-secret app-private state, but compare/fail closed before accepting a session.
  • Treat missing/deleted Keystore wrapping key, undecryptable ciphertext, or restored stale credential as a typed UNENROLLED/re-enrollment state, never as permission to create a replacement identity silently.
  • Rotation should be staged and rollback-safe: create+wrap the new client key, enroll/authorize its public key, atomically switch active credential only after server acceptance, then revoke/delete the old one. A crash mid-rotation must leave one known-good credential or an explicit recovery state.

Tests I want mapped into #173 before implementation: raw/Z85 secret absent from persisted files/logs/APK diagnostics; wrong/deleted wrapping key; pin mismatch; corrupt ciphertext/tag; process recreation; rotation crash boundaries; revocation; duplicate/stale sessions; backup/restore -> explicit re-enrollment; and two-client/cross-principal isolation already required by the issue.

Authoritative references checked 2026-09-05:

This keeps the selected #170 JeroMQ/CURVE architecture intact; it just makes “Keystore-backed” technically honest.

Dependency-prep research note for #173 (no production implementation while #133/#159 remain open): the #170 decision's phrase “Android Keystore-backed storage” needs a precise boundary. JeroMQ 0.6.0 CURVE config requires the client long-term secret as raw 32-byte key material (or 40-char Z85) via `ZMQ.Socket.setCurveSecretKey(byte[])`. Android Keystore, by design, keeps AndroidKeyStore secret/private key material non-exportable and out of the application process. Therefore the CURVE private key itself cannot naively be generated as a non-exportable AndroidKeyStore key and then handed to JeroMQ. Recommended #173 design: - Generate the actual CURVE keypair using the selected JeroMQ/CURVE implementation. - Generate a separate AES-256-GCM wrapping key in `AndroidKeyStore` (`PURPOSE_ENCRYPT|PURPOSE_DECRYPT`, GCM, no padding). Do not require per-use user authentication: the assistant/background reconnect path must be able to reconnect without a biometric prompt. - Immediately encrypt/wrap the raw CURVE secret with that Keystore AES key. Persist only `{version, public_key, ciphertext, iv/tag}` in app-private storage; keep the wrapped credential in `noBackupFilesDir` and/or explicit backup/data-extraction exclusions so stale device-bound ciphertext is not restored as if it were a portable credential. - On connect, unwrap only long enough to configure the JeroMQ socket; keep plaintext lifetime bounded and clear temporary byte arrays where the JeroMQ ownership/copy semantics permit. Never log/Z85-print the secret. - Store the server public-key pin as non-secret app-private state, but compare/fail closed before accepting a session. - Treat missing/deleted Keystore wrapping key, undecryptable ciphertext, or restored stale credential as a typed `UNENROLLED`/re-enrollment state, never as permission to create a replacement identity silently. - Rotation should be staged and rollback-safe: create+wrap the new client key, enroll/authorize its public key, atomically switch active credential only after server acceptance, then revoke/delete the old one. A crash mid-rotation must leave one known-good credential or an explicit recovery state. Tests I want mapped into #173 before implementation: raw/Z85 secret absent from persisted files/logs/APK diagnostics; wrong/deleted wrapping key; pin mismatch; corrupt ciphertext/tag; process recreation; rotation crash boundaries; revocation; duplicate/stale sessions; backup/restore -> explicit re-enrollment; and two-client/cross-principal isolation already required by the issue. Authoritative references checked 2026-09-05: - JeroMQ 0.6.0 `ZMQ.Socket.setCurveSecretKey(byte[])`: https://javadoc.io/static/org.zeromq/jeromq/0.6.0/org/zeromq/ZMQ.Socket.html - Android Keystore extraction model: https://developer.android.com/privacy-and-security/keystore - Android Keystore AES/GCM example/API: https://developer.android.com/reference/android/security/keystore/KeyGenParameterSpec - Backup/data-extraction controls: https://developer.android.com/identity/data/autobackup This keeps the selected #170 JeroMQ/CURVE architecture intact; it just makes “Keystore-backed” technically honest.
nsaspy commented 2026-09-08 02:10:17 +00:00
Owner
Copy link

Core handoff for Android #173:

  • PR #322 is merged on canonical master at ceb2e13951af518cbc29df2dafabdea022baad89, so the Android credential wrapping/server-pin substrate is now available.
  • Shared device action PR #321 is rebased onto that exact master at 3c00b9c5fabe436b297b8308389da1837a05669b. Its Android APK gate and both shared-mic lanes are green; Core full tests/Nix/package are still running, so this is not merge authority yet.
  • #321’s contract is the closed Android-neutral ZARA/1 plane: bounded open_uri/open_app availability plus session-bound device.action.request -> accepted -> result/error, explicit generated action_id, deadline rejection before enqueue, terminal cancel, and terminal-before-accepted fail-closed behavior. No payload principal/device authority and no shell/import/eval primitive.
  • Current master already has deterministic reconnect guarantees Android can rely on without inventing session.resume: stable request IDs do not duplicate side effects across reconnect, conflicting ID reuse fails closed, selected durable conversation is reopened after reconnect, and queued old-session events are discarded. A new hello gets a new application session; in-flight work is not falsely represented as resumed.
  • Production secure TCP/#329 remains in PR #331 and is under fresh fuzz/chaos + full-gate verification; do not assume that draft is merged yet.

Android can continue implementation against the merged #322 substrate and the existing reconnect/conversation contract, while treating #321/#331 as pending shared dependencies until provider-acknowledged exact-head merges.

Core handoff for Android #173: - PR #322 is merged on canonical `master` at `ceb2e13951af518cbc29df2dafabdea022baad89`, so the Android credential wrapping/server-pin substrate is now available. - Shared device action PR #321 is rebased onto that exact master at `3c00b9c5fabe436b297b8308389da1837a05669b`. Its Android APK gate and both shared-mic lanes are green; Core full tests/Nix/package are still running, so this is not merge authority yet. - #321’s contract is the closed Android-neutral ZARA/1 plane: bounded `open_uri`/`open_app` availability plus session-bound `device.action.request -> accepted -> result/error`, explicit generated `action_id`, deadline rejection before enqueue, terminal cancel, and terminal-before-accepted fail-closed behavior. No payload principal/device authority and no shell/import/eval primitive. - Current master already has deterministic reconnect guarantees Android can rely on without inventing `session.resume`: stable request IDs do not duplicate side effects across reconnect, conflicting ID reuse fails closed, selected durable conversation is reopened after reconnect, and queued old-session events are discarded. A new hello gets a new application session; in-flight work is not falsely represented as resumed. - Production secure TCP/#329 remains in PR #331 and is under fresh fuzz/chaos + full-gate verification; do not assume that draft is merged yet. Android can continue implementation against the merged #322 substrate and the existing reconnect/conversation contract, while treating #321/#331 as pending shared dependencies until provider-acknowledged exact-head merges.
nsaspy commented 2026-09-08 02:10:17 +00:00
Owner
Copy link

Core handoff update for Android #173:

  • Shared typed device capability/action lifecycle is now merged on canonical master via PR #336 at merge SHA eb6e9bac0a9fc13ca90b3779fe1d7271107d431e.
  • Exact pre-merge head 87ecf536c2347e6407155846a6c47bf8b7890e6e was fully green: full pytest, nix flake check, packaged build, Android APK/secret gate, Ubuntu shared-mic and Arch shared-mic.
  • Android may now rely on the generic closed ZARA/1 contract: capability.snapshot; session-bound device.action.request -> accepted -> result/error; server-generated action_id; deadline fail-before-enqueue; terminal cancel; stale-session rejection; no shell/import/eval authority.
  • Core security PR #331 remains draft/pending. Threat testing exposed and Core has patched a reconnect semantic bug there: a fresh authenticated hello is now rate-limited + connection-limited but no longer consumes the concurrent runtime slot held by an old in-flight turn. This directly prevents an abandoned route/turn from deadlocking Android reconnect. Treat this behavior as pending until #331 reaches exact-head green and merges.

Canonical Core master after #336: eb6e9bac0a9fc13ca90b3779fe1d7271107d431e.

Core handoff update for Android #173: - Shared typed device capability/action lifecycle is now **merged on canonical `master`** via PR #336 at merge SHA `eb6e9bac0a9fc13ca90b3779fe1d7271107d431e`. - Exact pre-merge head `87ecf536c2347e6407155846a6c47bf8b7890e6e` was fully green: full pytest, `nix flake check`, packaged build, Android APK/secret gate, Ubuntu shared-mic and Arch shared-mic. - Android may now rely on the generic closed ZARA/1 contract: `capability.snapshot`; session-bound `device.action.request -> accepted -> result/error`; server-generated `action_id`; deadline fail-before-enqueue; terminal cancel; stale-session rejection; no shell/import/eval authority. - Core security PR #331 remains draft/pending. Threat testing exposed and Core has patched a reconnect semantic bug there: a fresh authenticated `hello` is now rate-limited + connection-limited but no longer consumes the concurrent runtime slot held by an old in-flight turn. This directly prevents an abandoned route/turn from deadlocking Android reconnect. Treat this behavior as pending until #331 reaches exact-head green and merges. Canonical Core master after #336: `eb6e9bac0a9fc13ca90b3779fe1d7271107d431e`.
nsaspy commented 2026-09-08 02:10:17 +00:00
Owner
Copy link

Core handoff: PR #331 is now merged to canonical master as 7cb047a390644c7da96cfb4620bfb8d569450fff. This removes the stock-daemon P0 secure-listener blocker: production TCP now uses the canonical authenticated CURVE/ZAP gateway with durable server identity, enrolled-client registry, live owner-local enroll/revoke/list authority, immediate revocation, and fail-closed state divergence handling. Exact head fabea77133914976bd0da2373ad9392d42a46a1e passed CI run #1138: full tests, nix flake check, packaged Zara build, Android skeleton/native-Prolog/debug-APK/secret gate, and Arch+Ubuntu shared-mic jobs. Android can now run its real stock-daemon hello/text-turn interoperability gate against merge 7cb047a….

Core handoff: PR #331 is now merged to canonical `master` as `7cb047a390644c7da96cfb4620bfb8d569450fff`. This removes the stock-daemon P0 secure-listener blocker: production TCP now uses the canonical authenticated CURVE/ZAP gateway with durable server identity, enrolled-client registry, live owner-local enroll/revoke/list authority, immediate revocation, and fail-closed state divergence handling. Exact head `fabea77133914976bd0da2373ad9392d42a46a1e` passed CI run #1138: full tests, `nix flake check`, packaged Zara build, Android skeleton/native-Prolog/debug-APK/secret gate, and Arch+Ubuntu shared-mic jobs. Android can now run its real stock-daemon hello/text-turn interoperability gate against merge `7cb047a…`.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
agent/pi-coder-plugin-2026-09-17
fix/android-remote-listener
ui/chat-message-bubbles
release/v0.1.1-alpha-20260908
fix/default-daemon-endpoint-20260908
ui/650-outrun-shell
fix/400-plugin-capability-composition
fix/tts-idle-cpu-spin
design/android-canonical-reference-2026-09-07
fixtures/voice-recordings
rage/core/388-tool-cancellation-r18
rage/core/388-tool-cancellation-r1
release/v0.1.0-alpha
rage/android/175-terminal-transcript-fence-r4
rage/core/324-expanded-history-sidebar-r2
rage/android/175-terminal-transcript-fence-r3
rage/android/175-focus-release-retry-r2
rage/android/175-focus-release-retry
ci/desktop-idle-cpu-budget
rage/android/175-terminal-transcript-fence-r2
rage/android/175-route-stop-retry-r3
rage/575-transient-send-backpressure-r3
rage/575-transient-send-backpressure-r2
rage/android/175-terminal-transcript-fence
rage/android/175-route-stop-retry-r2
rage/android/175-sink-self-close-r2
rage/android/175-route-stop-retry
rage/android/175-sink-self-close
rage/android/175-audio-focus-sync-loss-r2
rage/android/175-stock-voice-interop-r3
rage/android/175-stock-voice-interop-r2
rage/android/175-audio-focus-sync-loss
rage/android/175-recover-stack-current-4
rage/android/175-stock-voice-interop-r1
rage/android/175-recover-stack-current-2
rage/587-vulkan-current-master-r2
rage/587-dictation-vulkan-current2
rage/575-transient-send-backpressure-r1
tmp-do-not-use-587
tmp-do-not-use-587-2
tmp-do-not-use-587-3
tmp-do-not-use-587-4
rage/587-dictation-vulkan-current2-tree
fix/dictation-ggml-vulkan-rage587
rage/android-campaign-batch-20260906
rage/587-dictation-ggml-vulkan-current
rage/388-toolnode-forwarding-r17-current2
rage/587-dictation-ggml-vulkan-r1
rage/388-toolnode-forwarding-r17-current
rage/575-gateway-send-diagnostics-current
rage/178-device-action-json-depth-r7
rage/175-recorder-failure-precedence-r8
rage/175-terminal-capture-cleanup-r8
rage/175-playback-write-failure-cleanup-r8
rage/575-gateway-send-diagnostics
rage/388-toolnode-forwarding-r17
rage/575-stock-interop-diagnostics-r2
fix/dictate-whisper-cpp-vulkan
rage/575-stock-interop-diagnostics-r1
rage/324-expanded-history-sidebar-r1
rage/178-device-action-json-depth-r6
rage/388-plugin-cancellation-r16
rage/175-recorder-failure-precedence-r7
rage/175-terminal-capture-cleanup-r7
rage/175-playback-write-failure-cleanup-r7
rage/324-native-chrome-r1
rage/175-recorder-failure-precedence-r6
rage/175-terminal-capture-cleanup-r6
rage/175-playback-write-failure-cleanup-r6
rage/324-independent-geometry-r2
rage/175-close-resource-precedence
rage/178-device-action-json-depth-r5
rage/175-recorder-failure-precedence-r5
rage/175-terminal-capture-cleanup-r5
rage/175-playback-write-failure-cleanup-r5
rage/324-independent-geometry-r1
rage/324-screenshot-provenance-r1
rage/324-history-parity-r1
rage/178-device-action-json-depth-r4
rage/175-preserve-recorder-primary-failure-r2
rage/175-capture-terminal-failure-cleanup-r3
rage/175-playback-write-failure-cleanup-r4
rage/324-screenshot-ci-r1
rage/324-unified-copilot-r4
rage/175-capture-terminal-failure-cleanup-r2
rage/175-playback-write-failure-cleanup-r3
rage/324-unified-copilot-r3
rage/175-preserve-recorder-primary-failure
rage/175-capture-terminal-failure-cleanup
rage/178-device-action-json-depth-r3
rage/175-playback-write-failure-cleanup-r2
rage/178-voice-stream-json-depth-r5
rage/160-semantic-first-runtime-r2
rage/175-playback-write-failure-cleanup
rage/178-voice-stream-json-depth-r4
rage/324-unified-copilot-r2
rage/178-device-action-json-depth-r2
rage/178-voice-json-depth-r3
rage/178-voice-ack-json-depth-r3
rage/160-semantic-first-runtime
rage/492-device-action-replay-r6
rage/178-device-action-json-depth
rage/178-voice-json-depth-r2
rage/178-voice-ack-json-depth-r2
rage/178-voice-json-depth-bound
rage/178-voice-ack-json-depth
rage/178-voice-hello-json-depth
rage/178-device-json-depth-bound
rage/178-capability-json-depth-bound
rage/178-android-daemon-restart-stale-turn-r2
rage/492-device-action-replay-r5
rage/492-device-action-replay-r4
rage/178-android-daemon-restart-stale-turn-r1
rage/178-android-json-depth-bound-r2
rage/178-android-json-depth-bound-r1
rage/203-android-playback-session-invalidation-r3
rage/492-device-action-replay-r3
rage/178-android-audio-payload-bound-r4
rage/203-android-playback-session-invalidation-r2
rage/178-android-audio-payload-bound-r3
rage/492-device-action-replay-r2
rage/203-android-ui-close-runtime-ownership-r3
rage/203-android-playback-session-invalidation
rage/178-android-audio-payload-bound-r2
rage/203-android-ui-close-runtime-ownership-r2
rage/178-android-uri-intent-abuse-r4
rage/178-android-audio-payload-bound
rage/203-android-ui-close-runtime-ownership
rage/492-device-action-replay-r1
rage/178-android-uri-intent-abuse-r3
rage/178-android-no-raw-logging-r5
rage/492-device-action-replay-horizon
rage/218-normalizer-config-r4
rage/178-android-uri-intent-abuse-r2
rage/178-android-no-raw-logging-r4
rage/178-android-uri-intent-abuse-r1
rage/218-normalizer-config-r3
rage/178-android-no-raw-logging-r3
rage/178-android-prolog-lifecycle-r3
rage/178-android-no-raw-logging-r2
rage/178-android-prolog-lifecycle-r2
rage/178-android-principal-target-abuse-r2
rage/178-android-no-raw-logging-r1
rage/178-android-prolog-lifecycle-r1
rage/178-android-principal-target-abuse-r1
rage/178-android-device-action-replay-r4
rage/178-android-device-action-replay-r3
rage/178-android-capability-revocation-r3
rage/218-normalizer-config-r2
rage/178-android-trealla-result-overflow-r1
rage/178-android-device-action-replay-r2
rage/178-android-capability-revocation-r2
rage/178-android-auth-revocation-r2
rage/178-android-device-action-replay-r1
rage/178-android-capability-revocation-r1
rage/178-android-auth-revocation-r1
rage/178-android-reconnect-storm-r3
rage/218-normalizer-config-r1
rage/218-normalizer-config-status-r1
rage/324-unified-copilot-r1
rage/217-s1-mini-normalizer-r4
rage/178-android-reconnect-storm-r2
rage/178-reconnect-storm-red-proof
rage/217-s1-mini-normalizer-r3
rage/178-android-release-matrix-r1
rage/217-s1-mini-normalizer-r2
rage/203-android-recorder-failure-diagnostics-r3
rage/217-s1-mini-normalizer-r1
rage/203-android-assistant-role-loss-wiring-r3
rage/216-transcript-normalization-contract-r2
rage/203-android-recorder-failure-diagnostics-r2
rage/203-android-assistant-role-loss-wiring-r2
rage/216-transcript-normalization-contract-r1
rage/203-android-reconnect-scheduler-failure-r2
rage/388-plugin-tool-cancellation-r15
rage/203-android-reconnect-scheduler-failure
rage/203-android-voice-session-invalidation-r4
rage/203-android-voice-session-invalidation-r3
rage/203-android-ui-error-redaction-r3
rage/388-plugin-tool-cancellation-r14
rage/388-plugin-tool-cancellation-r13
rage/400-plugin-capability-composition-r1
rage/203-android-ui-error-redaction-r2
rage/388-plugin-tool-cancellation-r12
rage/203-android-audio-route-rollback-failure-r2
rage/325-atomic-durable-message-append
rage/203-android-state-store-temp-isolation-r2
rage/388-plugin-tool-cancellation-r11
rage/388-plugin-tool-cancellation-r10
rage/203-android-audio-route-rollback-failure
rage/203-android-recorder-failure-diagnostics
rage/203-android-voice-runtime-invalidation-r2
rage/203-android-assistant-role-loss-wiring
rage/203-android-voice-session-invalidation-r2
rage/203-android-ui-error-redaction
rage/388-plugin-tool-cancellation-r9
rage/203-android-state-store-temp-isolation
rage/203-android-connection-error-redaction
rage/203-android-assistant-role-loss-r3
rage/388-plugin-tool-cancellation-r8
rage/203-android-voice-runtime-invalidation-primitives
rage/203-android-assistant-role-loss-r2
rage/203-android-voice-diagnostic-redaction-r2
rage/388-plugin-tool-cancellation-r7
rage/203-android-assistant-role-loss
rage/203-android-voice-session-invalidation
rage/203-android-voice-diagnostic-redaction
rage/174-android-open-app-aliases
rage/388-plugin-tool-cancellation-r6
rage/203-android-assistant-shutdown-fence
rage/388-plugin-tool-cancellation-r5
rage/29-streaming-tts-provider-recovery-r10
rage/203-android-mic-permission-lifecycle
rage/203-android-audio-route-lifecycle
rage/175-android-audio-focus-lifecycle
rage/174-android-device-capabilities
rage/29-streaming-tts-provider-recovery-r9
rage/388-plugin-tool-cancellation-r4
rage/388-plugin-tool-cancellation-r3
rage/29-streaming-tts-provider-recovery-r8
rage/326-desktop-toggle
rage/388-plugin-tool-cancellation-r2
rage/388-plugin-tool-cancellation
rage/29-streaming-tts-current-r7
rage/29-streaming-tts-current-r6
rage/371-plugin-approval-current
rage/29-streaming-tts-current-r5
rage/371-plugin-approval-contract
rage/371-plugin-approval-red
rage/29-streaming-tts-current-r4
rage/196-ui-closed-runtime
rage/196-android-assistant-role
rage/29-streaming-tts-current-r3
rage/175-android-barge-in
rage/175-android-streamed-voice
rage/175-android-manual-voice
rage/29-streaming-tts-current-r2
rage/29-streaming-tts-current
rage/327-bounded-target-edit-distance-recovery-r2
rage/348-dash-prefixed-z85-cli-r2
rage/197-compose-first-usable
rage/348-dash-prefixed-z85-cli
rage/173-android-client-continuity
rage/327-bounded-target-edit-distance-recovery
rage/329-production-secure-listener
rage/329-merge-probe
rage/159-zara1-device-actions-current
docs/refresh-20260905
rage/159-zara1-device-actions-recovery
rage/324-unified-copilot
rage/173-android-auth
rage/327-bounded-target-edit-distance
research/unified-copilot-20260905
rage/133-desktop-daemon-default-regression
rage/133-daemon-default-regression
rage/13-open-app-allowlist-regression
rage/165-user-command-runtime
rage/315-route-backpressure-test-contract
rage/164-user-command-authoring
rage/163-user-command-compiler
rage/162-user-command-persistence
rage/309-prolog-config-recovery
docs/260-customization-wiki
rage/260-customization-diagnostics
rage/159-zara1-device-actions
rage/260-agent-loop-backend-registry
rage/260-backend-registry
rage/260-service-plugin-advice
backup/rage-260-service-plugin-advice-pre-android-merge-20260903
rage/android-172-cross-runtime-parity
rage/zara-004-config-durability
rage/260-prolog-command-advice
feature/long-horizon-tasks
rage/264-config-delta
rage/264-host-delta
rage/264-config-host-delta
rage/rebase-264-long-horizon-tasks
backup/rage-260-prolog-command-advice-pre-rebase-20260903
rage/android-172-resolver-parity
rage/260-python-user-hooks
rage/260-agent-loop-integration
rage/android-172-asset-staging
rage/android-172-native-adapter
rage/260-python-hooks-advice
rage/android-172-jni-bridge
rage/android-172-trealla-runtime
rage/260-hooks-prolog-config
rage/android-172-fixture-runner
fork/prolog-rlm-agentic-runtime
rage/android-172-normalized-results
rage/android-172-assets-v2
rage/core-246-todo-toggle-current
rage/android-172-assets
rage/core-246-todo-toggle-refresh
rage/android-172-portable-prolog-refresh
feature/agent-mode-core
rage/recover-259-run10
rage/android-172-portable-prolog
docs/244-merge-evidence
backup/feature-long-horizon-tasks-pre-rebase-20260902
feat/zara-031-context-management
docs/250-merge-evidence
rage/250-amd-stt-device-routing
rage/159-zara1-capability-advertisement
feat/unified-agent-tui
fix/discord-tools-bash
rage/158-api-service-providers
docs/249-merge-evidence
rage/249-latency-trace-checkpoint
fix/246-disable-todo-surface
codex/zara-discord-plugin-guidance
rage/157-execution-plans
rage/156-prolog-frames
rage/28-post-merge-evidence
perf/zara-027-streaming-llm-impl
rage/155-typed-slots
test/live-smoke-reasoning-budgets
feature/openrouter-rlm-directmode
rage/154-intentframe-contract
chore/backlog-import
rage/195-samsung-assistant-research
feat/android-app
research/aradr-local-tts-voice-cloning
feature/wake-words-edit-distance
perf/zara-027-streaming-llm
docs/134-reentry-assessment
rage/134-daemon-release-gate
rage/131-merge-closeout
docs/rage-130-merge-outcome
docs/rage-17-merge-outcome
fix/zara-016-llm-provider-contracts
build/flake-update-2026-08
rage/191-zara1-tool-approvals
rage/132-visible-stt-regression
codex/copilot-redesign
codex/default-daemon-cli
rage/132-transcript-events
rage/133-post-merge-evidence
rage/133-client-migration
rage/132-post-merge-evidence
rage/132-live-voice
rage/132-live-voice-zara1
rage/131-principal-isolation
rage/131-principal-scope
rage/130-curve-zap-security
rage/130-auth-security
docs/rage-129-merge-outcome
rage/129-zara1-protocol
rage/129-slice-e-lifecycle-red
rage/129-slice-e-endpoint-red
docs/rage-128-merge-outcome
rage/139-daemon
docs/full-feature-sweep
feature/mcp-client-support-current
remove-prolog-rlm
research/daemon-zeromq-voice-service
feature/autoresearch-bootstrap
agent/VAD-patch
agent/prolog-capability-reasoner
agent/whisper-cpp-vulkan-stt
agent/remove-pet-notification-spam
codex/service-plugin-runtime
agent/stt-backends
agent/fix-laptop-stt-quality
feature/prolog-rlm-integration
agent/fix-speaker-echo-loop
agent/stt-gpu-rocm-support
agent/fix-ubuntu-wayland-pets
feature/desktop-theme-contrast
fix/whisper-load-state
agent/mcp-client-support
fix/wake-model-readiness-debug
fix/wake-capture-failure-propagation
fix/wake-audio-health
agent/readme-current-zara
fix/desktop-conversation-migration-repair
agent/fix-voice-runtime-noise
feature/desktop-launch-surface
feature/quick-copilot
feature/conversation-full-chat
feature/desktop-shell
feature/runtime-host
feature/runtime-events
research/desktop-copilot
agent/overhaul-memory-forgetting
agent/fix-command-context-routing
agent/fix-streaming-vad-wake
agent/pets-post-merge-fixes
feature/pets
revert/wake-throughput
fix/wake-word-detection
fix/pulse-shared-mic-ci
fix/shared-mic-capture
feat/zara-timer-alarm-sounds
fix/zara-017-todo-correctness
fix/zara-015-prolog-engine-contract
fix/zara-018-ack-result-events
agent/readme-rewrite
fix/zara-014-wake-lifecycle
fix/zara-013-file-tool-sandbox
fix/zara-012-process-safety
fix/recover-zara-006-011-to-master
revert-36-fix/zara-005-dictation-lifecycle
revert-44-fix/zara-011-dictation-ordering
fix/zara-010-tts-contracts
fix/zara-011-dictation-ordering
fix/zara-007-intent-precedence
fix/zara-008-multi-tool-history
fix/zara-009-memory-fallback
fix/zara-006-timers
fix/zara-005-dictation-lifecycle
fix/zara-003-fail-closed-commands
fix/zara-004-prolog-config-overrides
agent/ci-test-gate
fix/zara-002-config-toml
fix/zara-001-wake-entrypoint
memory
cleanup
device-acceptance-661
v0.1.0-alpha
Labels
Clear labels   
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/zara#173
No description provided.