Release · CLI · Proxy

VibePod CLI 0.2: proxy logging and early container fixes

VibePod CLI 0.2.0 introduced session and HTTP capture, proxy support, log UI startup, and source-container attribution. The 0.2.1 patch followed with container credential and startup fixes.

2026-02-23 · Release · CLI · Proxy

What shipped in 0.2.0

VibePod 0.2.0 was the first observability-focused release. It added capture of agent sessions and messages, then extended that into HTTP request/response capture through a proxy flow.

The release also introduced the proxy command group, changed the quick UI alias from vp logs ui to vp logs start, added default images for the Datasette log UI and proxy containers, and recorded source-container attribution for proxied traffic.

A follow-up commit in the same release line handled proxy file-permission issues and added tests around proxy permissions, making the logging stack safer to run from local Docker containers.

What 0.2.1 fixed

The 0.2.1 patch release tightened credential handling for Auggie and Copilot containers and added startup fixes for Mistral Vibe / Devstral containers.

Example commands

The 0.2 line introduced the local logging/proxy workflow. Users could start the dashboard, run an agent, and inspect captured activity locally.

vp logs start
vp run claude
vp logs status
vp logs stop

# 0.2.1 focused on container fixes, so existing run commands became smoother:
vp run auggie
vp run copilot
vp run devstral

Related links