zlacker

>>mfbx9d+(OP)
I use claude code daily, but I've never been in a situation where Claude code was "deciding which product to use," that doesn't make sense to me. Claude is never on the web reading documentation - as far as I can tell that's not even in its toolkit. Can anyone give me more context for this? How do you end up having Claude code reading documentation and "choosing" a product to use? What type of prompts lead to this? I'm typically using it to add features to an existing repo, which doesn't really require any new services, to be fair, so I just haven't run into it I guess, but I didn't even know it was possible.

>>window+iwg
The choice happens implicitly rather than explicitly. If Claude tries an approach and hits a wall, it'll try a different approach. If an API call keeps not working, it'll choose a different API. It a tool is broken, it'll use something else. If it can't find docs nor read the code, it'll try to implement functionality from scratch. If you give it messy tools with confusing docs, you'll notice Claude not calling them as you'd expect, and instead trying something simpler instead.

>>dangom+kxg
"something simpler/simpler approach" are terms I search for in evals because they almost always indicate the model going off the rails (assuming the input prompt was decent).

>>Curiou+5Cg
this is a really cool insight, going to use this on my team from now on!