Papers for

technical support teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

GraphRAGProv tracks sources to explain graph query answers

GraphRAGProv: GraphRAG Meets How-Provenance

Abstract: GraphRAG systems often use knowledge graphs to retrieve relevant context for an LLM that produces the final answer. That makes answers more inscrutable and therefore less appealing for domains where transparency is paramount. We present GraphRAGProv, an architecture that executes SPARQL queries over source-grounded RDF graphs to compute answers and their how-provenance polynomials. These polynomials record which statement occurrences were used and how they were combined. Because each occurrence is linked to its source text, users can follow these links to check whether the extracted statements reflect the text and whether the query combines them to answer the question. Querying thereby becomes a way to inspect and evaluate the text-to-graph transformation. Our interactive demo examines 400 cases from two multi-hop QA benchmarks, revealing extraction and query errors even when the final answer is correct.

Tue 27 OctArtificial IntelligenceDatabases
The gist
Sometimes computers answer questions by looking up connected facts in a big graph, but it can be hard to see how they got the answer. The authors made a new system called GraphRAGProv that not only finds answers but also shows which exact facts were used and where those facts came from. This way, people can check if the answers really come from the original texts and understand how the computer combined the facts. Testing the system found mistakes in how facts were pulled or combined, even when the final answer was correct.
Open → 2610.37237v1

Conversational AI workspace improves memory and context management for developers

An Interactive GraphRAG Workspace for Reifying, Auditing, and Steering Conversational AI Memories

Abstract: Conversational Large Language Models (LLMs) are widely employed in software engineering for code generation, debugging, and architectural design. However, as developers engage in multi-session development tasks, technical knowledge becomes siloed in isolated, linear chat histories. Reusing context across sessions leads to three critical challenges: (1) flat-vector retrieval fails to traverse multi-hop relational dependencies between distant architectural decisions; (2) temporal drift in software packages and APIs results in silent context poisoning when reusing aged dialogue logs; and (3) raw conversation concatenation induces prompt bloat and attention degradation. We present CognitiveCanvas, an interactive tool that transforms conversational AI memories from ephemeral text logs into persistent, manipulable, and audited knowledge objects. \textsc{CognitiveCanvas} integrates: (1) a Hierarchical Semantic Fact-Graph (HSFG) that distills dialogues into Goal, Fact, and Code artifacts, achieving a 92.2\% token reduction while enabling multi-hop GraphRAG traversal; (2) a Continuous Temporal Drift Auditor coupling 60+ regex heuristics with live calendar-anchored LLM verification for 1-click self-correction; and (3) a Spatial-Symbolic Prompt Compiler (SSPC) that translates 2D direct manipulation gestures (Voronoi clustering, node resizing, synthesis edges) directly into structured attention directives

Fri 16 OctSoftware Engineering
The gist
Developers using chat-based AI tools for coding and software design often face problems when trying to continue work across multiple sessions because the AI’s memory is unstructured and becomes confusing over time. The authors created a system called CognitiveCanvas that turns conversation logs into organized, interactive graphs, making it easier to track goals, facts, and code. Their tool also checks for outdated information and helps users fix errors with a single click. This approach reduces clutter and helps programmers keep conversations more useful and accurate.
Open → 2610.23559v1

Large language models can partially verify no-code bug fixes automatically

Can LLMs Fix It Without Code? Toward Automated Verification of No-Code Bug Fixes

Abstract: A no-code fix resolves an invalid bug report by directing the user to change a setting, update to a version where the problem is already fixed, or adjust their workflow. Manually verifying whether a proposed no-code fix resolves the reported bug takes considerable developer time. This study proposes an automated, execution-based pipeline for evaluating the capability of large language models (LLMs) to generate no-code fixes in a real browser environment. We evaluate 322 no-code fixes generated by the 12 configurations released with the benchmark of a previous study, covering bug reports categorized as Faulty Configuration, Wrong Version, or External System & Dependency. An executor agent applies each fix by following its natural-language instructions, and an issue-specific checker determines whether the reported bug persists. We repeat the pipeline with three executors: two Computer-Use Agents, OpenCUA-72B and Claude Sonnet 5, and one multimodal agentic LLM, Meta's Muse Glimmer. Only 17.6% of the candidate issues could be set up and passed both sanity gates. Across the 322 fixes, 14.6% to 49.7% resolved the bug depending on the executor, and the strongest configuration, Claude Opus 4.6 in the Vanilla pipeline, resolved up to 74.1% of its fixes under Claude Sonnet 5. Changing only the executor shifted a configuration's resolution rate by 38.8% on average, and the three executors reached the same verdict on only 46.9% of the fixes. Compared with human execution, the executors matched the human consensus for 66.1% to 88.1% of the sampled fixes. Even under the best executor, fewer than half of the LLM-generated no-code fixes resolve the reported bug, so such fixes need verification before they reach users. Execution-based verification can provide this, but the measured capability depends strongly on the executor, which evaluations must report and control.

