Documentation

Finding things

One query covers every tool you use. Search is keyword and meaning at once: exact terms are matched, and so are the turns that meant the same thing in different words.

In the web UI

A search for why the ledger checks the idempotency key, returning six hits across claude-code, chatgpt and gemini with the matching terms highlighted.
One search across Claude Code, ChatGPT and Gemini at once. The project and its conversations are sample data; the software is not.

Open it with tokenome app, or tokenome open when the service is already running; both land on localhost:8741. The Search page takes a question in your own words. Each hit shows the matching text with your terms highlighted, the platform and model it came from, the project, and when it happened.

Opening a hit puts you in the conversation reader at the cited turn, so you read the exchange in order rather than a snippet out of context.

The conversation reader with the cited turn highlighted: a question about two ledger entries with the same idempotency key, the assistant's explanation, and the follow-up turn.
The cited turn, highlighted in the thread it came from. Sample data.

In the desktop app, Command-Shift-K opens a search palette from anywhere, with arrow keys and Return to jump straight to a turn.

On the command line

tokenome search "why does the ledger check the idempotency key"

The same index, the same ranking. Add --json when something else is going to read the output.

FilterWhat it does
--top-k NHow many results to return. The default is 10.
--project NAMEOne project only.
--platform NAMEOne tool only: claude-code, chatgpt, claude-desktop, gemini.
--model NAMEOne model only.
--ai-label NAMEOne label only. Searches locally.
--conversation IDInside one conversation. Searches locally.
--since, --untilAn ISO 8601 time range.
--around T --window MMinutes either side of a moment. Useful with a commit time.
--scopeWhere to look. See below.
--jsonMachine-readable output.

Scope: yours, the team's, or both

On one machine there is nothing to choose; every search is your own index. Once you are enrolled on a team server, the Search page gains a scope selector and the CLI takes --scope.

ScopeWhat you get
autoThe default. Team when you are enrolled, your own index when you are not.
teamThe shared index: everyone's opted-in projects, each hit attributed to the person who shared it.
mineYour local index only, including the conversations you have never shared.
allBoth, ranked separately. Anything you shared appears once, in the team section.

If the server does not answer quickly, you get your local results with a visible warning rather than a spinner. See Team.

Other ways in

  • tokenome search ... --around with a commit timestamp, when you know when something happened but not what it was called.
  • tokenome context, when you have a file and a line rather than a question.
  • tokenome faq, when the question is one you have asked before.
  • The MCP tools, when it is your agent asking rather than you.