Import your Claude Code sessions into a new Lanework board
Here’s a nice surprise: every Claude Code session you’ve ever run is still on your Mac. The feature you built in September, the bug you chased for three days, the plan you talked through and then forgot about. It’s all there, and you can resume any of it.
What you can’t do is see it all at once. Which sessions ended with something left open? Where did last month go? To find out, you’d have to open them one by one.
So let’s lay them out on a board. One card per session, sorted by project, ready to scan, search and pick back up. It takes three prompts, and Claude does the work.
How this works
One thing up front: Lanework has no import button. It doesn’t need one.
A Lanework board is a plain folder. Each lane is a folder inside it, and each card is a folder with a Markdown file. Claude is very good at writing folders and Markdown files. So you ask Claude for a board, Claude reads your session history, and the board appears in Lanework as it’s written.
Claude needs to know the board format first. The Lanework skills teach it, and they install with two commands. The steps are in the Lanework marketplace.
Where your sessions live
Claude Code saves each session as a transcript file under ~/.claude/projects/. Each folder you’ve worked in gets a folder of its own there, and each session is one .jsonl file inside it.
A transcript records everything: your messages, Claude’s replies, the session’s name if you gave it one, and a timestamp on every message. That’s plenty for Claude to list each session with its name, project, dates and first prompt. Building that list is a quick scan of the files. It uses no model time at all.
You may have more history than you think. My Mac had 1,691 transcript files. Most of those belonged to subagents, the helpers Claude starts during a session. The sessions I’d started myself came to 187, across 26 projects.
Step 1: Ask for an index
Start with a list, not a board. It’s fun to see what’s there, and you’ll want to choose what to import.
Index my Claude Code sessions. Read the transcripts under ~/.claude/projects/ and skip the subagent ones. Give me a numbered list with each session’s name, project, first and last date, how many prompts I wrote, and my first prompt. Don’t summarize anything yet.
A moment later you’ll have something like this:
1 Main acme-web Sep 3–5 14 prompts "Add dark mode to settings"
2 Scratch acme-ios Sep 8 1 prompt "Why does the build fail on CI?"
3 Main acme-ios Sep 9–12 22 prompts "Fix login crash on iOS 26"
4 Pricing notes Sep 15 6 prompts "Plan v2 pricing"
Two tips from my own list:
- Filter out the quick ones. Lots of sessions are one-prompt checks. When I kept only sessions with three or more prompts, 187 became a tidy 50. Just ask: “only show sessions with three or more prompts.”
- Read the first prompt, not the name. Session names tend to be “Main” or “Scratch”. The first prompt is what tells you which session is which.
Step 2: Pick your sessions and your card style
Now choose what goes on the board. All of it, a few projects, or a handful of numbers from the list.
Then choose how much each card should say. There are two good styles:
- Light. Each card gets the session’s name, project, dates, first prompt and session ID. Claude already has all of this from the index, so the board is ready in moments and costs next to nothing.
- Full. Each card gets a short summary: what you asked, what was decided, what got done, and what was left open. Your prompts become the card’s comments, so the whole conversation reads like a thread. This one takes longer, because Claude reads every transcript it summarizes.
Start light. You can always ask for full summaries later, on just the cards you care about.
Make a Lanework board called “Claude Code history” from sessions 1, 3 and 4, plus every acme-web session with three or more prompts. One lane per project, light cards. Put the dates, the first prompt and the session ID in each card’s body.
Step 3: Watch your board appear
This is the best part. Open the new board in Lanework while Claude works, and the cards land in their lanes one by one.
Once it’s done, it’s a board like any other:
- Search it. Type a word you remember from a prompt and the session turns up.
- Label it. Mark how each session ended, like shipped, abandoned or still open.
- Rearrange it. Drag cards around, or give a busy project a board of its own.
Claude can do the labeling too:
On the Claude Code history board, read each card and label how the session ended: shipped, abandoned or still open.
What you can do with it
Find your loose ends. Filter to “still open” and weeks of half-finished work become a short list you can actually finish.
See where your time went. With a lane per project and a prompt count on every card, it’s obvious which projects got your attention, and when.
Pick up where you left off. Each card holds its session ID. Run claude --resume <session-id> in the project’s folder and you’re back in that exact conversation. Or start a new session and point it at the card. A card is a short, clear account of where things stood, which often makes better context than the whole transcript.
What about Claude.ai Projects?
Chats in claude.ai Projects aren’t stored on your Mac, but you can ask for a copy. In claude.ai, go to Settings › Privacy › Export data, and you’ll get a zip with your projects and conversations inside. Unzip it, point Claude at the folder, and ask for a board the same way.
I haven’t tried this route myself yet. If you do, start with a few conversations and see how the cards turn out.
Two things to know before you start
Your transcripts hold everything you typed. That includes personal notes, file paths, and maybe a password you pasted in while debugging. Anything in a transcript can end up on a card. Have a look through the board before you share it or commit it to git.
Full summaries take a while. My session history came to 3.1 GB. Summarizing all of it would be slow, and it would cost real money. A light board with a three-prompt filter gets you most of the value in a minute or two. Go deeper only where it’s worth it.
That’s it. Three prompts, and months of work are on one board. Have fun looking around. You’ll find more in there than you remember.