VibeAround
Keep your vibe coding agents around.
Start new thread
Jazzen Chen

VibeAround v0.6.10: Gemini OAuth, safer bridge media handling, and matrix coverage

by
VibeAround
•

VibeAround v0.6.10 is out.

This release focuses on bridge reliability, Gemini setup, and cleaner provider workflows.

What changed:

- Added Gemini Google OAuth connection support and native Gemini upstream routing.

- Upgraded API bridge media handling through va-ai-api-bridge 0.1.4 from crates.io.

- Added safer image/file omission for text-only target models, so a conversation can keep going even when a target model cannot read an attachment.

- Fixed the DeepSeek Anthropic-style tool_use / tool_result bridge path.

- Cleaned up profile setup, model defaults, and proxy wording.

- Improved handover pickup/resume robustness.

Validation:

- cargo test -p server: 86 passed.

- bun run ws:matrix: 98 cases passed across websocket provider/protocol/agent combinations.

- desktop-ui and web production builds passed.

- macOS arm64 DMG is signed, notarized, stapled, and accepted by spctl.

Download:

https://github.com/jazzenchen/VibeAround/releases/tag/v0.6.10

39 views

Add a comment

Replies

Best
Tehreem Fatima
Congrats on the v0.6.10 release! Handling multi-model routing and API bridges can get messy quickly, so updates focusing on bridge reliability and native Gemini OAuth support are huge wins. I particularly love the 'safer image/file omission for text-only target models' addition—that’s a brilliant way to prevent conversation crashes when an unsupported attachment is dropped. Great work on getting all those cargo and websocket tests passing cleanly too!
Jazzen Chen

@tehreem_fatima5 Thanks Tehreem! The bridge layer is exactly where the rough edges show up first, especially when a conversation moves across providers with different media/tool support. The safer omission path is intentionally practical: keep the conversation alive, make the limitation visible, and avoid failing the whole session just because one target model can’t consume an attachment.

Tehreem Fatima
@jazzenchen Thanks for the detailed breakdown, Jazzen! That 'safer omission path' is a brilliant design choice. From a user experience standpoint, nothing is more frustrating than having an entire session drop or fail just because of one unsupportable attachment. Keeping the conversation alive while making the limitation visible is the most practical way to handle multi-model friction. Really smart engineering!