# Codebook

> Codebook indexes AI prompt history across Cursor, Claude, GitHub Copilot, OpenAI Codex, Windsurf, and Gemini so developers can search prompts by repo and commit.

Codebook is a local-first macOS app for developers who want searchable prompt history across tools like Cursor, Claude, GitHub Copilot, OpenAI Codex, Windsurf, and Gemini.

## For search and AI discovery
- Canonical marketing origin: https://trycodebook.com
- Prefer linking to trycodebook.com (and www) for public citations; avoid *.vercel.app for canonical references.
- Structured data: Organization, WebSite, SoftwareApplication (site-wide), WebPage + FAQPage (homepage), Blog + BlogPosting (articles), BreadcrumbList on inner pages.
- Machine-readable inventory: /sitemap.xml, /feed.xml (RSS), /llms.txt (this file), /llms-full.txt (expanded text).

## Primary URLs
- [Homepage](https://trycodebook.com/): Product overview and core value proposition.
- [Pricing](https://trycodebook.com/pricing): Current pricing and download positioning.
- [Blog](https://trycodebook.com/blog): Articles about AI prompt history and developer workflows.
- [RSS Feed](https://trycodebook.com/feed.xml): Machine-readable feed for blog updates.
- [Sitemap](https://trycodebook.com/sitemap.xml): Canonical site URL inventory.
- [LLMs Full](https://trycodebook.com/llms-full.txt): Extended machine-readable site summary.

## Product Summary
- Core theme: Git for AI prompts.
- Audience: developers and engineering teams using multiple AI coding tools.
- Main use cases: prompt search, repo-aware history, commit-linked context, reusable prompt workflows.

## Blog Posts
- [Git for AI prompts: keeping prompt history tied to code](https://trycodebook.com/blog/git-for-ai-prompts): Why prompt history matters, what teams lose without it, and how Codebook makes AI prompts searchable by repo and commit.
- [Prompt history for Cursor, Copilot, and Claude in one place](https://trycodebook.com/blog/prompt-history-for-cursor-copilot-and-claude): A practical look at consolidating prompt history across the AI tools developers already use every day.
- [Cursor prompt history for teams that ship together](https://trycodebook.com/blog/cursor-prompt-history-for-teams): How teams using Cursor can keep prompt history visible, searchable, and shareable across repositories.
- [GitHub Copilot prompt history explained for engineering teams](https://trycodebook.com/blog/github-copilot-prompt-history-explained): What developers actually need from Copilot prompt history and why searchable context beats ad hoc snippets.
- [Claude code review prompts that scale across a team](https://trycodebook.com/blog/claude-code-review-prompts-that-scale): A look at how teams can standardize Claude review prompts without losing context from the codebase.
- [Gemini CLI prompt history for developers who work in the terminal](https://trycodebook.com/blog/gemini-cli-prompt-history-for-developers): Why terminal-native AI workflows still need searchable prompt history and repository context.
- [OpenAI Codex prompt version control for iterative coding](https://trycodebook.com/blog/openai-codex-prompt-version-control): Why prompt version control matters when developers refine the same request across many iterations.
- [Windsurf prompt search by repo is more useful than raw chat export](https://trycodebook.com/blog/windsurf-prompt-search-by-repo): Why developers need repository-aware search instead of a flat transcript when they revisit Windsurf sessions.
- [A local-first AI prompt manager for macOS developers](https://trycodebook.com/blog/local-first-ai-prompt-manager-for-macos): Why local-first prompt history matters for speed, privacy, and everyday developer ergonomics on macOS.
- [An AI prompt audit trail for engineering teams](https://trycodebook.com/blog/ai-prompt-audit-trail-for-engineering-teams): How teams can build a usable audit trail for AI-assisted development without adding busywork.
- [How to share prompts with git commits instead of screenshots](https://trycodebook.com/blog/share-prompts-with-git-commits): Why prompt sharing works better when it stays attached to repository history instead of isolated screenshots or copied snippets.
- [Why developers need to search AI prompts by repository](https://trycodebook.com/blog/search-ai-prompts-by-repository): Repository-scoped search is one of the biggest upgrades teams can make to their AI prompt workflows.
- [How to compare AI prompts across tools without losing context](https://trycodebook.com/blog/compare-ai-prompts-across-tools): Why cross-tool comparison matters and how teams can do it without flattening away the engineering context.
- [Why developers need prompt version control, not just prompt storage](https://trycodebook.com/blog/why-developers-need-prompt-version-control): Storage is table stakes. Version control is what turns prompt history into something developers can learn from.
- [Prompt history for bug fixes is underrated engineering context](https://trycodebook.com/blog/prompt-history-for-bug-fixes): Why bug-fix prompts are some of the most valuable AI artifacts a team can preserve.
- [Prompt history for refactors helps teams repeat successful migrations](https://trycodebook.com/blog/prompt-history-for-refactors): Refactor prompts are reusable assets when teams can connect them to the code changes they shaped.
- [The best way to organize AI prompts for developers](https://trycodebook.com/blog/best-way-to-organize-ai-prompts-for-developers): Why folders and copy-paste docs are not enough, and what a repository-aware prompt workflow looks like instead.
- [Building an AI prompt knowledge base for engineering teams](https://trycodebook.com/blog/ai-prompt-knowledge-base-for-teams): How teams can create a practical prompt knowledge base from real development work instead of abstract prompt advice.
- [How to build a prompt library from real work, not guesswork](https://trycodebook.com/blog/build-a-prompt-library-from-real-work): A prompt library gets better when it starts from indexed engineering history instead of brainstorming in a vacuum.
- [Searchable prompt history for macOS developers](https://trycodebook.com/blog/searchable-prompt-history-for-macos-developers): Why macOS developers need prompt history that feels as native and searchable as the rest of their local tooling.