[untitled]
24 comments
Looks like complete AI slop without any clear communication of what value is provides to user; flagged
At least the AI was self-aware enough not to add a LICENSE file.
> 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 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]
> 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]
I've also had ai suggest the name Argus many times for an observability platform lol
Hey at least its not ATLAS!
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.
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.
How does this compare to the built-in agent mode debugging that just shipped in VS Code?
https://code.visualstudio.com/updates/v1_110#_agent-debug-pa...
https://code.visualstudio.com/updates/v1_110#_agent-debug-pa...
Not sure what I'm getting here that I do not get from a custom status line.
[deleted]
If you don’t use VSC, don’t enjoy emoji slop, and also want to see sub agent log chains: https://github.com/eqtylab/agent-console
Someone else’s more polished Mac app: https://readout.org
Someone else’s more polished Mac app: https://readout.org
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.
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.
Nice! It looks very well polished.
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
> 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