Thu 8 OctSoftware EngineeringArtificial Intelligence
The gist
Fixing software bugs without writing code often means changing settings or updating versions, but checking if these fixes actually work takes a lot of developer time. The authors studied whether large language models (LLMs) can automatically verify these no-code fixes by running them in a real browser environment. They found that while some fixes do solve the problems, the success depends a lot on the model used to apply and check the fixes, and less than half of the fixes reliably work. This means automated checking can help but still needs careful control and verification before relying on no-code fixes automatically.
Open → 2610.11963v1

Recast learns to find and combine evidence for better AI answers

RECAST: Learning to Compute the Right Context through Adaptive Evidence Routing

Abstract: Large language models are increasingly applied to tasks grounded in long, heterogeneous information sources. Conventional Retrieval-Augmented Generation (RAG) relies on fixed similarity-based retrieval, while agentic variants adapt queries and tool use but remain largely retrieval-centric. However, in many tasks, the evidence required for a solution is not explicitly present in any single source item. Instead, it must be derived through filtering, aggregation, or computation across multiple source items. In this work, we introduce RECAST (Routing Evidence through Computation, Access, and Synthesized Tools), a learned framework that formulates evidence construction as a sequential decision process over heterogeneous retrieval and computation operations, allowing evidence to be actively derived rather than merely retrieved. A lightweight RouterLM iteratively selects and formulates primitive operations or specifies customized operations for a frozen CompilerLM to translate into executable code. Once it judges the evidence sufficient, RouterLM passes the accepted evidence to a frozen AnswerLM to produce the final solution. We train RouterLM with supervised fine-tuning (SFT) followed by group relative policy optimization (GRPO). Across six heterogeneous benchmark families, RECAST achieves a mean success rate of 75.6%, outperforming the strongest large-model baseline by 15.9%. Moreover, training enables the Qwen3.5-9B RouterLM to outperform a training-free Gemini 3.5 Flash RouterLM by 5.0%. On three held-out benchmarks, RECAST improves over the strongest baseline by 15.0% on average, demonstrating strong zero-shot generalization across tasks and heterogeneous source representations.

Wed 7 OctArtificial Intelligence
The gist
Finding the right information to answer complicated questions often means combining bits from many sources, not just copying one answer. The authors created RECAST, a system that learns how to pick and link pieces of information and perform calculations step-by-step to build the final answer. It uses a smart controller to decide which actions to take and when enough evidence is found to give an answer. This approach works better than previous methods on many different tasks and can handle new kinds of problems without extra training.
Open → 2610.10507v1

Function aware retrieval improves answers from complex technical documents

From Chunks to Functional Evidence: Function-Aware Retrieval for EDA Documentation QA

Abstract: Retrieval-Augmented Generation (RAG) is widely used to ground answers in documents. For complex technical documentation, however, the primary bottleneck is often not model reasoning but a mismatch between a query and the way knowledge is organized for retrieval. This mismatch is pronounced in Electronic Design Automation (EDA) documentation, where the information needed for an answer is scattered across heterogeneous yet tightly coupled artifacts. We therefore redesign the basic retrieval unit of RAG. Instead of operating on isolated chunks or binary relations, we collect typed artifacts into EDA functional units. Each unit is recorded as a hyperedge with links to its source chunks. We then train an encoder to align queries with functional units and combine unit retrieval with direct chunk retrieval. After mapping the selected units back to their sources, a unified reranker chooses the evidence given to the generator. On the newly constructed EDADocEval-QA dataset, our method improves ROUGE-L by 37.1% over Chunk RAG and 55.6% over the strongest graph baseline. On the public ORD-MMBench benchmark, it improves ROUGE-L by 30.0% over the strongest baseline. These results support function-aware evidence organization in the evaluated EDA documentation settings.

Wed 7 OctInformation RetrievalArtificial Intelligence
The gist
Finding the right information in complicated technical manuals can be hard because the information is scattered and connected in different ways. The paper shows a better way to organize and search for useful information by grouping related parts based on their function, rather than just looking at isolated pieces. The authors tested their method on electronic design manuals and public technical question benchmarks, showing much better answer quality compared to previous methods. This approach helps computers find more relevant evidence to answer detailed technical questions.
Open → 2610.09361v1

