Your AI agents need a terminal, not just a vector database

본 기사는 agentic workflow 실패의 원인이 LLM의 추론 능력보다 제한적인 retrieval 인터페이스에 있을 수 있다고 지적합니다. 여러 대학 연구진은 embedding과 vector database를 우회해 agent가 raw corpus를 command-line 도구로 직접 검색하는 DCI 방식을 제안했습니다. 기존 RAG는 top-k snippet에 의존해 정확한 문자열, 버전, 오류 코드, 파일 경로 같은 단서를 놓치기 쉽다는 설명입니다.

DCI는 AI agent를 단순한 질의응답 시스템이 아니라 corpus를 탐색하고 가설을 반복 검증하는 소프트웨어 작업자에 가깝게 설계해야 한다는 흐름을 보여줍니다. enterprise 환경에서는 semantic retrieval만으로 처리하기 어려운 로그, 코드, 문서의 희소 단서를 다루기 위해 terminal 접근권과 감사 가능한 검색 절차가 중요해질 가능성이 큽니다.

When agentic workflows fail, developers often assume the problem lies in the underlying model’s reasoning abilities. In reality, the limited information provided by the retrieval interface is often the primary limiting factor.Researchers at multiple universities propose a technique called direct corpus interaction (DCI) that lets agents bypass embedding models entirely, searching raw corpora directly using standard command-line tools.The limits of classic retrievalIn classic retrieval systems such as RAG, documents are chunked, converted into vector representations (or embeddings), and indexed offline in a vector database. When an AI system processes a query, a retriever filters the entire database to return a ranked "top-k" list of document snippets that match the query. All evidence must pass through this scoring mechanism before any downstream reasoning occurs.But modern agentic applications demand much more. "Dense retrieval is very useful for broad semantic recall, but when an agent has to solve a multi-step task, it often needs to search for exact strings, numbers, versions, error codes, file paths, or sparse combinations of clues," the authors of the DCI paper said in comments provided to VentureBeat. "These long-tail details are precisely where semantic similarity can be brittle."Unlike static search, agents must also revise their search plans dynamically after observing partial or localized evidence. Exact lexical constraints and multi-step hypothesis refinement are difficult to execute with semantic retrievers. Because the retriever compresses access into a single step, any critical evidence filtered out by the similarity search cannot be recovered later, no matter how advanced the agent's downstream reasoning capabilities are. As the authors explain, current retrieval pipelines can become a bottleneck because "they decide too early what the agent is allowed to see."Direct corpus interactionThis direct access addresses a core problem in enterprise environments: data staleness. Embedding indexes are always a snapshot of a specific moment in time, taking considerable compute and time to build and maintain."In many enterprise settings, the data is not a stable document collection. It is daily financial reports, live logs, tickets, code commits, configuration files, incident timelines, and internal documents that keep changing," the authors said. DCI lets the agent reason over the current state of the workspace rather than yesterday's vector index.The agent operates in a terminal-like environment where its observations are raw tool outputs such as file paths, matched text spans, and surrounding lines. The core tools provided by DCI are few but highly expressive. Agents use commands like “find” and “glob” to navigate directory structures and locate files. For exact matching, they use “grep” and “rg” to locate specific keywords, regex patterns, and exact strings. When local inspection is needed, tools like “head,” “tail,” “sed,” “cat,” and lightweight Python scripts allow the agent to peek at the context surrounding a match or read specific file sections.The agent can combine these tools via shell pipelines to execute complex search logic in a single step. An agent can pipe commands to enforce strict lexical constraints, such as searching a file for one term and piping the output to search for a second term. It can combine multiple weak clues across a corpus by finding a specific file type, searching for a keyword like "report," and filtering for a year like "2024." It can also immediately verify a hypothesis by inspecting the exact lines around a keyword match.DCI delegates semantic interpretation directly to the agent instead of relying on embedding-based similarity search. The agent can formulate hypotheses, test exact lexical patterns, and extract detailed information that a traditional semantic retriever might miss.The researchers propose two versions of this system. DCI-Agent-Lite is designed as a lightweight, low-cost setup built on the GPT-5.4 nano model and restricted purely to raw terminal interactions like bash commands and basic file reads. Because reading raw files can quickly fill up a smaller model's memory, this version relies on lightweight runtime context-management strategies to sustain long-horizon exploration.DCI-Agent-CC is the higher-performance version, designed for teams with more compute budget. It runs on Claude Code powered by Claude Sonnet 4.6. Claude Code provides stronger prompting, more robust tool orchestration, and superior built-in context handling, which improves the agent's stability during complex, multi-step searches across heterogeneous datasets.DCI in actionThe researchers tested both versions of DCI across agentic search benchmarks like BrowseComp-Plus, knowledge-intensive QA with single-hop and multi-hop reasoning, and information retrieval ranking in tasks requiring domain-specific reasoning and scientific fact-checking.They tested DCI agai