Back
GoogleAntigravity
Voice dictation, embedded ripgrep code search, status line cost metrics, and UTF-8 encoding fixes
AI summary
Written by AI from the official notes. Check them for exact details.New voice dictation feature added along with improved code search and cost tracking metrics.
- Introduced
/voicedictation for speech-to-text input. - Added cost tracking to monitor token spending in sessions.
- Bundled embedded
ripgrepfor faster and consistent code searches. - Improved permission suggestions for script runners.
- Fixed UTF-8 encoding issues in file edits and responses.
Why it matters: Users who rely on voice input and code search will benefit from these enhancements and fixes.
Full release notes11 changes
Adds /voice dictation with mic-serve SSH forwarding, embedded ripgrep for consistent agent code search, custom status line cost tracking, granular script runner permission suggestions, and UTF-8 file editing and MCP error fixes.
- Added
/voicedictation to transcribe speech directly into the prompt withf5and/voicetoggle shortcuts, introduced themic-servesubcommand to forward a local microphone over SSH, and improved quota messaging for concurrent stream limits. - Added a
costfield to the status line data model, exposing unrounded estimated session costs to track running token spend. - Improved agent code search by bundling an embedded
ripgrepbinary instead of invoking external system binaries, increasing search performance and cross-platform consistency. - Improved the
always-proceedpermission mode to auto-approve MCP tool calls and page reads without prompting. - Improved allow-always permission suggestions for script runners (
npm run,yarn,pnpm,cargo run) by scoping approvals to specific script names. - Improved conversation titles by generating them automatically on creation, providing meaningful session names in the resume picker.
- Improved error diagnostics when an MCP server configured for Google credentials cannot locate Application Default Credentials (ADC).
- Fixed corrupted file edits in documents containing non-ASCII text (CJK characters, accented letters, emoji) caused by inexact offset matches producing invalid UTF-8.
- Fixed sessions stalling mid-response when a tool result or file diff contained invalid UTF-8.
- Fixed file writes being reported as failures after successfully saving to disk, preventing unnecessary agent retry loops on large files and notebooks.
- Fixed precedence resolution so explicitly configured skill and plugin paths take priority over automatically discovered customizations during name collisions.