Repository navigation
Orca v0.5.2
Fixes after v0.5.1:
- A
*in a bash permission rule now matches/, so deny rules catch
commands with paths. - A plan inside a reply keeps its place when a session is resumed or a
background turn returns to the foreground. - Stopping a background agent while its worker starts now works and says so.
- A late
turn/steeris refused instead of running later as a turn. - The post-publish release checks wait out npm propagation.
Changes
Permission rules
- In a
bashrule,*and?now match any character,/included. A deny
rule such asrm -rf *now also catchesrm -rf /tmp/build. An allow rule
such asgit push *now covers a branch namedfeature/login. Rules for
file tools still match paths:*and?stay within one directory, and
**crosses directories. - The approval modes page documents rule syntax.
Terminal UI and sessions
- A plan inside a reply now stays between the text before and after it. This
holds when a session is resumed and when a background turn is brought back
to the foreground. It used to show after the whole reply.
Background agents
- Stopping a background agent while its worker is still starting now waits
for the worker, stops it, and shows "stopped by user". The stop used to
fail. The agent then kept running, or later stopped without saying who
stopped it.
App server
- A
turn/steercan arrive after the turn has decided to end. It now gets a
turn_controlledreply with"status":"idle"and is not applied. It used to
be queued and run later as a turn the client never started. The harness
contract documentsturn/steer. - In the TUI, a message sent with
Ctrl+Enterthat the turn can no longer
take goes to the front of the queue, as before.
Release tooling
- The post-publish checks wait up to 15 minutes for npm to serve a new
version. This covers the clean install and the Windows smoke tests. - The published-release check accepts commits pushed to main after the tag.
verify-release.ymlreruns the whole post-publish verification without
re-tagging.
Tests
- Hosted child tests now run in their own directory, not the crate
directory. Task sessions left there by old test runs made them time out
when run together. - The continuation-lease storage test and a Windows server shutdown test no
longer fail under load.
Compatibility
- Bash permission rules.
*in abashrule now matches/. An allow
rule such asgit *now also allows git commands whose arguments contain
slashes. Review any allow rules that relied on the old matching. - Plan position. When more text follows a plan in a reply, the session
records where the plan sat. Orca 0.5.1 and earlier cannot open a session
that holds such a record. Other sessions are unaffected. turn/steer. A client can receive"status":"idle"for a steer sent
while the turn is ending. Send that input withturn/startinstead.
Existing configurations and conversation history remain readable.
Verification
cargo fmt --all -- --check
cargo clippy --workspace --all-targets --locked -j 1
node --test scripts/test-validate-runtime-surface-contract.mjs
node scripts/validate-runtime-surface-contract.mjs
node --test scripts/test-validate-windows-platform-boundaries.mjs
node scripts/validate-windows-platform-boundaries.mjs
node scripts/release/verify-version-sync.mjs
node scripts/release/test-verify-version-sync.mjs
node scripts/release/test-stage-npm.mjs
node scripts/release/test-verify-published.mjs
cargo nextest run -p orca-tui --lib --locked --profile ci-serial --retries 0
cargo nextest run --test tui_pty_contract --locked --profile ci-serial --retries 0
cargo nextest run --workspace --all-targets --locked --profile ci --no-fail-fast --retries 0
npm --prefix site run build
npm --prefix site run check:seoUpgrade
npm install -g @blade-ai/orca@0.5.2
orca --versionFull Changelog: v0.5.1...v0.5.2