Story

I mostly built this for myself.

After a few long coding-agent sessions(Claude Code, Gemini CLI, Codex), I'd sometimes get to a point where something felt "off." The output looked reasonable, but it wasn't quite aligned with what I originally intended. And I couldn't easily tell when that shift happened without scrolling through a huge transcript.

So I put together a small local tool to make that drift visible.

Vibe Audit tries to surface when an agent continues the same line of work, starts a new phase, or quietly pivots. It builds a rough baseline from the user’s prompts, tracks session events, and then shows:

- Phase shifts(continuation/new_phase/pivot) - An alignment score with a short rationale - A timeline view of how context evolves over time

It runs entirely locally and hooks into CLI sessions.

Quick start: npx vibe-audit

A few notes: 1. It’s still beta. Phase detection and alignment scoring depend partly on model interpretation. 2. Different CLIs emit slightly different event formats, so behavior isn't perfectly identical across providers. 3. If a session is force-stopped mid-stream, the last turn can be incomplete. 4. It's currently designed for personal/local workflows rather than team-wide infrastructure.

I'm sharing this early to see whether intent-drift detection is actually useful in real-world workflows, or if I'm just over-optimizing my own frustration.