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.
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
I won't flag it because I caught (legit) flak for that last time, but the above should be sufficient information for the voters to asses. Upvoting this is poisonous to Hacker News.
11 comments
[ 2.1 ms ] story [ 28.8 ms ] threadSomeone else’s more polished Mac app: https://readout.org
https://code.visualstudio.com/updates/v1_110#_agent-debug-pa...
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.
> 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
> created: 64 days ago
> debugger
> 3 commits
> emoji soup README
I won't flag it because I caught (legit) flak for that last time, but the above should be sufficient information for the voters to asses. Upvoting this is poisonous to Hacker News.
I do think it's worthy of flagging.
[Edit: take a look for yourselves folks, you're being duped: https://news.ycombinator.com/submitted?id=lydionfinance; flagged]