Introduction

What PCR.dev is and how it works

✦

Latest: v0.2.9 · TUI improvements — addictive-grade close-outs, vim-style yank in pcr show, and a one-row context strip on the detail pane. [Release notes →](https://github.com/pcr-developers/cli/releases/tag/v0.2.9)

PCR.dev is a platform for Prompt & Code Reviews (PCRs). When humans build software for humans, the prompts powering each AI-assisted change deserve review just like the code they produce.

PCR captures the prompts you send to Cursor, Claude Code, and VS Code Copilot, attaches them to the git diff each prompt actually produced, and surfaces the result as a reviewable artifact alongside your pull request. Think of it as a commit history for the prompt layer — the reasoning behind every chunk of AI-assisted code.

What's new in v0.2.9

  • –Unified close-outs: every state-changing command (init, bundle, pull, push) now exits with the same ▲ done · 2.1s shape and a one-line next-step hint. No more dead air after a long push.
  • –`pcr show` polish: vim-style y yanks the focused draft/bundle id, o opens the focused bundle's review URL (or the draft's project page) — both panes.
  • –Context strip in `show`: a 1-row strip under the header shows project · ⎇ branch · ◎ N drafts · ↑ Xm ago and refreshes every 2s. No more bouncing back to pcr status for orientation.
  • –Rich `--help` everywhere: pcr <cmd> --help now renders the same purpose / when-to-use / examples / see-also / docs block the interactive pcr help browser uses.
  • –`pcr log` upgrade: the drafts section groups by session, color-codes per source (cursor cyan, claude magenta, vscode yellow), and aligns HH:MM timestamps for readability.

Key concepts

ConceptDescription
ProjectA codebase you've registered with pcr init. Prompts authored against that directory get attributed to this project.
SessionA single conversation with an AI tool. Prompts within a session share a session_id.
DraftA captured prompt that hasn't been bundled yet. Lives in ~/.pcr-dev/drafts.db.
BundleA named, sealed group of drafts. The unit of review on PCR.dev.
SourceThe AI tool that captured the prompt: cursor, claude-code, vscode, or mcp.

Capture modes

  • –File watcher (pcr start): passively monitors session transcripts written to disk by Cursor, Claude Code, and VS Code Copilot. Zero changes to your editor setup.
  • –MCP server (pcr mcp): an active integration where the AI tool calls PCR directly via the Model Context Protocol. Gives richer per-call metadata.
✦

Most users should start with the file watcher. It captures everything automatically and your prompts are ready for review when you are.

Next →Quickstart