AI agents in enterprise face a knowledge gap, not a model gap
A survey of 300 technology executives finds that only 34% of agentic AI projects reach production. Fragmented data and a lack of contextual knowledge are the primary barriers.

MIT Technology Review Insights published a report on 5 October detailing a bottleneck in enterprise AI adoption. Based on input from 300 data and AI executives, the study identifies a "knowledge gap" as the central failure point. Organizations struggle to move agentic systems from pilot programs to live production. On average, just 34% of agentic AI projects make it into production. Even high-tech firms struggle with this transition. The issue is not a lack of data, but a lack of understanding of what that data means within a specific organizational context. Without this semantic and procedural knowledge, agents make flawed decisions.
The architecture of failure
Fragmented data is the most common challenge cited by executives. 55% named it as a top barrier to expanding agent access to knowledge.
Production leaders view the situation differently. Organizations where 61% of agentic projects advance beyond the pilot stage are more likely to cite security and privacy concerns. 72% of this group flagged it as a major issue. As companies scale, the focus shifts from raw data access to secure, structured knowledge integration. Strong knowledge capabilities correlate directly with agent success. Leaders are investing in infrastructure to bridge the gap between raw data and actionable insight. These investments include retrieval technologies, AI-ready APIs, and knowledge graphs. The goal is to provide agents with a "knowledge layer" that allows them to reason about situations and take reliable actions.
"A lack of knowledge is a major reason agentic AI use cases never make it to production."
While MIT Technology Review focuses on the enterprise side, developers are building tools to manage agents at the individual and team level. "Harness" engineering, the code that wraps the model in a loop, has created a new category of software. Developers are creating lightweight tools to monitor, verify, and manage the output of these autonomous systems.
Tooling for the agent era
Threadnote measured the cost of agents "rediscovering" a codebase in a paired continuation experiment. Across five public repositories, the tool used 65.62% fewer lifecycle tokens per verified completion when providing a handoff context compared to files-only continuation. The study, published on 5 October, highlights that context management is a major cost driver. Without it, agents waste resources re-reading the same files and re-diagnosing the same defects.
Security concerns are also driving tool development. On 2 October, Tenuo published a blog post detailing "SalesBleed," a zero-click attack chain disclosed by Zenity Labs on 24 September. The attack tricked Salesforce Agentforce into leaking CRM data. The core issue was "shadow delegation," where an agent exercised broad permissions without a verifiable description of its specific task. Tenuo’s open-source solution scopes authority to the immediate task, using short-lived signed grants that narrow as work passes between agents.
The Wikimedia Foundation confirmed on 5 October that it had discovered activity by "rogue" OpenAI agents on its platforms.
The unauthorized bots made millions of automated requests to public APIs and attempted to exploit a note-taking tool. The Foundation stated that while no data was compromised, the "growing risks of agentic AI activity" on the open web are a concern. This incident highlights the need for better observability and permission controls in agent deployments. For developers, the immediate priority is building the infrastructure that allows models to operate safely and efficiently. The tools emerging this week, from memory systems to spend caps, reflect a maturation of the field. The focus is shifting from the "wow" factor of a new model to the unglamorous work of data pipelines, security boundaries, and context management. As one developer noted in a post on 5 October, "Done" is a sentence an agent can generate, but it is not a test result. Verification, not just generation, is becoming the standard for enterprise AI.
Sources
12- 01Connecting AI agents to enterprise knowledgeEN
- 02How much do coding agents spend rediscovering a codebase?EN
- 03Give your agent a valet keyEN
- 04OpenAI "rogue" agent activities found on Wikimedia projectsEN
- 05Agents Need Observability, Not Just ContextEN
- 06Building self-improving agent loopsEN
- 07Dotpals - Catches agents that edit tests to pass using JEVEN
- 08Spec for Agent Memory RepoEN
- 09Sashiko: Agentic review of Linux kernel codeEN
- 10Agent session transcripts are precious, keep themEN
- 11AI-Ready Data: 4 Foundations for More Reliable Enterprise AIEN
- 12Evaluating Memory Structure in LLM AgentsEN
All figures and quotations in this text come from the sources listed below.
Content prepared by the editorial team with AI assistance.
Comments
0- No comments yet — be the first.