ORKA CODE · Release notes· Version 0.3.1

Orka Code 0.3.1 — speed, Pierre, and current harnesses

· Dramatically faster session opening, the Pierre file/diff experience, full access by default, and registry-current harnesses including Claude Fable 5.1.

Orka Code 0.3.1 — speed, Pierre, and current harnesses

0.3.1 packs a seven-sprint performance-and-UI arc plus a same-week harness refresh into one private Alpha release.

Much faster where it counts

  • Opening older sessions is ~60–90× faster: transcript checkpoint scans that took 29–100ms now resolve in ~0.3–1.1ms, backed by new guarded expression indexes.
  • The app re-renders far less under multi-session streaming: session, fleet, and presence state moved into narrow-subscription stores, and the event presentation pipeline was extracted and tightened.

The Pierre file and diff experience

  • The Files tab is a Pierre tree: git-status letters (M/A/D/R/U) with folder rollups, the complete colored icon set, compact rows, search, right-click menus, and drag-and-drop file moves with a guarded backend.
  • The Changes tab is a folder-grouped changed-files tree; clicking a file opens its diff as a center tab with Split/Stacked views.
  • The Assistant’s file surfaces use the same trees. Everything loads lazily — zero Pierre modules at app boot — and follows light/dark theming.

Full access by default

  • New sessions on both harnesses launch with full tool access unless you explicitly opt into approvals, choose plan mode, or a session inherits a predecessor’s explicit choice. Historical reviewed Assistant actions replay truthfully with their recorded mode.

Registry-current harnesses

  • Claude Code 2.1.258 — including Claude Fable 5.1 with its one-million-token context in the model pickers.
  • Codex 0.152.1 — including the refreshed visible model catalog (gpt-5.6-sol and friends); hidden catalog entries remain excluded until proven.
  • Both pins admitted under the Harness Fidelity Contract with independent approvals; remaining live-fidelity debt is recorded honestly under the 0.3.1 private evidence policy.

Under the hood

  • Two cleanup passes removed dead code and re-verified every protected mechanism; the codebase held up better than expected.
  • Release binary and evidence chains are digest-bound end to end.