Stop re-explaining your preferences every session. taste-capture hooks into git, mines your edits to AI-generated code, and automatically injects your constraints into future AI sessions.
Every time you change AI-generated code, that's your taste speaking. taste-capture mines that signal automatically.
One command installs a post-commit hook. Works with any editor, any AI assistant.
Use Cursor, Claude, Copilot — whatever you use. taste-capture watches in the background.
When you edit AI-generated blocks, a local model analyzes the diff and extracts the rule you applied.
CONSTRAINTS.md is automatically prepended to your system prompt next time. AI already knows your rules.
Automatically inferred from your actual edits — not written by you.
Never create barrel exports (index.ts re-exports). Import directly from source files.
Inferred from 3 edits · 4 days agoUse 2-space indentation. Never mix tabs and spaces. Trailing newline required.
Inferred from 7 edits · 2 weeks agoReact components: PascalCase filenames. Hooks: camelCase with `use` prefix. No default exports from hooks.
Inferred from 5 edits · 1 week agoTests live alongside source files as `*.test.ts`, not in a `/tests` directory. No mocking the database.
Inferred from 2 edits · 3 days agoLocal processing means zero marginal cost. Pay only for team sync and automation.
Full local pipeline. Your constraints stay on your machine.
Share constraints across your whole team. One repo, one voice.
Auto PR review on every pull request. Taste enforced at scale.
No. The free tier runs entirely locally using a local Llama-3-8B model. Diffs are analyzed on your machine, constraints stay in your repo. Nothing is sent to our servers.
It doesn't need to. The git hook tracks staged changes before and after your manual edits. The delta — what you changed relative to the AI's output — is the signal. You mark AI-assisted commits with a flag (or we auto-detect Cursor/Copilot metadata).
All of them. taste-capture is AI-agnostic — it works at the git layer, not the IDE layer. Claude Code, Cursor, GitHub Copilot, Codeium — if you commit the code, we can analyze the diff.
Llama-3-8B running locally via Ollama. No API keys, no internet required. Cloud Sync and Managed tiers use the same local model — your diffs never leave your machine even on paid plans.
Yes. Run taste-capture edit to open your CONSTRAINTS.md in your editor. Add, remove, or rewrite any constraint. Changes sync to your team immediately on Cloud Sync+.
On Cloud Sync, constraints are stored in our API (SQLite, keyed by repo URL). Every team member's local hook fetches the latest constraints before each session. Merges are last-write-wins per constraint ID.