Skip to content

VibeAround CLI 0.0.7

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Jul 03:02
va-v0.0.7
254fd20

Highlights

  • IM va new and /new now start with the channel's latest configured agent and profile instead of inheriting the previous thread selection. This addresses #247.
  • Queued channel conversations now stay active until the route queue has fully drained, so rapid follow-ups no longer receive a premature completion signal.
  • Successfully queued channel output is now forwarded to the channel plugin before the matching ACP prompt response completes.
  • Concurrent settings, profile, workspace, and launcher updates now preserve unrelated changes through serialized atomic writes.
  • Active agent threads are retained by a soft-limited warm pool with pressure eviction, preserving session continuity without fixed per-route idle timers.

Fixes

  • Stop and cancel now wait for the agent's real ACP result; an unresponsive agent is shut down after a 30-second cancellation grace period.
  • Web and TUI history, sessions, activity, and permission requests are now isolated by the complete route.
  • Saved local authentication is now reused only for the exact recorded 127.0.0.1 server port.

Payloads

  • macOS darwin-arm64: locally built, signed, notarized, verified, and uploaded.
  • Linux x64, Windows x64, and web payloads: built and uploaded by CI.

npm

  • Published @vibearound/cli@0.0.7 (npm install -g @vibearound/cli@0.0.7).

Compatibility

  • Custom WebSocket clients that consumed prompt_done must switch to 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.

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.
Assets 6
Loading