RAGFlow 1.0 preview: from RAG engine to agent-native database
newpeak · reddit · 2026-11-02
The RAGFlow team shared the arXiv paper behind the upcoming 1.0 release, arguing that retrieval's center of gravity has shifted: agents now loop over writing queries, reading results, and deciding when they have enough, so classical objectives like better chunking, embeddings, and Recall@k are no longer the binding constraint — paying for the reading is. Two conclusions from the paper: retrieval is a harness problem before an index problem, and compilation is not a better retriever — structural artifacts (summary trees, outlines, wikis, graphs) showed no detectable accuracy gain under a competent harness. Instead, knowledge compilation is reframed as a supply layer: an ingestion-time pipeline producing typed, provenance-bound artifacts (claims with verbatim evidence, entity relations, timelines, ontologies, wikis, memory), with the harness governing what enters the context window. Hence 'agent-native database': agents are supplied with pre-compiled, verified facts rather than ranked chunk lists. The authors candidly note the cost savings are bought with retrieval rounds, and deployment outcomes for claims/graph/wiki are published as an empty ledger marked 'no measured effect.'
More from coding & agent
- GitHub Actions has a lesser-known ubuntu-slim runner: 1 CPU, 5GB RAM, cheaper CI — DanielLockyer · 2026-11-02
- Before automating a workflow with AI, ask if anyone understands it end to end — djgoel123 · 2026-11-02
- One stale date silently broke a WhatsApp reply agent: 19 messages unanswered — petrusenko_max · 2026-11-02
- The 10X engineer is now just a SKILLS.md: 6 workflow rules for AI coding agents — mdancho84 · 2026-11-02
- Auditing my MCP credential broker: the worst hole was the config file — Relevant_Mousse_9117 · 2026-11-02
- AWS's open-source Strands Harness claims 45% cheaper than Claude Code, reigniting harness debate — blaizedsouza · 2026-11-02