chore(master): release 0.26.1

[arcbox-labs]

🤖 I have created a release beep boop

0.26.1 (2026-08-26)

Bug Fixes

• agent-adapter,engine: stream codex rollout reads and evict expired history caches (#466) (fedc6ec)
• pi: preserve account model IDs with slashes (#471) (6bb0633)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This automated release PR advances the desktop application from version 0.26.0 to 0.26.1.

• Updates the Release Please manifest and desktop package version.
• Adds the 0.26.1 bug-fix release notes to the desktop changelog.

Confidence Score: 5/5

The release metadata update appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Advances the tracked release version from 0.26.0 to 0.26.1.
apps/desktop/CHANGELOG.md	Adds the generated 0.26.1 release notes and links to the included fixes.
apps/desktop/package.json	Updates the desktop package version to 0.26.1, consistent with the release manifest and changelog.

_{Reviews (2): Last reviewed commit: "chore(master): release 0.26.1" | Re-trigger Greptile}

[pullfrog]

✅ No new issues found.

Reviewed changes — a stock release-please cut of the single managed package (., component desktop). No behavioral surface of its own, so this review is verification rather than code reading.

• .release-please-manifest.json — "." bumped 0.26.0 → 0.26.1.
• apps/desktop/package.json — version bumped 0.26.0 → 0.26.1 via the config's extra-files $.version write.
• apps/desktop/CHANGELOG.md — new ## [0.26.1] section with the compare link v0.26.0...v0.26.1.

Checks performed against head 2639d921:

• Version agreement and bump size are correct. All three files say 0.26.1, and the only commit between tag v0.26.0 (16411c91) and this PR's base is fedc6ec6 fix(agent-adapter,engine): … — a single fix: → patch.
• No stale version drift. grep -rn -F '0.26.0' across the repo excluding node_modules, .git, and *CHANGELOG.md returns zero hits (no pnpm-lock.yaml substring false positive this cut). Root package.json at 0.0.0 and apps/mobile/app.json expo.version at 1.0.0 are both by design, not drift.
• The compare link resolves. git ls-remote --tags origin confirms v0.26.0 exists at 16411c91, so the changelog's v0.26.0...v0.26.1 range is real.
• No undocumented riders. git log origin/master --not HEAD^ is empty, so the PR base is master HEAD — nothing extra will ride into the tag that finalize-releases.yml places on post-merge master.
• The one shipped fix carries no release-machinery risk. git diff --stat 16411c91...fedc6ec6 touches only packages/host/agent-adapter/src/native/codex/{adapter,history}.ts, packages/host/engine/src/session/history-service.ts, and three test files. No workflow, composite action, packaging script, or toolchain pin changed, so this release is not the first to exercise a reworked signing or packaging path — a release-desktop.yml dry_run: true dispatch isn't warranted here.

Mergeable as-is once CI is green on 2639d921.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes — release-please force-replaced the branch (2639d921 → f52e3fdc) after 6bb0633a fix(pi): preserve account model IDs with slashes (#471) landed on master. The recut touches only the changelog; .release-please-manifest.json and apps/desktop/package.json are byte-identical to the previously reviewed cut.

• Added the #471 changelog bullet — apps/desktop/CHANGELOG.md:9 now lists fix(pi): preserve account model IDs with slashes alongside the existing #466 entry.
• Rolled the section date — 2026-08-24 → 2026-08-26 on the ## [0.26.1] heading.
• Held the version at 0.26.1 — a second fix: on top of a fix: is still the same patch, so no manifest or package.json churn. Correct.

Checks re-run against head f52e3fdc:

• Bump size still matches the range. git log 16411c91..HEAD^ is exactly fedc6ec6 fix(agent-adapter,engine): … (#466) and 6bb0633a fix(pi): … (#471) — two fix: commits, patch. Both appear in the changelog, and nothing in range falls into release-please's hidden chore/ci/docs/refactor sections.
• No stale version drift. grep -rn -F '0.26.0' excluding node_modules, .git, and *CHANGELOG.md returns zero hits. Root package.json at 0.0.0 and apps/mobile/app.json expo.version at 1.0.0 are by design.
• The compare link resolves. git ls-remote --tags origin confirms v0.26.0 at 16411c91, so v0.26.0...v0.26.1 is a real range. No abandoned-version check needed — this recut changed no version.
• No undocumented riders. git log origin/master --not HEAD^ is empty, so the PR base is master HEAD and nothing extra rides into the tag finalize-releases.yml places on post-merge master.
• No release-machinery risk. git diff --stat 16411c91...6bb0633a touches only packages/foundation/providers, packages/host/agent-adapter, packages/host/engine, one AGENTS.md, and five test files. No workflow, composite action, packaging script, or toolchain pin, so this release is not the first to exercise a reworked signing or packaging path — a release-desktop.yml dry_run: true dispatch isn't warranted.

Mergeable as-is once CI is green on f52e3fdc.

  ^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

[arcbox-labs]

🤖 Created releases:

• v0.26.1

🌻