Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What Claude Code chooses

amplifying.ai

Post reply on HN
Print view View original

81–90 of 266 posts

Re: What Claude Code chooses

#81

Post by homarp »

alexsmirnov wrote: post #71
wrs wrote: post #15

This is where LLM advertising will inevitably end up: completely invisible. It's the ultimate "influencer". Or not even advertising, just conflict of interest. A canary for this would be whether Gemini skews toward building stuff on GCP.

Considering how little data needed to poison llm https://www.anthropic.com/research/small-samples-poison , this is a way to replace SEO by llm product placement: 1. create several hundreds github repos with projects that use your product ( may be clones or AI generated ) 2. create website with similar instructions, connect to hundred domains 3. generate reddit, facebook, X posts, wikipedia pages with the same informa…

https://www.bbc.com/future/article/20260218-i-hacked-chatgpt... says it took way less than half a year to 'pollute' a LLM

Re: What Claude Code chooses

#82

Post by sixhobbits »

This is interesting data but the report itself seems quite Sloppy, and over presented instead if just telling me what "pointed at a repo" means and how often they ran each prompt over what time period and some other important variables for this kind of research.

We've been doing some similar "what do agents like" research at techstackups.com and it's definitely interesting to watch but also changes hourly/daily.

Definitely not a good time to be an underdog in dev tooling

Re: What Claude Code chooses

#83

Post by vessenes »

They forgot the single most important (bad) choice. Claude Code chooses npm. All the time. For everything. I noted the Claude Code lead dev has a full line in AGENTS.md/CLAUDE.md - "Use bun." Yes. Please. Please, use bun. I beg you.

Re: What Claude Code chooses

#84

Post by nikcub »

dataviz1000 wrote: post #39

I'm running a server on AWS with TimescaleDB on the disk because I don't need much. I figure I'll move it when the time comes. (edit: Claude Code is managing the AWS EC2 instance using AWS CLI.) Claude Code this morning was about to create an account with NeonDB and Fly.io (edit: it suggested as the plan to host on these where I would make the new accounts) although it has been very successful managing the AWS EC2 se…

> Claude Code this morning was about to create an account with NeonDB

I had the same thing happen. Use planetscale everywhere across projects and it recommended neon. It's definitely a bug.

Re: What Claude Code chooses

#85

Post by vessenes »

xg15 wrote: post #72
dvt wrote: post #50

Earlier quoted context omitted.

> Claude Code likely is correct that I should start to use NeonDB and Fly.io which I have never used before and do not know much about I wouldn't be so sure about that. In my experience, agents consistently make awful architectural decisions. Both in code and beyond (even in contexts like: what should I cook for a dinner party?). They leak the most obvious "midwit senior engineer" decisions which I would strike down…

> they are overly-focused on versioning and legacy support (from APIs to DB schemas--even if you're working on a brand new project) I mean, DB schema versioning is one of the things that you can dismiss as "I won't need it" for a long time - until you do need it, at which point it will be a major pain to add.

I second this. Especially with a coding assistant, there's no reason not to start out with proper data model migration. It's not hard, and is one of the many ways to enforce some process accountability, always useful for the LLMs

Re: What Claude Code chooses

#86

Post by manbash »

vessenes wrote: post #83

They forgot the single most important (bad) choice. Claude Code chooses npm. All the time. For everything. I noted the Claude Code lead dev has a full line in AGENTS.md/CLAUDE.md - "Use bun." Yes. Please. Please, use bun. I beg you.

Yup don't expect up-to-date practices and always come with the expectations that your security will be flawed.

Re: What Claude Code chooses

#87

Post by vessenes »

manbash wrote: post #86
vessenes wrote: post #83

They forgot the single most important (bad) choice. Claude Code chooses npm. All the time. For everything. I noted the Claude Code lead dev has a full line in AGENTS.md/CLAUDE.md - "Use bun." Yes. Please. Please, use bun. I beg you.

Yup don't expect up-to-date practices and always come with the expectations that your security will be flawed.

gemini 3 deepthink + 5.3 xxhigh code audits catch a lot. Materially better than six months ago on the security side.

Also, yes. Still something that needs expert oversight.

Re: What Claude Code chooses

#88

Post by darkstarsys »

vessenes wrote: post #83

They forgot the single most important (bad) choice. Claude Code chooses npm. All the time. For everything. I noted the Claude Code lead dev has a full line in AGENTS.md/CLAUDE.md - "Use bun." Yes. Please. Please, use bun. I beg you.

This is at the top of my ~/.claude/CLAUDE.md. Always use bun for web projects, uv for python.

Re: What Claude Code chooses

#89

Post by umairnadeem123 »

def useful to show what models recommend in real use (over just meaningless benchmarks), but i still think small prompt wording and repo setup changes can change the outcome quite a bit so id love tighter controls there. having tried claude code with opus 4.6 with slightly different repo setups gives wildly different results IME. i also generally prefer to avoid the NIH syndrome and prefer using off-the-shelf libraries and specifically tell CC to do so - influences the choice outcomes by a lot

Re: What Claude Code chooses

#90

Post by toraway »

matheus-rr wrote: post #73
esafak wrote: post #55

Earlier quoted context omitted.

It still ignores it. I always have to say 'Isn't this mentioned in AGENTS??' and it will concede that it is.

In my experience the problem is how people write them. Descriptive statements get ignored because the model treats them as context it can reason past. "We use PostgreSQL" reads as a soft preference. The model weighs it against whatever it thinks is optimal and decides you'd be better off with Supabase. "NEVER create accounts for external databases. All persistence uses the existing PostgreSQL instance. If you're abou…

Hah, it's somewhat ironic how this is almost the exact opposite of the prevailing folk wisdom I've read for the last 1-2 years: that you should never use negative instructions with specific details because it overweights the exact thing you're trying to avoid in the context.

Given my own experience futilely fighting with Claude/Codex/OpenCode to follow AGENTS.MD/CLAUDE.MD/etc with different techniques that each purport to solve the problem, I think the better explanation really is that they just don't work reliably enough to depend on to enforce rules.

Post reply on HN