Apologies but I will use this thread as an opportunity to report CC VSCode extension bugs because I don't think there's an official channel that actually gets read by humans.
> yeah they're shipping too fast and everything is buggy as shit
- fork conversation button doesn't even work anymore in vscode extension
- sometimes when I reconnect to my remote SSH in VSCode, previously loaded chats become inaccessible. The chats are still there in the .jsonl files but for some reason the CC extension becomes incapable of reading them.
-- this issue happens so frequently that I ended up making a skill to allow CC to dig up info from the bugged sessions
The top of the readme says “See Everything | Optimize Everything”. From what I can tell Argus does the former but not the latter. It’s the optimization that I struggle with.
For example, the analysis screenshot shows rereading files. Obviously that’s a waste of time and tokens, but I don’t know how to prevent it. It would be great to link that to some guidance on how to improve vs just showing you what’s going wrong.
My goal is to focus specifically on Claude Code and analyze a single product more effectively. You’re welcome to open an issue and request any features you’d like, and I can add them. I mainly want to directly address developers’ needs and requests.
Are there any videos or screenshots of readout? The webpage is very minimalistic.
https://github.com/dlupiak/claude-session-dashboard - I found this one today, it shows me nicely basic statistics. Do you know the similar tool that would be showing also the interactions of sub-agents? I want to see the user prompts and also statistics by file which tools have touched or read them.
> yeah they're shipping too fast and everything is buggy as shit
- fork conversation button doesn't even work anymore in vscode extension
- sometimes when I reconnect to my remote SSH in VSCode, previously loaded chats become inaccessible. The chats are still there in the .jsonl files but for some reason the CC extension becomes incapable of reading them.
-- this issue happens so frequently that I ended up making a skill to allow CC to dig up info from the bugged sessions
For example, the analysis screenshot shows rereading files. Obviously that’s a waste of time and tokens, but I don’t know how to prevent it. It would be great to link that to some guidance on how to improve vs just showing you what’s going wrong.
https://code.visualstudio.com/updates/v1_110#_agent-debug-pa...
https://github.com/dlupiak/claude-session-dashboard - I found this one today, it shows me nicely basic statistics. Do you know the similar tool that would be showing also the interactions of sub-agents? I want to see the user prompts and also statistics by file which tools have touched or read them.