v0.7.1

v0.7.1 — Stability & Reliability

---

Improvements

• Pi agent engine 0.56.2 — updated from 0.55.0 with GPT-5.4 support (openai, openai-codex, azure-openai-responses), gpt-5.3-codex fallback for GitHub Copilot, Mistral native conversations integration, and OpenCode Go provider support
• Automation session titles — automation-initiated sessions now use the automation's name as the session title instead of a truncated prompt snippet; AI title generation is skipped for these sessions (861a597, 79b9ebb)
• CLI validate-server — added --disable-spinner / --no-spinner flag for CI environments; validate-server auto-bootstraps a temp workspace and LLM connection when none exist (84b3378, 1ea478d)

Bug Fixes

• Branch creation reliability — fixed a race condition where ERR_STREAM_WRITE_AFTER_END from the SDK's ProcessTransport left branch creation in an infinite loading state; added 15s timeout with interrupt-based cancellation for hung preflight queries (8ff3710, 0dc1d2e)
• Base64 false positives — replaced heuristic base64 detection with a strict canonicalization pipeline (charset regex, normalize, auto-pad, roundtrip verify) to eliminate false positives on English text and other non-base64 content. Fixes #344
• Cross-machine session recovery — persist cleared sdkSessionId on session expiry recovery, preventing repeated stale-ID failures when syncing sessions across machines. Fixes #342
• Spawn ENOENT during auto-update — detect app bundle swap during auto-update using structured error fields + regex fallback, with bounded single retry. Fixes #268
• Duplicate LLM connections on re-auth — fixed stale React closure in handleReauthenticateConnection that generated new slugs (e.g. chatgpt-plus-2) instead of reusing existing ones; added updateOnly guard on the server side (b735f9d)
• Codex token expiry — Pi/Codex auth-expiry errors now route through the typed_error auth-retry pipeline instead of appearing as red error messages; global refresh mutex prevents cross-session token refresh races (1d85bc8)
• Settings "Check Now" stuck at 0% — unified autoDownload policy between Settings check and native menu so download-progress events arrive correctly (b8ad8c4)