What Claude Code chooses
TL;DR Highlight
Asking Claude Code purely open-ended questions — without mentioning any tool names — reveals what tech it actually reaches for in different scenarios.
Who Should Read
Developers curious about Claude's implicit tech biases and default recommendations, and anyone building AI-assisted dev tooling who wants to understand LLM preference patterns.
Core Mechanics
- The experiment: ask Claude Code open-ended questions like 'what should I use to build X?' without naming any specific tools or frameworks.
- Claude tends to recommend popular, well-documented, mainstream options — which aligns with its training data distribution rather than necessarily the best technical fit.
- For frontend, Claude defaults to React + TypeScript. For backend APIs, it gravitates toward Python/FastAPI or Node/Express. For databases, PostgreSQL.
- When pushed with constraints ('what if I need maximum performance?'), Claude's recommendations shift notably — suggesting it understands alternatives but defaults to popularity.
- The implicit biases are important to know when using Claude Code as a tech advisor — its defaults reflect 'most common in training data' not 'best for your specific case.'
Evidence
- The author ran a series of open-ended technology choice questions and documented Claude's first-choice recommendations across categories.
- Follow-up questions with specific constraints (performance, team size, budget) showed Claude could reason past its defaults when given context.
- HN commenters noted this reflects a broader LLM pattern: defaulting to high-documentation/high-popularity options because that's what dominates training data.
How to Apply
- When asking Claude for tech recommendations, always include your specific constraints upfront (team expertise, scale requirements, budget) rather than asking open-endedly.
- Treat Claude's first-choice recommendations as 'what most teams use' rather than 'what's best for you' — it's a useful baseline but not a substitute for architectural thinking.
- If you want Claude to consider less-popular but potentially better-fit options, explicitly ask: 'what are the alternatives to X and when would each be preferable?'
Terminology
Related Papers
What happened after 2k people tried to hack my AI assistant
실제로 6,000개 이상의 이메일로 AI 에이전트에 prompt injection 공격을 시도한 공개 실험 결과로, Claude Opus 4.6이 비밀 파일 유출을 한 번도 허용하지 않았지만 실험 설계의 현실성에 대한 논란이 뜨거웠다.
When Does Combining Language Models Help? A Co-Failure Ceiling on Routing, Voting, and Mixture-of-Agents Across 67 Frontier Models
여러 LLM을 조합해도 '모든 모델이 동시에 틀리는 비율(β)'이 성능 상한선이며, 업계가 쓰는 pairwise 상관계수(ρ)는 이 상한선을 예측하지 못한다.
Beyond Function Calling: Benchmarking Tool-Using Agents under Tool-Environment Unreliability
실제 환경처럼 API가 망가지거나 결과가 이상할 때 LLM 에이전트가 얼마나 잘 버티는지 측정하는 벤치마크 ToolBench-X 공개.
Nearly Half of LG Smart TV Apps Contain Residential Proxy SDKs
6,038개의 LG·Samsung 스마트 TV 앱을 스캔했더니 2,058개에서 사용자의 IP를 몰래 팔아 트래픽을 중계하는 Residential Proxy SDK가 발견됐다. TV는 컴퓨터처럼 감시받지 않아서 프록시 호스트로 거의 이상적인 환경이다.
Prompt Injection as Role Confusion
LLM이 시스템 프롬프트, 사용자 입력, 툴 출력을 구분하지 못하는 구조적 결함이 prompt injection의 근본 원인이라는 ICML 2026 논문으로, 현재 LLM 보안 아키텍처의 한계를 명확히 분석한다.
GPT-5.5 hallucinates 3x more than MIT-licensed GLM-5.2
모델 크기가 커질수록 성능이 좋아진다는 통념에 반해, 오픈소스 753B 모델 GLM-5.2가 추정 1~2T 규모의 GPT-5.5보다 환각 비율이 3배 낮다는 벤치마크 결과가 나왔다. 단순히 파라미터 수와 벤치마크 점수만으로 모델을 선택하면 실제 업무에서 낭패를 볼 수 있다는 경고다.