VibeAround v0.6.9: per-agent launch commands, IM session fixes, and preview polish
VibeAround v0.6.9 is out.
This release is about making local coding agents easier to launch, resume, and reach from web/IM surfaces.
What changed:
- Added per-agent launch settings, so each agent can have custom terminal arguments and agent-protocol arguments inserted into the generated launch command
- This covers Codex sandbox / permission-mode / YOLO-style workflows without making the feature Codex-only
- Improved IM session behavior: IM can resume the latest session without replaying old message playback, with a setting to control auto-continuing the last IM session
- Tested preview and Markdown preview flows across direct launches, bridged profiles, web chat, and multiple agents
- Added a copy button for browser pairing commands
- Fixed Claude Code launches for token-based auth by restoring the expected auth-token environment variable shape
- Published signed and notarized macOS DMG, plus Windows installer/MSI/portable ZIP and Linux AppImage/deb
Release:
https://github.com/jazzenchen/VibeAround/releases/tag/v0.6.9
If you use VibeAround with Codex, Claude Code, Pi, Gemini, or bridged model profiles, this should make the launch path a lot more transparent and customizable.
Replies
The per-agent launch args is the kind of fix you only think of after living with several agents at once. Reaching a local agent from a web or IM surface is the part I keep wanting and rarely see done cleanly. Is the IM bridge tied to one agent or can it route to whichever one is live?
Per-agent launch settings are a smart direction. Once people run different coding agents for different tasks, the workflow needs more than one generic launch command — each agent needs the right context, flags, and recovery path to stay useful.