Hacker Newsnew | past | comments | ask | show | jobs | submit | zoho_seni's commentslogin

Definitively our approach is ai dev ex first.

Protocols that literally insert a bit are HDLC / PPP / CAN and they insert a 0 after a few 1s


I've been using codex and never had a compile time error by the time it finishes. Maybe add to your agents to run TS compiler, lint and format before he finish and only stop when all passes.


I’m not sure why you were downvoted. It’s a primary concern for any agentic task to set it up with a verification path.


You can't see diffs in git?

How you using hooks?


That’s a separate tool though. You don’t want to have to open another terminal to git diff every 30 seconds and then give feedback. Much better UX when it’s inline.

My main hooks are desktop notifications when Claude requires input or finishes a task. So I can go do other things while it churns and know immediately when it needs me.


You could easily guard against bullshit issues. So you can focus on what matters. If the issue is legit goes ahead to a human reviewer. If is run of the mill ai low quality or irrelevant issue, just close. Or even nicer: let the person that opened the issue to "argue" with the ai to further explain that is legit issue for false positives.


How is an llm supposed to identify an llm-generated bullshit issue...? It's the fox guarding the henhouse.


Just try and you'll see if it can work. Just copy paste some of these issues give context of the project and ask if makes sense


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: