You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Web, TUI, and IM conversations now share one accurate turn lifecycle: a route becomes idle only after its complete queue has drained.
IM va new and /new now start with the latest configured channel agent and profile instead of retaining the previous thread selection. This addresses #247.
Concurrent settings, profile, workspace, onboarding, and launcher updates now preserve unrelated changes through one atomic settings owner.
Managed channel plugins are now installed from catalog-pinned revisions through a staging directory, leaving the current installation intact if preparation fails.
Channel onboarding now follows each plugin's declared authentication method, including phone pairing-code onboarding, and every channel instance receives isolated runtime state and cache directories.
Active agent threads are retained by a soft-limited warm pool with pressure eviction while preserving session continuity.
Fixes
Successfully queued stdio notifications are now forwarded to the channel plugin before the matching ACP prompt response completes.
Stop and cancel now wait for real agent settlement, with forced shutdown after a 30-second cancellation grace period.
Web and TUI history, sessions, activity, pending messages, and permission requests are isolated by the complete route.
Saved local authentication is reused only for the exact recorded http://127.0.0.1:<port> endpoint.
Compatibility
Custom WebSocket clients must replace prompt_done handling with turn_status and treat active: false as the public completion boundary.
Custom stdio channel plugins that consumed va/prompt_done must use the ACP prompt response as their completion boundary; @vibearound/plugin-channel-sdk@0.6.6 implements this contract.
Existing channel plugins remain compatible; custom plugin builds should use @vibearound/plugin-channel-sdk@0.6.6.
Full Settings API replacements require a current ETag; PATCH remains the preferred incremental update path.
No settings or workspace data migration is required.
Packages
macOS Apple Silicon DMG: locally built, signed, notarized, verified, and uploaded.
Windows x64 Setup EXE, MSI, and portable ZIP: built and uploaded by CI.
Linux x64 AppImage and deb: built and uploaded by CI.
Known Limitations
Channel output remains a non-persistent, bounded best-effort queue. Output rejected because the queue is full or the plugin runtime disconnects is logged but not replayed.
The Windows QQBot crash report in #250 remains open and is not claimed as fixed.
Phone pairing-code wiring is included, but real-device WhatsApp linking still depends on the upstream provider implementation.
On Windows, replacing a running plugin can fail; VibeAround restores the previous installation so the runtime can be stopped before retrying the update.
