Orca v0.3.0

Orca v0.3.0

Orca v0.3.0 adds native Windows x64 and ARM64 support to the CLI, TUI,
sandbox, update flow, npm packages, and release pipeline. Windows is now a
tested release platform rather than a compatibility path compiled from another
host.

What Changed

• PowerShell 7, Windows PowerShell, cmd.exe, and explicit Git Bash commands are
  resolved with their own quoting and invocation rules. PowerShell 7 is found
  through both PATH and its standard installation directory; restricted
  sessions fall back to cmd.exe instead of using Windows PowerShell 5.1 under
  AppContainer ConstrainedLanguage. Structured command arrays launch as native
  Windows argv without shell re-parsing, while legacy strings retain shell
  semantics. ConPTY backs interactive shell sessions, including terminal
  resize and process-tree cleanup through Job Objects.
• Windows input handles AltGr without turning text entry into a Ctrl+Alt
  shortcut. Clipboard access uses native Windows APIs, and the system prompt
  names the active shell dialect instead of giving POSIX-only instructions.
• Sandboxed commands use restricted tokens for capability modes and
  AppContainer when restricted reads or network isolation require it. Path
  identity rejects ambiguous device, ADS, and reparse-point escapes; ACL
  changes use the same verified handle with explicit DACL access.
• install.ps1 detects x64 or ARM64, downloads the matching archive, verifies
  its SHA-256 checksum, and installs orca.exe, the native runner, and the
  sandbox setup helper. -SetupSandbox, -RepairSandbox, and -RemoveSandbox
  manage the workspace capability receipt.
• Standalone and npm updates replace the running Windows installation only
  after its process exits. Runtime state uses cross-process OS locks and atomic
  replacement on Windows as well as Unix, covering goals, tasks, workflows,
  threads, and history.
• GitHub Releases and npm now cover six native targets. Windows archives
  contain the CLI, runner, setup helper, and license; native x64 and ARM64 CI
  run reviewed platform contracts and the complete workspace test suite.

Compatibility

Existing CLI flags, configuration, JSONL, app-server, and ACP contracts remain
compatible. Windows sandboxed execution requires a provisioned workspace
capability; without it, restricted commands fail with setup guidance. Direct
domain-restricted network policies remain unsupported on Windows and fail
closed. danger-full-access remains the explicit unrestricted mode.

Verification

• cargo fmt --all -- --check
• cargo test --workspace --all-targets --locked -- --test-threads=1
• cargo clippy --workspace --all-targets --locked
• cargo xwin check --workspace --all-targets --target x86_64-pc-windows-msvc --locked
• node scripts/test-validate-windows-platform-boundaries.mjs
• node scripts/validate-windows-platform-boundaries.mjs
• node scripts/release/test-verify-version-sync.mjs
• node scripts/release/test-stage-npm.mjs
• node scripts/release/test-verify-published.mjs
• npm --prefix site run build
• npm --prefix site run check:seo
• Native Windows x64 and ARM64 platform contracts and full workspace tests

The tag workflow repeats the locked serial workspace test, builds archives for
all six targets, publishes the main package and six platform packages, and
verifies checksums, npm integrity, package aliases, native binary identity, and
a clean installed orca --version result.

Install

npm install -g @blade-ai/orca@0.3.0

macOS and Linux native installer:

curl -fsSL https://orcaagent.dev/install.sh | \
  INSTALL_DIR=/usr/local/bin ORCA_VERSION=0.3.0 sh

Windows PowerShell, including workspace sandbox setup:

& ([scriptblock]::Create((irm https://orcaagent.dev/install.ps1))) -Version 0.3.0 -SetupSandbox

What's Changed

• fix(test): make subagent sleep hook portable on Windows by @echoVic in #13
• test(workflow): gate windows cli timing on model-call hook by @echoVic in #15

Full Changelog: v0.2.56...v0.3.0