Skip to content
Codebook logo

Codebook

Scans prompts sent to Cursor, Claude, Copilot and Codex and organizes them by repo and commit for browsing, searching and sharing.

Maintained

Developer toolsFor developersSearch
trycodebook.com ↗Launched on Product Hunt · May 3, 2026
Open trycodebook.comAlternativesSet it up for my teamIs Codebook yours? Claim the card →
At a glanceswept Oct 18, 2026

≈ 14visits/mo

Emerging · estimate, read Oct 19, 2026

For
Developers who use Cursor, Claude, Copilot or Codex and want their prompt history organized by repo on macOS.
Activity
Maintainedsite updated 6 months ago
Runs as
Desktop app
Used for
  • Search past AI prompts by describing what you need
  • Share prompt threads with teammates by commit
  • Review prompt history for each repo and commit
Worth knowingcomputed from what we read · each with its source
Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Codebook with

Pick up to two.

All 10 alternatives to Codebook →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Codebook for?

Sign in to leave a note
Questions this page answers
  • What is Codebook?

    Scans prompts sent to Cursor, Claude, Copilot and Codex and organizes them by repo and commit for browsing, searching and sharing. It is listed in the Atlas under Developer tools.

  • Who is Codebook for?

    Developers who use Cursor, Claude, Copilot or Codex and want their prompt history organized by repo on macOS.

  • Do people use Codebook?

    Emerging: ≈ 14 visits/mo · estimate, 2026-10.

  • Is Codebook still maintained?

    Maintained: site updated 6 months ago.

  • What are alternatives to Codebook?

    In Developer tools, by use: One, Clor, CloudPloy, PolicyLayer, CLSkills Hub, Fulcra.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk