3 ms·

Is it possible to view the prompt history? I’ve had extreme levels of productivity and would love to list out how I’ve been using it generally for an article li

Is it possible to view the prompt history? I’ve had extreme levels of productivity and would love to list out how I’ve been using it generally for an article like this but it would be incredibly impractical to log it on the side.

globular-toast 1y ago
Just show the code you've produced.
- jaggederest 1y ago
  Right but that's like showing the compiled binary but not the source. With claude code prompt and config is everything.
  - globular-toast 1y ago
    This is the saddest part of this whole thing for me. You consider the prompts and config to be the real source code, but those are just completely lost into the ether. Even if you saved the prompts you can't reproduce their effects. Then there's the question of how do other developers contribute to the code. They don't have your prompts, they just have the code. So, no, prompts are not source code, that's why I ask for people to just show the code they are producing and nobody ever does.
    - jaggederest 1y ago
      I have repos on github. I show the code. I also make my design documents (roughly the prompts generated by the prompts) into committed markdown documents. So I show the second-tier prompts at least, you could consider those an intermediate language representation if you like. > Then there's the question of how do other developers contribute to the code. They don't have your prompts, they just have the code. I usually try to commit the initial prompts and adjustments. I don't commit trivial things like "That's not quite right, try doing X again" or "Just run the entire test suite" > So, no, prompts are not source code Hard disagree, but that's fine.
jaggederest 1y ago
I really want to record a live commentary of me working with claude. Maybe that's something you could think about. I feel like the results I get are qualitatively superior to anything I've seen anyone I've worked with produce. The fact that it's a lot faster is just gravy on top.
orta 1y ago
With Claude Code at least, all of the chats you've had are stored in jsonl files on your computer in ~/.claude - I made a little TUI for exploring these in https://github.com/orta/claude-code-to-adium https://github.com/orta/claude-code-to-adium Personally, I'm less sold on tracking prompts as being valuable both for production cases (imo if a human should read it, a human should have wrote/fully edited it applies to commits/PRs/docs etc) and for vibe cases where the prompts are more transitory

globular-toast 1y ago

Just show the code you've produced.

jaggederest 1y ago
Right but that's like showing the compiled binary but not the source. With claude code prompt and config is everything.
- globular-toast 1y ago
  This is the saddest part of this whole thing for me. You consider the prompts and config to be the real source code, but those are just completely lost into the ether. Even if you saved the prompts you can't reproduce their effects. Then there's the question of how do other developers contribute to the code. They don't have your prompts, they just have the code. So, no, prompts are not source code, that's why I ask for people to just show the code they are producing and nobody ever does.
  - jaggederest 1y ago
    I have repos on github. I show the code. I also make my design documents (roughly the prompts generated by the prompts) into committed markdown documents. So I show the second-tier prompts at least, you could consider those an intermediate language representation if you like. > Then there's the question of how do other developers contribute to the code. They don't have your prompts, they just have the code. I usually try to commit the initial prompts and adjustments. I don't commit trivial things like "That's not quite right, try doing X again" or "Just run the entire test suite" > So, no, prompts are not source code Hard disagree, but that's fine.

jaggederest 1y ago

I really want to record a live commentary of me working with claude. Maybe that's something you could think about. I feel like the results I get are qualitatively superior to anything I've seen anyone I've worked with produce. The fact that it's a lot faster is just gravy on top.

orta 1y ago

With Claude Code at least, all of the chats you've had are stored in jsonl files on your computer in ~/.claude - I made a little TUI for exploring these in https://github.com/orta/claude-code-to-adium https://github.com/orta/claude-code-to-adium Personally, I'm less sold on tracking prompts as being valuable both for production cases (imo if a human should read it, a human should have wrote/fully edited it applies to commits/PRs/docs etc) and for vibe cases where the prompts are more transitory