ORKA CODE · Release notes· Version 0.2.2

Orka Code 0.2.2 — clearer work, stronger continuity

· A clearer live-work timeline, safer Session continuity, new Claude-native capabilities, and a broad interface-coherence pass for the private Alpha.

Orka Code 0.2.2 — clearer work, stronger continuity

0.2.2 is a catch-up and confidence release for Orka’s selected private Alpha cohort. It packages the product work merged since 0.2.1, keeps the existing exact managed harness pair, and refreshes compatibility review against the final Orka implementation.

Clearer live agent work

  • The transcript is now one calmer streaming timeline, with compact reasoning, tool, task, and result rows; clearer in-flight and settled states; improved long-session scrolling; and clickable local-file references.
  • Questions, permissions, plans, MCP elicitation, and authentication recovery settle through a composer-anchored request drawer without losing their provider-specific meaning.
  • Drafts, send errors, and asynchronous settlements stay attached to the exact Session and Workspace that produced them.

Claude-native additions

  • Artifact publishing is explicit and consent-gated: Orka asks before publish or browser open and never silently auto-approves.
  • Usage-limit recovery parks the Session truthfully. Automatic continuation is optional, Profile-fenced, bounded, and off by default.
  • Todo-tool activity, MCP startup failures, and EndConversation finalization are presented as first-class lifecycle events instead of generic chat text.
  • Browser control remains visible but cannot be enabled in 0.2.2 because Orka did not verify a provider-native connection and representative action on the managed Claude Code pin. Existing enabled settings can still be turned off, and the setup guide remains available. Orka does not claim that an extension, account, browser profile, or tab is connected.

Continuity and trust

  • Durable Codex Sessions retain the exact managed runtime that founded them across relaunch, resume, native fork, and update preflight.
  • Managed-binary downloads expose bounded progress and clean up abandoned scratch data after interruption.
  • Failure messages are scoped and actionable, with retained drafts and local incident context instead of cross-Workspace error spill.
  • Zero-remote repositories remain first-class for create, start, send, resume, commit, and local merge workflows.

Whole-app coherence

  • Shared control, badge, chip, typography, radius, density, elevation, focus, motion, overlay, and toast rules now cover the main product surfaces.
  • Command Palette, keyboard shortcuts, and the native macOS menu share one command registry and consistent Escape behavior.
  • Observability adapts from the minimum window to ultrawide layouts with one deliberate scroll owner and truthful zero-versus-unavailable values.
  • Empty states, truncation, recovery actions, and long labels now preserve the information needed to understand and repair a problem.

Exact managed harnesses

  • Claude Code remains on exact managed 2.1.236.
  • Codex remains on exact managed 0.148.0.
  • Max approved this exact pair for private 0.2.2 under decision max-one-time-0.2.2-private-frozen-harnesses-2026-08-21. The release gate still checks and reports registry drift. Registry-current harness admission and upstream feature review move to the dedicated 0.2.3 harness release.

Honest compatibility boundaries

  • Both pins retain exact artifact and release-member hashes, synchronized model catalogs, all eleven compatibility surfaces, structured regressions, fail-closed unknown-shape handling, and refreshed implementation bindings. Release remains blocked until the final candidate receives independent fixed-commit approval.
  • Missing complete provider-native replay remains explicit UNVERIFIED-LIVE debt across both harnesses, including MCP and Skills. This release reuses no 0.2.1 MCP carve-out.
  • Unsupported semantic controls remain unavailable instead of becoming prompt text or simulated success.

Private Alpha boundary

Install only the signed and notarized DMG supplied through the invited Alpha handout, and do not redistribute it. Commit or back up irreplaceable work before installing or updating.

The frozen-pair and evidence decisions apply only to exact app version 0.2.2 with private visibility. They cannot be reused for 0.2.3, a later release, or a public build.