๐ค AI Summary
RAG pipeline development faces two key challenges: (1) strong coupling between retrieval and generation components, leading to difficulty in error attribution, and (2) slow debugging feedbackโoften requiring hours due to heavyweight preprocessing. To address these, we propose the first developer-centric, composable RAG primitive library and interactive debugging framework. Our approach decouples and encapsulates core RAG operations (query transformation, retrieval, and generation) as modular primitives, enabling link-level real-time visualization and coordinated debugging with millisecond-scale feedback. Guided by an empirical study of debugging practices among 12 professional engineers, we derive design principles aligned with real-world development workflows. Experiments demonstrate that our method reduces RAG debugging cycles by over 99%, improves error attribution accuracy by 42%, and significantly enhances both development efficiency and system maintainability.
๐ Abstract
Retrieval-augmented generation (RAG) pipelines have become the de-facto approach for building AI assistants with access to external, domain-specific knowledge. Given a user query, RAG pipelines typically first retrieve (R) relevant information from external sources, before invoking a Large Language Model (LLM), augmented (A) with this information, to generate (G) responses. Modern RAG pipelines frequently chain multiple retrieval and generation components, in any order. However, developing effective RAG pipelines is challenging because retrieval and generation components are intertwined, making it hard to identify which component(s) cause errors in the eventual output. The parameters with the greatest impact on output quality often require hours of pre-processing after each change, creating prohibitively slow feedback cycles. To address these challenges, we present RAGGY, a developer tool that combines a Python library of composable RAG primitives with an interactive interface for real-time debugging. We contribute the design and implementation of RAGGY, insights into expert debugging patterns through a qualitative study with 12 engineers, and design implications for future RAG tools that better align with developers' natural workflows.