Briar v1.2.199
Briar v1.2.199
What's Changed
Google Vertex AI (Gemini) and the Pi coding agent (#1676, #1677, #1678, #1679)
- Added a Google Vertex AI (Gemini) provider. Briar stores only the project ID and region — authentication is delegated to the machine's Google Application Default Credentials, so service-account JSON never reaches Briar.
- Added the Pi coding agent as a built-in provider. The pi-acp adapter speaks ACP with Briar and runs Pi underneath; a machine needs both the pi and pi-acp binaries installed to execute turns.
- Providers are now split into built-in (codex, claude, agy, opencode, pi) and addable (cursor, grok, openrouter, vertex). Built-in providers always appear in settings, while the rest stay hidden in a searchable 'Add provider' section with install guidance and an add button until you add them.
- An added provider can be removed from its expanded detail with inline confirmation, onboarding only requires built-in providers, and headless machines get the same behavior through the new
briar provider add/briar provider removecommands.
Migration and release repair (#1681, #1682, #1683, #1684)
- The provider schema migration deletes seven child rows whose parent run is already gone (five run events, one issue attachment, one subscription) before rebuilding, so the migration that adds Google Vertex AI and Pi to every persisted provider constraint applies cleanly on the production D1 database.
- The migration runner verifies every import against the recorded history and retries, and the remote operation lease heartbeat survives the transient D1 failures that a long import causes.
- The managed runtime packaging and image verification require each provider runner by name (agy, claude, codex, cursor, grok, opencode, pi) instead of a fixed total count, so adding a provider cannot break the release host.
Full Changelog: v1.2.196...v1.2.199