TeleTune improves software agent skills by learning from offline user logs

TeleTune: Evolving Agent Skills From Offline Telemetry

Abstract: Computer-use agents need to capture procedural knowledge of how people use software. User telemetry offers a scalable source of this knowledge. However, learning reusable skills from these logs requires addressing three challenges: (1) Goal Underspecification, since logs do not record the goal behind each action; (2) Non-Replayability, since past activity cannot be replayed to evaluate skill updates; and (3) Interleaved Trajectories, since logs may mix several tasks without marking their boundaries. To address these, we introduce TeleTune, a framework for learning a textual skill library from offline logs without recorded goals, cannot be replayed during optimization, and may interleave tasks. TeleTune uses action-prediction errors on logged trajectories to propose library edits and keep only those that improve held-out action-prediction accuracy, which we call skill-guided progress. The learned workflows also enable retrieval of demonstrations that cover the subgoals of a new task. At test time, the agent is provided with the learned library and the workflow-based retrieved demonstrations. Experiments on WorkArena and Online-Mind2Web show that TeleTune outperforms random retrieval, Agent Workflow Memory (AWM), and their combination. We find that the best baseline varies by setting, whereas TeleTune achieves average success rates of 77.1% and 80.6%, respectively, improving over the strongest baseline on each benchmark by 6.7% and 7.7%. Under the heaviest perturbation of the WorkArena training data,TeleTune keeps the highest average success rate at 68.5%, 6.3% above the strongest baseline. Our analyses show (1) skill optimization and workflow-based retrieval are complementary, (2) optimizing on fixed logs costs 5 to 75 times fewer tokens than validating the same edits with live episodes, (3) skill-guided progress tracks the live success rate.

Sun 4 OctArtificial IntelligenceComputation and Language
The gist
Teaching computer agents how people use software is hard because logs don’t clearly say what users want, can’t be replayed to check learning, and mix different tasks together. The paper’s authors created TeleTune, a system that learns common skills from these messy logs by testing which changes best predict user actions. This helps the agent get better at understanding and performing tasks based on past user behavior, without needing to try things out live. Experiments show TeleTune works better than previous methods even when the data is noisy or mixed up.
Open → 2610.05437v1

Language model performance improves with reusable plugins in harnesses

PluginRSI: Recursive Improvement of Agent Harnesses with Reusable Plugins

Abstract: The harness surrounding a language model is a central determinant of agent performance. Recent methods optimize harnesses by searching over complete programs, where individual mechanisms are difficult to isolate and reuse. We introduce PluginRSI, which represents a harness as a composition of atomized plugins and organizes harness evolution around these plugins. Individual plugins are improved independently and accumulated in a shared library, then recombined into new harnesses at each iteration. PluginRSI improves over existing harness optimization methods across software engineering, command-line interaction, and question-answering tasks. The resulting harnesses retain their advantage when transferred to other solver models without further optimization. The evolved plugin library accelerates subsequent optimization from the initial harness, which helps faster and higher convergence on unseen tasks. These results show that accumulating reusable mechanisms provides an effective basis for continued harness improvement.

Sat 26 SeptArtificial Intelligence
The gist
Making smart programs that guide language models to solve problems works better when the program is built from small, reusable pieces called plugins. The authors created a method called PluginRSI, which improves each plugin on its own and then mixes them to make better guiding programs. This approach helps the language model do better on different tasks like coding, using command lines, and answering questions, even when used with new models. Over time, PluginRSI builds a library of useful plugins that speeds up creating even better programs for new challenges.
Open → 2609.32423v1

Coding agents recover missing facts to support decisions better

The Missing Complement: State-Conditioned Minimal Sufficient Evidence for Coding Agents

Abstract: A coding agent halfway through an issue has already read much of what a retriever ranks highest. Relevance is scored per passage, but sufficiency belongs to the set: a ranker can fill its budget with variants of one required fact and leave the decision unsupported. We formulate state-conditioned minimal sufficient evidence recovery: given a captured agent state, recover a compact evidence combination that supplies the support its next decision still lacks. SERBench measures this on 500 held-out states from 45 repositories, recording what the agent has seen and crediting only sets that cover every fact the current decision was annotated to require. MSS-Complement treats acquisition as set construction, not ranking. Three semantic calls propose a jointly sufficient set, search for what it lacks, and return 4-8 intact source units within 6,144 tokens. One configuration, fixed on calibration data, recovers a complete set for 73.0% of those states at five items and 80.6% at eight, against 61.4% and 72.4% for Qwen3 embedding with reranking. A matched control ranking by similarity alone reaches 66.6%, placing the gain in the set-level policy, not the computation. From frozen repository source with no gold-derived pool, the lead is 5.0 points. On AMA-Bench it answers from a 76.2% smaller answer prompt, with accuracy 2.08 points above that benchmark's own memory agent. Removing one required group from an otherwise complete set costs 12.3 and 11.1 points of repair-localization precision under two executors. Retrieval for agents is better posed as recovering what a decision lacks than re-ranking what an issue resembles.

