Seems like you could achieve the same type of experience with this.
This is quite excellent though; makes it easier to try different solutions and switch between them (considering they are all doing a race to get better).
Here’s a hint: https://github.com/microsoft/playwright/issues/10369#issueco...
[1]: https://web.archive.org/web/20201108093051/https://github.co...
This looks to me like a great way to log claude code interactions.
Is it just me that cannot figure out a way to log the prompts and responses when using Claude Code?
If I look here I see nothing about a logging switch (beyond --verbose which is different). I'm surprised I cannot tell it to write this to a per session file.
https://docs.anthropic.com/en/docs/agents-and-tools/claude-c...
It is interesting because my daughter uses my claude account on another computer and I can see her prompts and she can see mine. I get nervous when I go down a political rabbit hole that she will get freaked out, but so far so good. Claude does keep a "history" there. But, not when you are using the code tool.
There is one very good reason I can imagine why this would not be in the tool. If I'm billing a client at $100X and my final cost from Claude Code is only $X, then I suppose I would prefer that no one could ever ask for that information. Someday employers will, I bet.
Maybe there is an easier way, like scripting or capturing the terminal output directly?
