Markdown Conversation History Tracking Feature Request

What's your use case? Can you tell me more about how you want to use the saved conversations?

What's your use case? Can you tell me more about how you want to use the saved conversations?

I'll just comment here. I've taken to coaching Sonnet through writing a much bigger custom summary, with customized detail only me or the full model context I've been in could make. For the most recent messages, I ask it to copy both sides' natural language verbatim, then an narrative overview of where we've been and are going, and a broad summary. Only then do I run /compact. I don't need it to be readable to a human a month later. Only sonnet ten seconds later.

I would like for compacting the context or restarting the program to not feel costly.
So far, I've gone to do a big task like a refactor, saw low context, used /compact, and

1. Was disoriented that sonnet didn't know what I was talking about
2. Found the summary formulaic and poorly applicable
3. Confused why it gave a summary of the state of the project and not of the conversation
4. Actually pretty unhappy that i couldnt access it again. My messages to models are often my only notes. I should be able to cross reference it forever just like I do in claude desktop. More than happy to generate hundreds of megs of log.

I'm happy to manage all that, but I want to be able to.

+1 to the explanation above - but also just having running history of prior conversations is helpful for when you start a new session but want to refer to something discussed in a previous session.

Similarly I would love to continue sessions from specific points in prior (or current) conversation - though maybe that's a separate feature request.

Actually pretty unhappy that i couldnt access it again. My messages to models are often my only notes. I should be able to cross reference it forever just like I do in claude desktop. More than happy to generate hundreds of megs of log.

I agree completely

Thanks to the others who have chimed in here. Exactly what is said above...I should have forever access to my conversations with Claude Code. There are times when I want to refer back to previous sessions and today that is not possible.

I use prompts to accomplish something like this. it's not exact and of course not perfect. But it keeps a history, uses it for context and archives old entries when it gets to long. I have a prompt I run at the start of a session (new or after /compact), and one that I run at the end of a session before a /compact or exiting. These prompts maintain the tasks to do, finished, project history from our session, and lots of other details that helps me keep everything in order. They are specific to my projects and file paths and all that, but could easily be modified for any project.

Startup Prompt

End of Session Prompt

The files they edit and other prompts for working in those projects are all in that repo.

This is of course way more expensive as I do these two large prompts and processes every session and it spends a lot of my context. But for right now its the best way i've found to keep Claude Code working on the projects with the context it needs between sessions. Claude doesn't forget much anymore, or tell me it can't do something.

@bcherny

Use cases for viewing a time-stamped conversation history:

• When restarting claude it clears the whole terminal history, including when I've just done a /compact so that I can reboot. That's frustrating, I want to get that summary and put it in my new session.
• Demonstrating using CC to other engineers - what works and what not - great to look at the log all in one place.
• Retrospective analysis of time spent, and how spent while using the tool.

On windows, open powershell and run $profile
Navigate to the directory and edit profile.ps1 to add this code:

$transcriptPath = "C:\Users\{your user}\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\PowerShell_transcript.txt"
Start-Transcript -Path $transcriptPath -Append

restart powershell

now your logs (inputs and outputs) will be saved at C:\Users\{your user} \AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\

Type (Get-PSReadlineOption).HistorySavePath in powershell to obtain the above path in case you ever need it.

I've been happily using claude code to test it, and been enjoying it a lot, but without a feature like this it would be a nonstarter for serious work. I want to be able to keep track of my own conversations to:

1. log them for posterity - allows me to understand thought-processes that led to certain additions. If I can commit the chatlog at the same time I commit a certain feature, that gives me context while reviewing a specific commit
2. understanding what works and what doesn't - i like to look back at my conversation history and analyze it to understand what prompts i used and how i could improve them

I am currently manually keeping a chatlog with the messages I send it, and part of my prompt is asking it to keep certain "working" documents updated. At the end of the session I ask it to summarize my chatlog combined with the working documents. But this is inconsistent and a very impractical and slow way to interact with CC

I would also love to export transcripts, though I'd prefer HTML that preserves all the coloring. I've been doing this manually by selecting my entire terminal history and choosing "copy as HTML" (a feature of gnome-terminal).

I like to save these transcripts and attach them to pull requests so people can see what the process looked like. This helps me evangelize Claude Code.

ideas:

• tracking convo history could be an opt-in option
• could add /export-convo or /save-convo cmds

Have encountered multiple issues already due to not being able to pull out past conversation, i.e.:

• Used it to generate some code. Days later when reviewing the changes I realized a potential issue, loosely remembered discussing it (i.e. I actually asked in the session why something was done a particular way but forgot to add it to comments), & had no way to review the conversation.
• Discussing good practices with teammates, wanted to share a successful and failed Claude Code fix, but there's no way to pull out the conversation to share
• Tried to fix something with Claude Code but failed; several days later tried again and succeeded. Wanted to review my own prior prompts so I could more clearly compare what worked vs didn't, but no way to review.

This is actually the first AI tool I've worked with that has no way to review past interactions.

My use case is just to show how good Claude Code can be.

I like to review my prompts and their responses at the end of the week for learning. I like using prompting to help me learn and ask questions. I find it really helpful with the desktop AI apps to review the conversations and distil my own notes from them. I'd really appreciate being able to do the same with CC - something like a /history command to show a list of prompts (maybe summarised titles like the desktop apps) then I can select one and then see the details of it.

Hi Folks,

We built a CLI wrapper that allows you to get past conversations out and autosave as you go.
Quick Start

When you run Claude Code through specstory, it automatically saves your conversations in .specstory/history/ in your current project directory. The CLI acts as a wrapper, launching Claude Code while capturing all your chat sessions.

We're thinking of open sourcing it soon, let us know what you think. Easy way to install is using homebrew:

brew tap specstoryai/tap
brew update
brew install specstory

---

It provides simple flags to manage your Claude Code conversations:

Run Claude Code through SpecStory wrapper (default)

specstory

Sync all Claude Code sessions to markdown files from previous sessions (w

specstory -s

Generate markdown for a specific session

specstory -u <session-uuid>

Run with verbose output to see what's happening

specstory --verbose

Run -h for comprehensive flag details and options

specstory -h

• 📝 Automatic capture: Running the CLI launches Claude Code and captures conversations
• 🗂️ Project-based organization: Sessions are saved in .specstory/history/ with timestamps
• 💾 Batch conversion: Use -s flag to convert all existing sessions to markdown
• 🌳 Git-friendly: All output is clean markdown, perfect for version control

I was searching for a way to share sessions but was not able to find a simple tool, so I created one: https://github.com/automata/ccsession

You can export the session of your current project (the one active in your current folder) with only one command:

npx ccsession@latest

Or specify the project id:

npx ccsession@latest --project project-id

To export as Markdown instead of HTML:

npx ccsession@latest --markdown

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.