# Changelog

## 0.4.4 — Guided installation for the CLI beta

- Publish checksum-pinned Mac and Windows installers that prepare a private Node runtime and CLI before guided setup. Agents can use `--install-only` / `-InstallOnly` for installation without account access, then request any required user authorization.
- Include guided Orca deployment, original pairing reuse, project selection, background service and bounded watchdog recovery in the downloadable CLI.
- Handle Windows Unicode paths, NSIS install paths with spaces, PowerShell 5.1 script encoding and built-in module discovery when launched from PowerShell 7.
- Add native Windows acceptance for official Orca installation, private stdin pairing, a fresh private Node runtime, repeat installation, preserved configuration, startup ownership and unchanged window focus. Tests use synthetic identities and never call a model.
- Synchronize the download page, installation manual and three-file Agent Skill around the same guided setup flow. Keep source private and desktop downloads withdrawn.

## 0.4.3 — Guided first installation (local trial)

- Add `onboard` and local-only `onboard --check` for login, verified per-user Orca installation, background service, cloud deployment, saved pairing, project selection and watchdog verification.
- Reuse existing installations and require explicit one-time desktop permission when no execution channel exists. No model fallback or background desktop control.
- Import pairing through stdin in a headless process without secret arguments, environment variables, temporary files or logs.
- Keep safe resumable stages, prevent overlapping setup and verify actual readiness on reruns.
- Prepare checksum-pinned Mac/Windows host installers with a private Node runtime. Public rollout and new Windows native acceptance remain pending.

## 0.4.2 — Event-driven Orca watchdog maintenance (local trial)

- Add opt-in `watchdog enable`, `status`, `check`, and `disable` through an existing Orca pairing and a dedicated background maintenance terminal.
- Ensure the recognized tmux watchdog or reuse the checksum-verified cloud supervisor, preserving data, pairing, launcher and user terminals.
- Reuse gateway health events with a six-hour success cache, ten-minute recovery cooldown, coalesced requests and a persisted three-failure budget. No additional local polling timer, model request or desktop fallback.
- Observe tmux process exit with Linux pidfds when available, with a five-minute local HTTP audit and timed fallback on older kernels.
- Embed maintenance payloads in standalone bundles to preserve the existing updater archive format. Public downloads retain the previously published version pending trial acceptance.

## 0.4.1 — CLI updates and preserved authorization

- Make the CLI a standalone JavaScript bundle with no npm dependency installation during self-update.
- Add `update`, `update --check` and `update --rollback`, using the official HTTPS catalog, exact download paths, bounded archives, SHA-256 validation, standalone startup checks and failure rollback.
- Preserve active gateway processes, profile settings, Orca pairing and native helper identity during updates; restarting a background service remains explicit.
- Preserve an already-authorized Mac helper in the private profile, pin its binary digest and share it across future CLI/desktop versions. Never cache a password or plaintext login token.
- Make repeated `init` reuse the current account authorization and report running gateway version and owner kind.
- Keep the published desktop 0.4.0 packages available while prioritizing CLI 0.4.1.

## 0.4.0 — Desktop Bot chat

- Add a Mac/Windows Bot chat page with Bot selection, message submission, recent replies, per-Bot drafts and read-only auto-update while visible.
- Require explicit model-usage confirmation for every message. Block duplicate submissions; uncertain sends remain manual and are never resent automatically.
- Keep login/route credentials in the main process; pass only display fields to the renderer, render replies as plain text, and exclude conversations from logs and diagnostics.
- Cancel stale reads across account/settings changes and stop reply polling when leaving or hiding the chat view.
- Validate the backend with synthetic clients and the renderer with hidden native Mac/Windows fixtures; automated checks never submit a real Grok prompt.

## 0.3.1 — Binary beta distribution

- Point desktop help and cloud setup at the hosted beta download/manual page, so users do not need private repository access.
- Link directly to the pinned official Orca release for desktop installation.
- Provide private-source Mac/Windows binaries and a verified Linux cloud executable with a checksum-pinned installer.

## 0.3.0 — Windows x64 private preview

- Add current-user DPAPI and Chromium AES-GCM login adapters, protected executor identities and private NTFS metadata.
- Add Windows proxy discovery, a colored tray, native window controls and platform-specific onboarding.
- Add silent per-user CLI startup with an owned Windows Job Object; never kill an unrelated PID.
- Add per-user NSIS/ZIP packaging and native Windows credential, installer, startup, no-focus and uninstall checks.
- Keep Windows CI artifacts private. Real Grok Windows-account validation remains a separate acceptance step.

## 0.2.0 — Private cloud CLI preview

- Add all 17 missing command names from the local reference CLI, plus `status --cloud`.
- Add direct `run`, line-oriented `sh`, signed executor install/check/autostart,
  read-only agents/transcripts, PNG screenshots and explicit remote input.
- Keep model prompts behind `--allow-model`; desktop bootstrap requires `--desktop`.
  Never use a model or remote desktop as a background reconnect fallback.
- Derive an account-bound Ed25519 executor identity in memory, install only its
  public key, reject replay/expired/modified requests, and bound execution/output.
- Preserve the existing local gateway/control protocol and separate CLI/cloud setup.
- Add isolated HTTP/RFB/shell regression coverage and include the executor in the
  private CLI payload audit. No public release or live model/UI testing.

## 0.1.1 — Private preview preparation

- Fully ad-hoc sign both architectures of the native Keychain helper and include
  a designated code requirement. Packaged smoke checks now validate the helper
  separately from the app bundle.
- Explain persistent Keychain permission, the complete CLI login-service setup,
  keepawake timing and checkout-based installation while the repository is private.
- Scan the staged CLI payload before distribution and keep checksums scoped to
  the current version.

## 0.1.0 — Preview

- Mac menu bar app with English/Chinese setup, account authorization, pairing
  conversion, connection controls, proxy settings, login startup and diagnostics.
- CLI sharing a single private profile owner with the desktop app.
- Loopback-only opaque WebSocket relay, authenticated provider route validation,
  server-first frame preservation, bounded retries and transient-failure recovery.
- Memory-only provider credentials and a noninteractive native Keychain helper.
- Checksum-pinned official Linux Orca installer with persistent pairing data,
  bounded process supervision and optional cloud desktop autostart.
- Core, real local WebSocket, hidden desktop and simulated cloud lifecycle tests;
  release privacy checks, CI builds and third party notices.

This preview uses a private provider API and is not Apple notarized. Platform
uptime and authenticated live Orca sessions require validation in the user's own
account; automated tests do not use personal Grok credentials.
