[btsouth]

Summary

Cuts 1.5.27 and supersedes the 1.5.26 draft, which was built and signed but never published — its Claude account-isolation fix ships here rather than sitting in a draft nobody can install. The stale draft release has been deleted; the v1.5.26 tag stays as a marker of what was built.

Version bumped in all five locations from VERSIONING.md, BUILD_NUMBER=129, Cargo.lock regenerated.

What's in it

Six user-facing entries covering everything merged since the v1.5.26 tag:

• Cursor on-demand at a glance (Show Cursor on-demand usage at a glance #254, reported in [Feature]: Show (cursor) on-demand spendings ($) when reached 100% #191) — the reason for cutting this now
• Codex no longer overcharges gpt-5.1-codex-mini (Fix Codex mini pricing normalization #250) — billed at $1.25/M instead of $0.25/M
• Pace describes the window actually running hot (Report pace for the window actually running hot #256)
• Concurrent writes can no longer lose settings or credentials (Prevent concurrent state-store data loss #245)
• Configured Claude accounts no longer collapse onto one session (from the unpublished 1.5.26)
• Tab strips can be driven from the keyboard (Give tab strips keyboard navigation #255, closes Tab strips have no keyboard navigation #219)

Browser cookie import (#247) is written up under Changed rather than buried in Fixed, since it removes a capability: it says plainly that a provider authenticated that way will ask to be set up again, and that CLI, IDE, OAuth, and Claude Desktop detection are unaffected.

The date reads 2026-08-11, matching the established pattern — 1.5.22, 1.5.24, 1.5.25 and 1.5.26 all use the UTC date of their tag, and each was cut late-evening local.

Validation

scripts\local-check.ps1 -All -Version 1.5.27 passed in full: clippy and tests on both Rust manifests, frontend tests and build, store submission preparation, and release doctor. Release doctor's 3 warnings are all "tag / assets / GitHub release do not exist yet", which is expected before tagging.

Two flakes on earlier runs of that script, both confirmed environmental and not regressions:

• cli::tty_runner::tests::test_run_sends_script_through_pty resolves npm's cmd shim as the PTY shell and fails with Windows error 193 unless System32 leads PATH — the same failure recorded in Prevent concurrent state-store data loss #245 and Replace browser cookie import with manual setup #247. Worth a follow-up to resolve cmd.exe from %SystemRoot% rather than PATH.
• TokenAccountsPanel.test.tsx timed out on a findByText under load; it passes in 144ms on its own, against a 1000ms default timeout.

Not in this release

Predictive pace notifications and ceiling usage still do not see monthly quotas. Follow-up PR next.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	ceiling	b14a2b9	Commit Preview URL Branch Preview URL	Aug 11 2026, 01:59 AM

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e38cb68d-a063-454f-bb76-0d478fa8fb89

📥 Commits

Reviewing files that changed from the base of the PR and between 5b90a13 and b14a2b9.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (6)

• CHANGELOG.md
• apps/desktop-tauri/package.json
• apps/desktop-tauri/src-tauri/Cargo.toml
• apps/desktop-tauri/src-tauri/tauri.conf.json
• rust/Cargo.toml
• version.env

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Automated review

No blocking issues found.

_{For coding agents: fix BLOCK and FIX IF QUICK findings now; everything else is tracked or informational; never exceed one CodeRev fix round per PR.}

_{Advisory. Findings generated by grok-subscription and muse-spark-1.2-contributor, each filtered through a 3-vote deepseek-v4-flash refutation panel with the changed code in evidence.}