Comment by varenc
9 hours ago
The more interesting part of deepclaude is the local proxy it runs to switch models mid-session and do combined cost tracking. Though these features seem quite buried in the LLM-generated readme. Looking at the history, it appears they were added later, and the readme wasn't restructured to highlight this.
Also, the author checked in their apparently effective social media advertising plan: https://github.com/aattaran/deepclaude/commit/a90a399682defc... (which seems to be working)
How come such slop is allowed here, what value do these vibe coded zero shot "projects" add? Why not just post the prompt?
Seriously. When I first looked this project had been pushed the first commit two hours prior. Projects should be at least 3 months old or automatically removed.
But then that would have the downside of falsely blocking projects that were developed in private and then just pushed to Github (or any public repo). Like I always use my own, self-hosted Forgejo for everything by default.
3 replies →
For the same reason that GitHub has a releases page for uploading binaries.
Convenience? Am I supposed to take the prompt and use my own tokens on it? Why should I have to do that?
Recruiters used to use the candidate's Github "sources" page for evaluating candidates as a kind of proof-of-work.
And recruiter agents still do.
[flagged]