[xrd]

I'm using claude code a lot more than I expected I would. And, it has these problems exactly. It does not appear to log anything, anywhere. I cannot find a local log of even my prompts. I cannot find anything other than my credits counts to show that I used it. The coding conversation is not stored in my conversation in the webui.

I wonder if this is by design. If you are doing contracting work, or should I say, claude is doing contracting work by proxy for you (but you are keeping the money in your bank account) then this gives you a way to say "I don't know, maybe Claude did 12% of the work and I did the rest?"

openwebui and aider both have ways to log to something like datadog. So many layers of software.

I've been looking at ways to script my terminal and scrape all the textual data, a tool that would be outside of the subprocesses running inside the terminal. I really like to keep track of the conversation and steps to build something, but these tools right now make it really difficult.

[ljm]

One of the pet projects I have going is to try and store the interactions as a roam-style knowledge base of connected thought, with the idea that you could browse through this second brain you’ve been talking to afterwards.

Almost every time I’ve asked an LLM to help implement something I’ve given it various clarifying questions so I understand why, and digging through linear UI threads isn’t great.

A decent o11y or instrumentation layer is pretty important to do anything like that well.

[efreak]

If you use putty there's a way to log all output, including terminal control codes. This lets you see exactly what was happening, eg characters being deleted and the screen being wiped, and other things caused by eg curses. It's probably possible to write a playback function for this.