ORKA CODE · Release notes· Version 0.4.3

Orka Code 0.4.3

· Claude Code 2.1.289 and Codex 0.160.0, instant Send, switching models without leaving the chat, clearer Claude sign-in recovery and truthful spend.

Orka Code 0.4.3

  • Update the managed harnesses to Claude Code 2.1.289 and Codex 0.160.0. Existing conversations keep the runtime they were recorded with.
  • Pick the newest models as your signed-in account advertises them: Opus 5.5 and Sonnet 5.5 for Claude, GPT-6 Sol and Luna and the GPT-6.1 Sol default for Codex. New installs start Claude on Sonnet 5.5; saved model choices are kept. Removed models show as not available instead of being swapped silently.
  • See truthful spend. Claude reports a running total per process, and resumed or forked conversations now inherit it; Orka records each turn’s own cost and keeps the running total as the baseline, so forks, revives and app restarts no longer inflate what you spent.
  • Keep working when an MCP server asks a question Orka cannot show yet. Orka declines the request the way the harness expects instead of leaving the turn waiting.
  • Preserve Claude’s mandatory permission warnings even in Full access, and hide remember controls when the native request prohibits them. No bypass-immunity claim is made.
  • Keep your Profile’s own Skills synced from claude.ai; plugins from claude.ai stay off in Orka so nothing adds MCP servers, hooks or pre-approved tools outside the MCP Store view.
  • Quieter transcripts: Claude’s 30-second keep-alive pings during slow responses no longer appear as unknown events.
  • Send feels instant. Your message appears right away, marked as sending or starting the session, until the harness accepts it. If it can’t be sent, your draft comes back to the composer.
  • Switch to the other harness’s model without leaving the chat. Orka shows what will be shared with the other provider, then continues on your next message in the same tab. The earlier conversation stays one click away.
  • Clearer Claude sign-in recovery. There is one place to act. After you reconnect the same account, confirm it once to continue the Session; a different account still stops it.
  • Archiving a Workspace with open terminals works again after you confirm.

Codex 0.155 and later migrate their local state database one way; a Session that has run on 0.4.3 cannot be guaranteed to open again on 0.4.2.