Orca v0.2.55

Full Changelog: v0.2.54...v0.2.55

Orca v0.2.54

Full Changelog: v0.2.53...v0.2.54

Orca v0.2.53

Full Changelog: v0.2.52...v0.2.53

Orca v0.2.52

Orca v0.2.52

Orca v0.2.52 fixes a continuation boundary that could stop a persistent Goal
even though the model had only reached its inner-turn limit. Turn completion
now preserves whether work advanced, was interrupted at a resumable boundary,
or requires human or external intervention.

What Changed

• Goal continuation now uses a typed disposition:
  Advanced, Interrupted, or Blocked. MaxInnerTurns is a resumable
  interruption; cost-budget exhaustion, cancellation, approval, verification
  failure, and other blocking outcomes still pause.
• Agent-loop results preserve a typed end reason through the controller,
  thread, and RuntimeHost boundaries. The continuation gate no longer has to
  infer semantics from a lossy success boolean.
• Budget soft-landing reminders are injected before inner-turn, cost, and Goal
  token limits are exhausted. They ask the model to finish the current atomic
  step, update the task plan, and record findings at a clean handoff point.
• Every automatic continuation receives a structured handoff containing the
  objective, continuation trigger, previous status and end reason, token
  budget, open gap, current task plan, and a bounded assistant checkpoint. The
  next turn is told to resume from that state and verify the current worktree
  instead of restarting repository exploration.
• Progress detection is now independent from continuation admission. Completed
  mutating tools and structured plan changes count as substantive progress;
  read-only exploration and model chatter do not.
• SQLite recovery preserves productive-turn barriers, so identical gaps on
  opposite sides of real progress are not joined into one false streak.
• The watchdog pauses after three repeated model-fixable gaps and separately
  caps eight consecutive MaxInnerTurns interruptions.

Compatibility

No CLI, TUI, configuration, or SQLite schema migration is required. Existing
Goal state and turn history remain readable.

The behavior change is intentionally narrow: reaching the inner-turn limit can
now continue automatically. Cost-budget exhaustion, cancellation, approval
requirements, verifier failure, user control, pending interaction, and
workflow ownership remain stopping boundaries.

Verification

• complete serial Rust workspace test suite
• 946 orca-runtime unit tests and all runtime integration suites
• Rust formatting and workspace clippy
• npm staging and published-package verifier self-tests
• website production build and SEO checks
• public GitHub Release, npm package, platform aliases, and npm exec smoke
  verification

Install

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

Or install a native release asset:

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

Orca v0.2.51

Full Changelog: v0.2.50...v0.2.51

Orca v0.2.50

Full Changelog: v0.2.49...v0.2.50

Orca v0.2.49

Full Changelog: v0.2.48...v0.2.49

Orca v0.2.48

Orca v0.2.48

Orca v0.2.48 corrects ACP implementation metadata and hardens the adapter's
runtime integration tests.

What Changed

• ACP initialize now reports the Orca binary release version from
  RunConfig.app_version. The previous release exposed the internal
  orca-runtime crate version (0.1.0) through agentInfo.version.
• ACP integration tests isolate ORCA_HOME, so recorded session fixtures never
  touch a developer's real conversation history.
• The hosted-turn test verifies that each ACP session preserves the working
  directory supplied by session/new.
• Cancellation coverage now exercises a notification that arrives before the
  hosted OperationHandle is installed. The pending cancel is applied as soon
  as the handle becomes available and still terminates through the active
  Generation Fence.
• The v0.2.47 ACP release is now included in the website release list and
  bilingual changelog.

Compatibility

The ACP wire methods, internal JSONL protocol, TUI behavior, tool schemas,
history format, npm package name, and native archive layout are unchanged.

Verification

• 11 ACP EventEnvelope projection unit tests
• 4 RuntimeHost-backed ACP integration tests
• complete serial workspace tests and workspace check
• npm staging and smoke tests
• website build and SEO checks

Install

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

Or install a native release asset:

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

Orca v0.2.47

Orca v0.2.47

Orca v0.2.47 adds an Agent Client Protocol (ACP) adapter layer, enabling code
editors and ACP-compliant clients to communicate with Orca over the standard
JSON-RPC wire format via stdio.

What Changed

• New --mode=acp entry point runs Orca as an ACP-compliant agent on stdio,
  parallel to the existing --mode=server (internal JSONL protocol).
• ACP sessions map to runtime threads; ACP prompts map to hosted turns; runtime
  EventEnvelopes are projected to session/update notifications.
• Supported ACP methods: initialize, authenticate (no-op),
  session/new, session/load, session/prompt, session/cancel.
• Streaming session/update notifications include: AgentMessageChunk,
  AgentThoughtChunk, ToolCall, ToolCallUpdate, and Plan.
• Uses agent-client-protocol v0.10.4 with the unstable feature.
• The internal JSONL protocol (--mode=server) is unchanged.
• HostedTurnRequest::event_observer() is now public to support custom
  ThreadOperationExecutor implementations in integration tests.

Architecture

The ACP adapter is intentionally thin:

ACP concept	Projected onto
session/new / session/load	RuntimeHost::start_thread
session/prompt	RuntimeThreadHandle::start_turn_with_config + EventObserver
session/update	EventEnvelope -> event_map::event_to_session_update
session/cancel	OperationHandle::interrupt()
Completion	OperationHandle::completion().wait() -> StopReason

Three execution contexts bridge async(?Send) ACP to blocking RuntimeHost:

1. RuntimeHost internal thread (owns turns, synchronously callbacks observer)
2. ACP LocalSet thread (drives JSON-RPC connection + notification drain)
3. tokio blocking pool (spawn_blocking for all RuntimeHost calls)

Compatibility

Tool names, JSON schemas, slash commands, TUI keys, server methods, history
records, npm package names, and native archive layout are unchanged. The ACP
entry point is additive.

Verification

• 11 unit tests for event mapping (event_map::tests)
• 4 integration tests (tests/acp_agent.rs): initialize, new_session+prompt,
  cancel, and unknown-session error handling
• Full workspace build (no warnings in ACP code)

Install

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

Or install a native release asset:

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

Full Changelog: v0.2.46...v0.2.47

Orca v0.2.46

Full Changelog: v0.2.45...v0.2.46