// llm limitations

All signals tagged with this topic

Coding Agents Still Can't Deliver Production-Quality Software

A hands-on test of four AI coding agents with real constraints—$100 budget, concrete deliverable—found that none produced genuinely usable output, despite passing basic functionality checks. This matters because it exposes the gap between "works in isolated tasks" and "ships a real product." Current agents excel at scaffolding and boilerplate but fail at debugging, architectural decisions, and the grinding work of polish that separates demos from deployable tools. The limiting factor isn't raw capability but integration, judgment, and the messy reality that software quality compounds through iterative refinement—something today's agents still can't do autonomously without human intervention.

AI Still Misses Half of Planted Research Errors

Claude and frontier models caught only about 50% of deliberate errors inserted into psychology papers. AI peer review remains a weak substitute for human scrutiny, not a reliable complement. The gap matters because journals are already under pressure to adopt faster review processes. Deploying frontier AI as a first-pass filter could systematically let flawed work through—especially in fields where methodological errors compound across downstream research. Commercial AI tools performed even worse, indicating that capability gaps between frontier and commodity models create real quality-control stakes for publishers considering automation.

Why AI tutors fail where human teachers succeed

Smartschool's struggle to build exam prep software exposes a gap between retrieval systems (which fetch facts) and pedagogical systems (which diagnose misconceptions, scaffold learning progressively, and adapt to individual cognitive gaps). The market has oversimplified "AI in education" as content delivery, leaving a vacuum for tools that model student understanding rather than generate plausible answers—a harder engineering and data problem that explains why most edtech AI remains shallow against the hype.

Google Questions Core Purpose Behind LLMs.txt Standard

Google's pushback reveals a practical fracture in how the LLMs.txt file—meant to let AI companies declare training data boundaries—actually gets deployed. The standard was designed for transparency and consent, but if companies are using it as a compliance checkbox rather than a genuine signal about their data practices, the mechanism fails at its stated purpose. When adoption is voluntary and verification is difficult, a file format cannot enforce good faith.