Version Control for AI Coding

Prompts as source code

Today: Developers write code and track changes with git

Tomorrow: Developers write prompts and track changes with PVC

PVC Mascot - A modern stoic philosopher holding a version token

The AI Session Blob Problem

After 5-10 Codex prompts, you're left with chaos.

One massive git diff
No idea which prompt caused which change
No way to revert specific AI changes
Lost context between sessions

You're not alone — 2,100+ developers feel this

"

oh man this is definitely not just a you problem, been wrestling with the same thing

— Developer on r/codex
"

You're not alone. What you're describing is the exact 'AI session blob' problem: 5–10 prompts later you have one big diff, but no causal trail.

— r/vibecoding
"

The deeper issue isn't Git. It's that AI work happens as a series of micro-decisions, but you're recording it as one macro-change.

— r/vibecoding
PVC solves this.

What is PVC?

Git for AI coding sessions. PVC automatically tracks everything.

Real-Time Tracking

See prompts and responses as they happen. No waiting, no manual logging.

Per-Prompt Git Diffs

Know exactly which prompt changed which files. Each prompt gets its own git diff.

Zero Setup Overhead

One command. Works automatically. No code changes required.

Session Timeline

Full audit trail of every AI coding session. Perfect for debugging and learning.

Team Knowledge Sharing

Share sessions via git. Teammates see exactly how you solved problems.

Revert Specific Changes

Undo one prompt's changes without losing everything else.

Use Cases

Real problems, real solutions.

Debug Faster

Problem

"Auth is broken after 5 Codex prompts"

Solution
pvc show session-123
# See: Prompt #3 changed auth.ts incorrectly
# Revert just that change
Result

Debug in 10 seconds instead of 10 minutes.

Learn from History

Problem

"How did I refactor this component last time?"

Solution
pvc list --search "refactor"
# See: Effective prompts from past sessions
# Reuse proven patterns
Result

Build your personal library of effective prompts.

Collaborate Better

Problem

"How did you build this feature?"

Solution
# Share: .pvc/runs/session-123.json via git
# Teammate sees: exact prompts + responses + changes
Result

Knowledge transfer without meetings or Loom videos.

Audit & Compliance

Problem

"What did AI change in our codebase last quarter?"

Solution
pvc list --date 2025-Q1
# Export: Complete audit trail
Result

Track all AI-generated code for compliance.

Manual Workarounds vs. PVC

Without PVC
With PVC
Commit after every prompt (kills flow)
Automatic tracking, zero friction
Lost context between sessions
Full session history, searchable
"Which prompt broke this?" → 2 hours
"Which prompt broke this?" → 10 seconds
Manual notes in commit messages
Structured prompts + responses + diffs
Can't revert specific AI changes
Cherry-pick any prompt's changes
No learning from past sessions
Build prompt library over time

Not Just Another Tool

PromptLayer, LangSmith, Helicone → Version prompts for AI products
PVC → Version prompts for AI coding

Other tools help you build AI apps. PVC helps you code with AI.

Real-Time Demo

Everything happens automatically. You just code.

Terminal 1: Codex
$ codex
> write a login function with email validation

> add password strength requirements
Terminal 2: PVC Watch
$ pvc watch
✓ Prompt logged: "write a login function..."
✓ Response captured
✓ Files changed: auth.ts (+34 lines)

✓ New prompt
✓ Git diff from previous prompt
✓ Updated session timeline

VS Code ExtensionComing Soon

📂 PROMPT VERSION CONTROL
  
  🟢 Active Sessions
    └─ Codex Session (in progress)
       ├─ [10:00] "write a login function"
       │   └─ auth.ts (+34, -0)
       ├─ [10:05] "add validation"
       │   └─ auth.ts (+15, -2)
       └─ [10:08] "make accessible" ← LIVE
           └─ Pending git diff...

What Developers Say

"

Finally! I've been doing manual commits after every prompt and hating it.

— Early beta tester
"

This is what I've been looking for. Debugging AI code just got 10x easier.

— Software Engineer
"

Game changer for our team. We can now review AI-generated code properly.

— Tech Lead

FAQ

The Future of Coding is Here

In a world where prompts generate code, tracking prompts IS tracking development. PVC is infrastructure for the AI coding era.

npm install -g pvc

Requirements

Node.js 16+Codex CLIGit (recommended)
Built with v0