Looks like complete AI slop without any clear communication of what value is provides to user; flagged
eikenberry 44 days ago [-]
At least the AI was self-aware enough not to add a LICENSE file.
piker 44 days ago [-]
> user: lydionfinance
> 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've also had ai suggest the name Argus many times for an observability platform lol
ramraj07 44 days ago [-]
Hey at least its not ATLAS!
lydionfinance 44 days ago [-]
[flagged]
onionisafruit 44 days ago [-]
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.
lydionfinance 44 days ago [-]
[flagged]
n8cpdx 44 days ago [-]
How does this compare to the built-in agent mode debugging that just shipped in VS Code?
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.
As a reader without a dog in this fight, I appreciate the comment and having the options. It's pretty common on HN.
kronks 44 days ago [-]
The AI generated emoji soup readme isn’t exactly inspiring…
lydionfinance 44 days ago [-]
[flagged]
formerly_proven 44 days ago [-]
Can you help me install this, I’m kinda hangry and need a good buttermilk pancake recipe to overcome this.
AppleBananaPie 44 days ago [-]
+1
lydionfinance 44 days ago [-]
[flagged]
msp26 44 days ago [-]
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
Rendered at 18:08:47 GMT+0000 (UTC) with Wasmer Edge.
> 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]
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...
Someone else’s more polished Mac app: https://readout.org
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