zlacker

>>KuzeyA+(OP)
I've seen many people say "I don't get the hype", so here's my attempt to explain it. I've been working in technology and software companies my entire life, but not as a developer.

Two days ago, I submitted and had my first pull request merged to an open source project (Clawdbot) thanks to my AI assistant rei.

A short story: rei suddenly stopped responding in some Slack channels. So I asked it to help me troubleshoot.

We traced the issue: adding custom instructions in one Slack channel incorrectly stopped it from replying in all the others.

I considered reporting the issue in GitHub, but then I thought, "Well... what if we just try to fix it ourselves, and submit a PR?"

So we did. We cloned the codebase, found the issue, wrote the fix, added tests. I asked it to code review its own fix. The AI debugged itself, then reviewed its own work, and then helped me submit the PR.

Hard to accurately describe the unlock this has enabled for me.

Technically, it's just an LLM call, and technically, I could have done this before.

However there is something different about this new model of "co-working with AI that has context on you and what you're doing" that just clicks.

>>jason_+ai
This is a thing you can enable on GitHub for any project.

You just described a GitHub feature

>>kristo+Uj
>>9224

>>jason_+pl
i disagree with your dropbox example. dropbox is apprently easier to use than a selfhost ftp site and well maintained by a company. but this clawedbot is just a one-man dev developed project. there are many similar "click to fix" services.

>>tttpob+Yv
Not exactly, clawdbot is an open source project with hundreds of contributors (including me!) in only 3 weeks of its existence. Your characterization of just a one-man dev developed project is inaccurate.

>>jason_+l51
I acknowledge its potential to be a great project, but I am simply stating my view that it is overhyped(currently). I also think that although agent scaffolding matters, model capability is the determining factor.