Skip to content
carafe logo

carafe

Captures your local AI coding sessions so you can search them, replay them and hand them off to another agent.

Actively maintained

carafe: data, price, alternatives
  • Is it safe? We have not read the data policy of carafe yet. Read it on the official site before you upload anything.carafe.sh ↗
  • Is it free? We have not read the prices of carafe yet; they are next in our queue. Until then, the official site has them.carafe.sh ↗
  • What else does this? CursorfreeEgnyteOpenCodefreeSee ↓
At a glancechecked Oct 26, 2026

not read yet

Use

For
developers using Claude Code or Codex who want past sessions kept on their own machine
Activity
Actively maintainedrelease 3 weeks ago
How it runs
CLI
Used for
  • search past coding sessions across Claude Code and Codex
  • hand off a session to another coding agent
  • restore project files to an earlier checkpoint
Worth knowingcomputed from what we read · each with its source
  • Launched on Product Hunt on Oct 26, 2026Product Hunt ↗
Alternatives in Developer toolsby use, among tools still maintained

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

Compare carafe with

Pick up to two.

All 10 alternatives to carafe →

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 carafe for?

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

    Captures your local AI coding sessions so you can search them, replay them and hand them off to another agent. It is listed in the Atlas under Developer tools.

  • Who is carafe for?

    developers using Claude Code or Codex who want past sessions kept on their own machine

  • Is carafe still maintained?

    Actively maintained: release 3 weeks ago.

  • What are alternatives to carafe?

    In Developer tools, by use: Cursor, Egnyte, OpenCode, Warp, Pi Coding Agent.

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