Skip to content
Poirot logo

Poirot

Browses and inspects Claude Code session logs, showing files touched, token spend, tool calls and rate-limit windows on macOS.

Actively maintained

Developer toolsFor developersAnalytics
poirot.fyi ↗Launched on Product Hunt · Feb 25, 2026
Open poirot.fyiAlternativesSet it up for my team
Poirot: data, price, alternatives
At a glancechecked Nov 1, 2026

not read yet

Use

For
Claude Code users on macOS who want to see which files a session touched and what it spent.
Activity
Actively maintainedrelease 6 days ago
How it runs
Desktop app
Used for
  • browse past Claude Code sessions grouped by project
  • review which files a session modified and compare versions
  • track token usage and cost by model over time
Worth knowingcomputed from what we read · each with its source
  • Launched on Product Hunt on Feb 25, 2026Product Hunt ↗
Alternatives in Developer toolsby use, among tools still maintained

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

Compare Poirot with

Pick up to two.

All 10 alternatives to Poirot →

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

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

    Browses and inspects Claude Code session logs, showing files touched, token spend, tool calls and rate-limit windows on macOS. It is listed in the Atlas under Developer tools.

  • Who is Poirot for?

    Claude Code users on macOS who want to see which files a session touched and what it spent.

  • Do people use Poirot?

    Little sign of use.

  • Is Poirot still maintained?

    Actively maintained: release 6 days ago.

  • What are alternatives to Poirot?

    In Developer tools, by use: Honeycomb, Inception, Capacitor, WOZCODE, Clor.

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