New
- A second agent harness, behind a flag.
pi(pi-agent-core) now runs in-process in the sandbox alongside OpenCode, selected per project by thepi_harnessfeature flag. It implements abort-after-tool so Quick Queue can stop a turn at a tool boundary, and it enforces the same per-pattern permission rules OpenCode applies. Off unless a project opts in, so nothing changes for existing projects.
Improved
- The
pi_harnesssetting reads correctly in all nine languages. - Internal: the sandbox daemon's timing budgets now tolerate a slow machine during a process respawn, so a correct restart is no longer reported as a failure.
Fixed
- Restored the load-balancer response-time alarms required by the Drata DCF-86 control.
What's Changed
- feat(kortixd): pi harness — pi-agent-core in-process as a second HarnessDefinition by @DimitrijeGlibic in #7332
- chore(release): staging VERSION → 0.13.24 [skip ci] by @github-actions[bot] in #7371
- chore(release): VERSION → 0.13.24 [skip ci] by @github-actions[bot] in #7372
- fix(drata-294): add ALB TargetResponseTime alarms (DCF-86 system monitoring) by @agent-kortix in #7328
- test(kortixd): budget the first-ready waits for a real respawn on a loaded runner by @markokraemer in #7376
- chore(staging): bring staging to main (pi harness behind a flag, 14 commits) by @markokraemer in #7375
- Release v0.13.24 — The pi agent harness, behind a per-project flag by @github-actions[bot] in #7377
Full Changelog: v0.13.23...v0.13.24