Free for VS Code, Cursor and Windsurf

Every chat. One logbook.

Browse, search and resume the Claude Code and Codex chats already on your laptop. See what each one cost, and which ones need you right now.

No account needed. Your chats never leave your laptop.

Fix the flaky login test

The login test fails about one run in five. Find out why and fix it.

Ran 3 commands

The test reads the session before the cookie is written, so it only passes when the write wins the race.

auth.test.ts+2 −1
- const session = getSession()
+ await cookieWritten(page)
+ const session = getSession()

Ran it 50 times in a row. No failures.

Claude38% of 200Kcache 91%$1.84Laptop412 MB3% CPUWorking
Reads
  • Claude Code
  • Codex
Runs in
  • VS Code
  • Cursor
  • Windsurf
  • VSCodium
What it does

Read it. Resume it. Measure it.

Every chat Claude Code and Codex saved on your laptop, shown the way you saw it, one click from running again.

read

Every chat, as you saw it

Markdown, images, tool calls folded into one line, and the diff each edit made. Grouped by project.

resume

Pick it back up

Hit Resume and pick where it reopens: a terminal, the Claude Code extension or Claude Desktop. If it's already running, you land on that terminal.

measure

Know what it cost

Tokens, spend at API prices, cache hits and active time, for one chat or your whole history.

How it works

Three steps. Nothing to set up.

1

Install it

From the VS Code Marketplace, or Open VSX if you use Cursor, Windsurf or VSCodium.

2

Your chats are already there

Click the logbook in the activity bar. It reads what Claude Code and Codex already keep in ~/.claude and ~/.codex.

3

Pick one back up

Open a chat to read it, or hit Resume. Branch starts a new chat from an old one.

Live chats

Which chat needs you? One look.

One tab with a card for every chat running in this window. See which are working and which are waiting, and what each one said last, without opening any of them.

  • Working or waiting for you, at a glance
  • Your last ask and the latest reply, with a copy button
  • The card with the newest message rises to the top
  • This window's chats, or every window, set in Settings
Use it or lose it

Spend your quota before it resets.

Plan-usage bars sit across the top of the panel. When a window is about to reset with plenty left, or is on course to run out early, Agent Logbook says so.

  • Claude's 5-hour and weekly windows, and Codex's
  • Flagged under the bars, on the live board and in the status bar
  • Pick the bars, their colours and the thresholds in Settings
Features

Small panel. Lots inside.

The things you reach for after a long day of agent work, each one a click from the chat list.

Search every message

Full text across every transcript, not just titles. Results stream in chat by chat.

Sub-agents as threads

Background agents show where they were launched, with their brief and report, and open as their own chat.

Branch with a brief

Start a fresh chat from an old one with a written handover, instead of dragging the whole context along.

Chats in fixed spots

Halves, thirds, a grid or the terminal panel. Move any chat from the right-click menu.

Laptop resources

Memory and CPU per running chat, plus leftover commands from ended chats, with a Stop button.

A card to share

A PNG of your usage for a day, a week or all time, sized for X and Slack. No project names unless you add them.

Groups that cut across projects

Put chats into your own groups, like a feature or a client, and filter by them in one click. Shared with the Claude Code extension.

Rename everywhere

Rename a chat and the running session and its terminal tab change with it.

Private by default

Your chats stay on your laptop.

Agent Logbook reads the transcript files already on your machine. There's no account, no server of its own and no analytics.

  • Transcripts are read from disk and never uploaded
  • One request of its own: your plan usage, the same one Claude Code makes
  • Deleting a chat moves it to a trash folder; nothing is wiped
  • Branch with a brief runs Claude on your plan, only when you click it

See everything it reads and writes →

Help

Questions, answered.

Does it upload my chats anywhere?

No. It reads the transcript files on your laptop and keeps its own cache next to them in ~/.claude. There's no account, no server of its own and no analytics. The only request it makes by itself is for your plan usage, explained below.

Why does it read my Claude login?

To draw the quota bars. It asks Anthropic for your current plan usage with the same request Claude Code makes, using the token Claude Code already stored: the macOS Keychain, or ~/.claude/.credentials.json on Linux and Windows. The token is never saved or sent anywhere else.

Which editors does it work in?

VS Code 1.94 or later, and editors built on it: Cursor, Windsurf, VSCodium and the rest. Install from the Visual Studio Marketplace in VS Code, or from Open VSX in the others.

Do I need Claude Code or Codex installed?

It shows the chats they've already saved, so you need at least one of them. Resuming a chat needs claude (or codex) on your PATH.

Is the cost what I actually paid?

No. It's what the same tokens would cost at API list prices. On a Pro or Max plan you pay the plan price, so the number shows how much use you get out of it.

Does it change my chat files?

Only in two ways, both on purpose. Renaming a Claude chat adds a title line to its transcript, which is how Claude Code reads the new name. Deleting a chat moves the file to ~/.claude/trashed-sessions instead of wiping it. Everything else it writes is its own cache and settings. The full list is here.

Does the live board show Codex chats?

Not yet. Codex chats are listed, read, searched and resumed alongside Claude's, but live status (the dots and the board) covers Claude chats for now.

Something's broken. Where do I report it?

Open an issue on GitHub, or email ragulsundaram15@gmail.com. Your editor name and version help.

Every chat, one click away.

Free, private, and already full of your chats.