Have you ever wondered what Claude Code does behind the scenes when you give it a prompt in the terminal?
What goes on inside it?
What tools does it call?
Which hooks are being called?

That was the exact question I had a few days ago.

The day the idea was born

I built an agentic coding pattern into my codebase: basically a CLAUDE.md file at the root and a .claude directory where the entire orchestration happens, with a directory for skills, a directory for the agents it needs to invoke at runtime, and so on. It works, and it does a great job. But I suddenly noticed that there are sessions where Claude finds its own way to a solution. A similar task that cost a few tokens sometimes gets done in fewer tokens, and, worst of all, sometimes in more. That made me want to peek inside. That was the day Flightpath was born.

How it works?

Flightpath is a tool built to work alongside your Claude Code session. It taps into what Claude Code is doing and gives you a live view in a browser. It never costs tokens and never adds anything to your session’s context. It reads Claude Code’s own records of the session, but it never changes your project files or your Claude settings, and it never sends anything off your machine. All your data stays on your computer.

Simply put: it shows what Claude Code does with your prompt, step by step.

Here are the main features of Flightpath when you watch it live in the browser.

Steps

The Steps view shows each step Claude took, and the details of any step you pick: what the context was then, how much it grew, what command ran, and so on.

Tokens

This tab shows how your context grew. It lists the “Biggest rises”, has a line for each subagent, and more. This is the place to quickly see how your tokens were used during the session.

Snapshot

This view goes deeper into a single step. You can pick a step from the session and see what the agent had been given at that step, and how your context was made up. If your context was compacted midway through the session, it also shows what was restored after the compaction.

Coach

This is my favorite of all!

It gives live suggestions during your session, in the browser and in the terminal, about obvious things it noticed that you could change to make that step cheaper. Each suggestion links to the relevant Claude Code documentation from Anthropic. The coach only suggests; it never changes your files.

Try it yourself

Flightpath is an open-source tool built by DK Labs. You can read the source code on GitHub: https://github.com/dk-labs-dev/flightpath

You need Node 24 installed first.

To install the Flightpath plugin, run these inside Claude Code:

/plugin marketplace add dk-labs-dev/flightpath
/plugin install flightpath@flightpath

Once Flightpath is installed, you can use these commands from your Claude Code session:

Commands

Command What it does
/flightpath:open Open this session's view in your browser
/flightpath:status Show whether this session is recording, and where the data is
/flightpath:stop · /flightpath:start Pause or resume this session
/flightpath:off Turn recording off everywhere
/flightpath:forget Delete this session's recording

I’ve tested it on Windows and Linux; on macOS it runs in CI, but I haven’t tried it there myself yet.

This is my first venture into the open-source community, and I would love your feedback.