logoalt Hacker News

Wowfunhappyyesterday at 10:09 PM1 replyview on HN

I'm fundamentally a hobbyist programmer, so I would have no problem sharing my process.

However, I'm not nearly organized enough to save all my prompts! I've tried to do it a few times for my own reference. The thing is, when I use Claude Code, I do a lot of:

- Going back and revising a part of the conversation and trying again—sometimes reverting the code changes, sometimes not.

- Stopping Claude partway through a change so I can make manual edits before I let Claude continue.

- Jumping between entirely different conversation histories with different context.

And so on. I could meticulously document every action, but it quickly gets in the way of experimentation. It's not entirely different from trying to write down every intermediate change you make in your code editor, between actual VCS commits.

I guess I could record my screen, but (A) I promise you don't actually want to watch me fiddle with Claude for hours and (B) it would make me too self-conscious.

It would be very cool to have a tool that goes through Claude's logs and exports some kind of timeline in a human-readable format, but I would need it to be automated.

---

Also, if you can't tell from the above, my use of Claude is very far from "type a prompt, get a finished program." I do a lot of work in order to get useful output. I happen to really enjoy coding this way, and I've gotten great results, but it's not like I'm entering a prompt and then taking a nap.


Replies

noman-landyesterday at 11:44 PM

All your conversations are living as json files inside `~/.claude/`.

show 1 reply