AdaLens: Interactive Storyline for Monitoring and Steering Long-Running Agentic Data Analysis
Authors: Yangtian Liu, Yan Miao, Shuhan Liu, Yunfan Zhou, Dae Hyun Kim, Di Weng, Yingcai Wu
Organizations: State Key Lab of CAD&CG, Zhejiang University, Hangzhou, Zhejiang, China · Department of Computer Science and Engineering, Yonsei University, Seoul, Republic of Korea · School of Software Technology, Zhejiang University, Ningbo, Zhejiang, China
Large language models are pushing data science toward increasingly autonomous and agentic workflows, with recent systems already supporting multi-step and long-running analyses. As these workflows become more autonomous, conventional interfaces no longer provide adequate support for two critical requirements: observability for understanding an agent's evolving reasoning and evidence, and steerability for redirecting low-value directions or deepening promising ones during execution. Existing interactive approaches improve process visibility and open intervention points, but they remain largely designed for discrete, turn-by-turn exchanges rather than the parallel branches and evolving decision structures of long-running agentic analysis. We study this need as interactive oversight in long-running agentic data analysis and present AdaLens, an interactive system for monitoring and steering ongoing runs. AdaLens combines a storyline-based representation that unifies analytical plans, execution progress, intermediate findings, and data-column involvement with steering interactions grounded in these analytical elements for directional guidance and execution control. We evaluate AdaLens through two case studies and a user study, examining how it supports analysts in monitoring and steering long-running agentic data analysis.
Figures & tables
Fig. 1: AdaLens interface for monitoring and steering long-running agentic data analysis through three coordinated views. (A) The chat view records user and system messages, dispatched plans (A1), and stage/final reports (A2). (B) The storyline view serves as the primary workspace, combining steering tools (B1), insight-type legends (B2), report anchors (B3), plan/summary cards (B4, B7), data-column traces (B5), atomic insight glyphs (B6), on-demand detail popovers (B8), and the alternation between finding regions (B9) and converge regions (B10) to reveal stepwise progression and data-grounded analytical lineage over time. (C) The inspector view summarizes coverage across columns and insight types (C1) and reveals the selected task or finding with linked evidence such as plots, code, and outputs (C2).
Fig. 2: AdaLens framework for interactive oversight in long-running agentic data analysis. Analysts steer the run through intention-level actions and execution-level controls (A). The orchestrator manages context integration, plan creation, report generation, and progress evaluation (B). The orchestrator dispatches plans to parallel workers whose analyzer and summarizer produce summaries and atomic insights with supporting evidence (C), and these intermediate analytical elements are surfaced through the chat, inspector, and storyline views (D).
Fig. 3: Case 1 (Stages 1–2): using AdaLens to initiate the investigation of the ambiguous hot_degree metric in a Twitter dataset and regulate candidate plans. (A) ED starts from a focused chat request asking which columns relate to hot_degree . (B) When two candidate plans appear in parallel with their execution states, ED pauses both, reviews them, terminates the categorical/boolean branch, and launches the branch on numerical variables.
Fig. 4: Case 1 (Stages 3–5): using AdaLens to inspect and extend the analysis of the ambiguous hot_degree metric and synthesize the resulting findings. (C) Column label sizes convey the extent of each variable’s involvement, highlighting hot_degree as the analytical focus; the resulting summary identifies statuses_count , media_count , and followers_count as its strongest related variables. (D) Based on these visible results, ED creates a targeted follow-up plan to model hot_degree from these variables; the same four column characters continue into the follow-up step, which yields a log-linear model for hot_degree . (E) AdaLens returns a final report that consolidates both the correlation findings and the resulting predictive model.
Fig. 5: Case 2 (Stages 1–3): using AdaLens to explore an NBA spatiotemporal tracking dataset in an open-ended manner and steer the analysis toward a promising matchup. (A) EE begins with a broad exploration request, after which the storyline presents early summaries, atomic insights, and the columns involved in them. (B) EE notices two frame-level ball-coordinate columns that are not of particular interest and applies Ignore to ball_zone and ball_z to deprioritize them. (C) He then applies Focus to a promising summary card about Bogut and James, steering subsequent plans toward this matchup.
Fig. 6: Case 2 (Stages 4–5): using AdaLens to elaborate a key insight and generate a final report. (D) Within the resulting summaries, an atomic insight reveals that blocked-shot interactions are more frequent in the first period than in the third, prompting EE to apply Elaborate to it for a deeper explanation of this temporal pattern. (E) AdaLens finally generates a report that consolidates the exploratory findings into a coherent interpretation of the game.
Fig. 7: Usability results from a 5-point SUS questionnaire [ 83 ] . Negative questions (Q2, Q4, Q6, Q8, and Q10) are shown inverted for consistency.
Large language models (LLMs) have enabled data-science agents to automate multi-step analyses over heterogeneous files. However, incorrect choices regarding data sources, scope, or statistical definitions often lead to silent errors: computations execute successfully but produce plausible yet incorrect outputs that fail to answer the intended question. To mitigate this, we present RADAR, an auditable runtime that makes an agent's analytical choices inspectable and supports their revision through execution feedback. RADAR operates through three core mechanisms. First, an evidence-preserving exploration module retrieves task-relevant content while retaining source locations and observation coverage. Next, the runtime uses typed operators to record the agent's declared inputs, operation arguments, and resulting observations. Finally, runtime validation checks proposed operations against these observations. When a conflict is detected, the runtime rejects the operation or provides diagnostic feedback, allowing the agent to revise its choices before errors propagate. This design enables agents to fail loudly while leaving semantic interpretation to the LLM. On KramaBench, RADAR achieves overall scores of 0.723 with full source retrieval and 0.747 with gold sources supplied, corresponding to relative gains of 35.9% and 28.8% over the strongest baselines. Beyond KramaBench, RADAR achieves relative performance gains of 14.0% on DA-Code and 59.3% on DABStep, demonstrating its applicability across diverse agentic data-analysis workflows.
Real-world data analysis is a multi-step process over heterogeneous inputs rather than merely producing a final answer. A practical system should autonomously organize multi-step workflows, execute generated code in a sandboxed and controllable environment, and remain inspectable through visible action traces and intermediate artifacts. Existing LLM-based analysis tools, however, often emphasize isolated subtasks, leaving limited support for complete execution-grounded workflows. We present DA-Studio (Data Analysis Studio), an interactive web-based demo system for end-to-end data analysis that is autonomous, sandboxed, and inspectable. DA-Studio integrates an action-structured analysis backend, a sandboxed execution workspace, and a browser interface for task setup, streamed action traces, artifact preview, code editing and rerunning, and report export. Through iterative action generation, code execution, and feedback incorporation, it incrementally constructs executable analysis steps from raw files and natural-language requests while exposing intermediate results and artifacts throughout the process.
Real-world data analysis is inherently iterative, yet existing benchmarks mostly evaluate isolated or short interactive tasks, leaving agents' ability to track evolving analytical context over long horizons untested. We introduce LongDS, a benchmark for long-horizon, multi-turn data analysis where agents must maintain, update, restore, and compose evolving analytical states. LongDS comprises 68 tasks constructed from real-world Kaggle notebooks, spanning 2,225 turns across six domains including Geoscience, Business, and Education. Tasks are designed around state-evolution patterns (e.g., counterfactual perturbation, rollback, multi-state composition), with an average dependency span of 11.3 turns. Evaluating five state-of-the-art models, we find that the best model reaches only 48.45% average accuracy, performance drops nearly 47 points from early to late turns, and long-horizon errors account for 52%--69% of failures. Further analysis shows that additional agent steps do not necessarily improve performance, suggesting that the key bottleneck is maintaining a correct analytical state rather than increasing interaction budget. We release LongDS to support research on reliable long-horizon agentic data analysis. Code and data will be released at https://github.com/zjunlp/DataMind.
Kewei Xu, Xiaoben Lu, Shuofei Qiao +4
Zhejiang University · Zhejiang University - Ant Group Joint Laboratory of Knowledge Graph · Ant Group