Thu 17 SeptInformation RetrievalArtificial IntelligenceComputation and Language
The gist
Sometimes, computer programs that find information grab many similar facts and miss key details needed to make a decision. The researchers created a way to identify just the missing facts that would help these programs. Their method picks a small, complete set of facts the program hasn’t seen but needs. This approach proved better than ranking similar facts one by one. It means programs can make smarter decisions by focusing on what they lack, not just what looks important.
Open → 2609.20050v1

LoRA tuning improves control systems course answers in open language models

LoRA Fine-Tuned Models for Control Systems Course Q\&A: A Multidimensional Evaluation of Model Scale and Rank Effects

Abstract: Large language models (LLMs) are increasingly used in specialized university courses, but control-systems questions require coordinated terminology, notation, derivations, and stepwise explanations. Direct general-purpose responses may be inconsistently structured and hard to verify. Using exercises and reference solutions from a Linear Control Systems course, we built a supervised fine-tuning dataset of 360 system-user-assistant conversations. We applied LoRA to Qwen2.5-3B-Instruct and Qwen2.5-7B-Instruct. With identical data splits, inference settings, and evaluation protocols, we compared base and fine-tuned models and tested LoRA ranks r=4, 8, and 16. Evaluation used ROUGE, BERTScore, and structured-output features to measure reference-answer similarity and stability of the Solution-Method-Teaching Points format. LoRA improved both similarity and structured-output stability at both sizes. On the current test set, 7B-r16 achieved the highest ROUGE-L (0.4093) and BERTScore-F1 (0.8643), while r=8 offered a better balance between performance and parameter efficiency. Bootstrap resampling showed ROUGE-L gains of 0.0764 [0.0613, 0.0915] for 3B-r16 and 0.0874 [0.0687, 0.1042] for 7B-r16; both intervals exceeded zero, indicating stable textual-similarity improvements on the current test set. These results suggest LoRA can align open-source instruction-tuned models more closely with the language and pedagogical organization of course reference answers. However, the metrics mainly capture textual similarity and formatting consistency, not domain-specific reasoning or mathematical correctness, which require expert assessment and task-specific rubrics.

Sat 12 SeptArtificial Intelligence
The gist
Large language models (LLMs) sometimes struggle to give clear and well-structured answers for control systems coursework. The authors created a dataset of questions and ideal answers from a linear control systems class and fine-tuned two LLMs using a technique called LoRA. This tuning helped the models produce answers that more closely matched course solutions, both in wording and organization. However, the measures used mostly check text similarity and formatting, not whether the math or reasoning is correct, which still needs expert checking.
Open → 2609.13918v1

RepoNav helps AI navigate code files to find the right functions

RepoNav: From Snippet Retrieval to File-Centered Repository Navigation for Code Agents

Abstract: Solving repository-level code tasks requires LLM-based agents to use code search tools to navigate large codebases and identify a small set of relevant files and functions. However, current retrieval tools typically return flat lists of isolated code snippets: such lists can surface relevant files, but provide insufficient structure for agents to distinguish the target function from semantically similar alternatives in the same file. We introduce RepoNav, a lightweight post-retrieval interface that reorganizes retrieved snippets into a file-centered navigation scaffold. By presenting compact structural cues and candidate targets, this scaffold guides on-demand file-structure browsing, helping agents compare sibling symbols before selecting a target function. Across diverse models on LocBench, RepoNav improves function-level localization and narrows the file-to-function gap. Controlled ablations demonstrate that these gains come from structured evidence organization rather than simply exposing additional file structure, and the approach also improves performance on a repository-level question-answering benchmark.

Tue 8 SeptSoftware EngineeringComputation and Language
The gist
Finding the right piece of code in a big project is hard, especially when code search tools return many separate snippets without clear context. To fix this, the authors created RepoNav, which organizes retrieved code snippets by the files they come from, showing structure and helping AI agents browse code more like a person would. This makes it easier for AI to pick the exact function needed and improves performance on tasks asking questions about code. The benefit comes from better organization of results, not just showing more file structure.
Open → 2609.08355v1