Git for Prompts Logo
Git for Prompts
Open-source prompt version control

Git for your AI prompts

Save versions of your AI prompts, test changes before shipping, and roll back if something breaks. Works completely offline with your local CLI or synced to the cloud.

Open cloud dashboard →

Open source • Works offline with SQLite • Your keys stay on your machine

gitforprompts.com/dashboard
Workspace Studio · Git for Prompts
gitforprompts

Prompt RepositoriesLocal & Cloud Synced

Manage, version, diff, and evaluate atomic prompt bundles.

+ Create New Prompt
Active Prompts
3
Tracked in local SQLite
Total Commits
12
Immutable snapshots
Evals Passed
53/54
98.1% pass rate
API Credentials
2
SHA-256 hashed
Prompt NameDescriptionVersionTest SuiteVisibilityActions
security-audit-v2Automated vulnerability scanning and CWE classification for Node & Python apps.v312/12 (100%)PrivateOpen studioEdit bundleView diffRun evals
customer-support-agentTone-calibrated customer response generator with strict refund guardrails.v523/24 (96%)PublicOpen studioEdit bundleView diffRun evals
code-reviewer-proStrict TypeScript and Rust code review agent with security audit rules.v418/18 (100%)PrivateOpen studioEdit bundleView diffRun evals
Why version control

Prompts break when you treat them like raw text

When prompts are hardcoded in application files, small edits break formatting with no way to undo bad changes. Git for Prompts gives you clear commit history, side-by-side diffs, and test suites.

Without version control

Hardcoded strings

Prompt edits pushed straight to code without test runs, schema checks, or rollback points.

With Git for Prompts

Versioned prompts

Snapshots saving your prompt template, model choice, and output format in a local SQLite file.

100%
Offline & Local First
0
Cloud Lock-in
<10ms
Local Eval Speed
MIT
Open Source License
The workflow loop

A local-first engine for prompt engineering

From initial draft to automated evals and team sync.

01

gitforprompts init

Initialize a local SQLite repository directly inside your project folder.

Local setup →
02

gitforprompts run & eval

Run local evaluations with your environment API keys against real test cases.

Run tests →
03

gitforprompts push

Sync approved versions to the team dashboard or deploy over the REST API.

Cloud sync →
PROMPT EVALUATION SUITE

Test & Evaluate prompt bundles before pushing

Run test cases against dual AI models (Groq & OpenRouter). Validate variable interpolations and strict Zod JSON output schemas.

  • Dual-Model Benchmark (Groq Llama 3.3 + Claude 3.5)
  • Strict Zod Schema Output Validation
  • Variable Interpolation ("{{name}}") Testing
  • Zero Key Storage — Direct User Provider Keys
Run Local Evals →
gitforprompts run test-suite --all
88/88 PASSED
✓test-case-security-audit

Input: SQL Injection payload • Score: 100%

12ms
✓test-case-json-schema-match

Zod validation: Object schema verified

18ms
✓test-case-variable-interpolation

Interpolated "{{codeSnippet}}" successfully

9ms
Core capabilities

Built for developers who ship AI to production

Version control your prompts, model settings, and structured outputs without cloud lock-in.

01

Saved versions

Every save creates a new version with full change history. Roll back instantly or view changes side-by-side.

02

Offline SQLite storage

The CLI runs completely offline in your terminal using local SQLite. No cloud account required.

03

Everything versioned together

Keep your system prompt, model settings, and response schemas saved together in one place.

04

Secure team sync

Push prompt versions to the web dashboard and serve them to your apps using secure API keys.

COMMAND LINE INTERFACE

Control your prompts directly from your terminal

Run evaluations, inspect diffs, and push approved prompt versions directly from your terminal. Pure TypeScript shared between the CLI and web dashboard.

Explore CLI Docs →
zsh — gitforprompts diff

$ gitforprompts diff prompt-v1 prompt-v2

--- prompt-v1 (2026-08-06)

+++ prompt-v2 (2026-08-07)

- systemPrompt: "You are a helper."

+ systemPrompt: "You are a strict code reviewer."

+ tools: ["run_static_analysis", "lint_check"]

“Treat prompts like production code: version them, diff them, and test them in your terminal before they hit production.”
KW
Karan Wakhare
Creator • Git for Prompts
About Git for Prompts

Version control built for AI engineering

Prompts control how AI apps behave, but most teams still keep them scattered across code files. Git for Prompts brings git-like version control to your prompts: clean version history, side-by-side diffs, automated testing, and local storage.

01

Local-first workflow

You never need an internet connection. The CLI saves prompts in a local SQLite database inside your project (.gitforprompts/). Create prompts, save versions, and run tests completely offline.

02

Safe version history

When syncing prompt versions across a team, database locks ensure version numbers never collide or overwrite someone else work.

03

Your keys stay private

We never store your AI API keys. Tests run using your own local environment variables, so your secrets never leave your machine.

04

Built for developers and AI agents

Built for both human developers and AI coding assistants. Supports clean schemas, standard API endpoints, and direct CLI commands.

100% open source • MIT license

Built in public. We welcome contributions from developers, researchers, and AI engineers.

Developer FAQ

Everything you need to know about Git for Prompts.

Does Git for Prompts store my LLM API keys?−

No. Local evaluations run in your terminal using your local environment variables. On the cloud platform, API credentials are stored as non-reversible SHA-256 hashes.

Git for Prompts Logo

Start versioning your prompts locally in seconds

Run `$ npx gitforprompts init` in your project folder. Complete history, works offline, zero setup.

Get started free →