Top
Best
New

Posted by craigmart 8 hours ago

How the Claude Code team thinks about verification(claude.dev)
186 points | 155 commentspage 3
fk202611 3 hours ago|
[dead]
ankur_misra 3 hours ago||
[flagged]
oceanrelay 7 hours ago||
[flagged]
anatolii1309 3 hours ago||
[flagged]
makercfd 4 hours ago||
[flagged]
dotdi 7 hours ago||
> https://github.com/anthropics/claude-code/issues has over 16k open issues

this u?

laichzeit0 7 hours ago|
And 90k closed. Looks like it's doing a pretty good job.
ahsillyme 7 hours ago|||
Issues are automatically closed after being inactive for too long. It's also true that many issues that are filed there have nothing to do with Claude Code proper. To conclude, these numbers (either many open, or many closed, or any relationship between them) a-priori mean nothing either way.
orbital-decay 7 hours ago||||
Opening and closing GitHub issues does not necessarily mean doing some job.
catlifeonmars 7 hours ago|||
A better signal would be average issue age.
Ampersander 7 hours ago||
Why is the team thinking? Their product should be doing that for them
simianwords 7 hours ago||
HN comments love to use the curmudgeonly tone but did you not stop to think that they are going as far as possible to let model do what it can and do everything else?

Did you forget that they literally publish benchmarks that show how much of the task can be done independently?

Goto80 7 hours ago||
Why is there a team? Their product should be the team. /s
titzer 5 hours ago||
I see a lot about adding skills to make Claude test things.

How about making Claude generate scripts that you can run?

Algorithms are better than agents. In fact, the whole point of AI is to reduce thinking to algorithmics. I didn't see a lot of evidence that the team understands this. If you need a magic box to test your other magic box, you have magic boxes all the way down.

duskdozer 3 hours ago|
Scripts that you can run on your own CPU don't cost tokens, so these companies are disincentivized from encouraging them.
saagarjha 5 hours ago||
This is just a depressing read, and I’m not even sure why the team decided to post it because it just looks horrible. Like, you’re telling me that the team’s approach to verification is that they post Claudeslop blog posts talking about the most unimaginative ways to write tests? That their idea of making things work is this?

> You can also close the verification loop by using the results to improve the agent’s performance on that task. For example, if an agent repeatedly fails a test that checks logs for user data, you can create a hook or a more explicit rule in your CLAUDE.md to avoid future issues. This (mostly) stops issues from happening again.

There are people out there who are doing all sorts of crazy neat things in the verification space using the tools you build and yet the people who could be helping seem to have no good ideas on how to help :/

TheRoque 6 hours ago|
I can totally see that they don't review their product at all, Claude code is probably the thrashiest TUI I've ever used.
More comments...