new open source project: github.com/omeedcs/vibetr… one of the biggest problems i’ve run into during a Anthropic Claude coding session (all love @bcherny) :P... is losing track of what’s actually happening.... and having no deep control over it. this has forced me to nuke entire sessions more times than i’d like to admit.when claude is making 20–40 edits across your codebase, everything starts to blur: which files changed? in what order? did that refactor actually hit every call site? did it quietly overwrite something critical? by the time you notice something’s off, you’re already deep in a mess that’s easier to throw away than untangle. so i built vibetracer. it’s a rust TUI that sits alongside your AI coding session and records every file change in real time. everything is content-addressed, every edit is logged with full diffs, and you get a timeline you can scrub through like a video editor - edit by edit, file by file. vibetracer analyzes your session as it happens. blast radius detection catches partial refactors where only some files were updated. invariant sentinels flag when cross-file rules break. a constants watchdog alerts you when critical values change.and you can surgically rewind a single file - or even a single edit - without touching anything else. AI coding needs an observability layer. right now we’re flying blind, and the only recovery tools are ctrl+z or git reset. vibetracer is essentially the missing undo button. it is very early stage, please feel free to contribute.
