Your paper timeline
Scroll AI takes the way you would scroll a great paper aggregator: quick signal first, deeper critique when something earns your attention, and challenges when a claim feels off.
36 papers in cs.SE
Trending mixes fresh papers with community signal.
0
cs.SEcs.AIcs.CY Robin Qu\'eriaux, Solveig Bachellery, L\'ea D\'el\'eris et al. · Oct 22, 2026

Regulated institutions must produce technical evidence for LLM deployments under the EU AI Act, yet existing benchmark suites are engineer-facing command-line tools while accountable reviewers are non-technical managers. VERA is an open-source, self-hosted dashboard that closes this workflow gap by letting reviewers select a model, run public benchmarks, and read requirement-level scores—with decomposable evidence and run-level energy consumption—in a browser. Its core contribution is wrapping raw measurement into a review and filing process designed for institutional approval.

Institutions that deploy large language models in regulated settings often need technical evidence of responsible AI practices before approving a deployment. COMPL-AI provides a technical interpretation of the EU AI Act that organises this evidence under six principle groups and eighteen technical requirements, twelve of which current benchmarks can measure. The benchmark suites that produce this evidence are typically operated from a command line, while the staff who approve deployments are non-engineers. We present VERA, an open-source self-hosted dashboard deployed to facilitate responsible AI processes within a large European bank. A reviewer selects a model and runs public benchmarks against it. VERA scores the twelve requirements that current benchmarks can measure and instruments the energy consumed by each evaluation, adding run-level evidence for environmental impact. We run four served open-weight models through the requirement pipeline, and the dashboard displays a score for each measurable requirement. A within-subject study then compares how participants read these benchmark results: from the raw output files in one condition, and through the VERA dashboard in the other. The dashboard reduced the time needed to perform the responsible AI assessment, reducing the time required from 56 seconds using raw files to 30 seconds using our dashboard, on average. Our dashboard scored highly (4.36 out of 5) on usefulness in the survey conducted within the organization. The dashboard and the study material are released publicly to promote replicability and reproducibility in different organisational contexts.
0
cs.LGcs.SE Zezhou Wang, Hanzhang Zhou, Panrong Tong et al. · Oct 22, 2026

Trace2World tackles the bottleneck of building faithful GUI training environments from sparse real-app traces. It separates global semantic reconstruction—resolving page identities, state fields, and conditional effects across traces—from browser implementation, then validates by independently replaying every source workflow. On 200 workflows across ten apps, this contract reaches 91.1% end-to-end fidelity versus 59.8% for the strongest task-local baseline and retains 94.0% of simulated training gains when transferred to real devices.

Scaling GUI reinforcement learning requires environments that preserve real-app behavior. Yet coupling behavior inference with coding can turn partial traces into runnable mocks with incorrect state transitions. We introduce \textbf{Trace2World}, which separates global behavior reconstruction from implementation. It reconciles traces into a shared, source-linked app model, then compiles an executable environment. Independent replay of source workflows localizes mismatches for bounded implementation repair. Validated worlds then support learner-adaptive task and environment augmentation within source-supported behavior. From 1,570 traces, Trace2World constructs 50 environments. On 200 workflows across ten apps, 91.1% are reproduced end to end, versus 59.8% for the strongest matched task-local baseline. Source-grounded validation retains 94.0% of simulated training gains on real devices, versus 54.7% under self-validation. Learner guidance raises benchmark success from 56.9% to 61.1%. Training in Trace2World further improves the model by 20.2 points on our benchmark, 5.4--16.2 points across four external GUI benchmarks, and 16.3 points on 100 real-device tasks. Reliable reconstruction separates what behavior source evidence supports from whether the implementation preserves it.
0
cs.AIcs.SE Dingxuan Zhang, Yanhui Jiang, Jun Wang et al. · Oct 22, 2026

Coding agents typically retrieve skills before execution but rarely choose at runtime whether to invoke coarse macro skills or fine-grained primitives. This paper reframes skill use as a runtime control problem, introducing Adaptive Skill Granularity: a decision-tree router selects micro, macro, or hybrid execution, and a finite-state executor downgrades from macro to micro after observable failures. The framework matters because it shifts skill libraries from static documents into controllable, verifiable execution abstractions that can trade off efficiency against robustness.

Reusable skills allow large language model agents to package task-specific procedures, tool affordances, and execution guidance into modular units. Prior work has largely studied how agents retrieve, compose, or synthesize skills before execution. In coding agents, however, execution poses an additional runtime control problem: the same task may be solved through primitive tool calls, macro skills, or hybrid execution that starts with a macro and falls back to micro-level recovery. We introduce Adaptive Skill Granularity, a framework that treats skill granularity as an action-abstraction policy conditioned on task structure, execution state, and macro-skill failures. The system combines a feature-based granularity controller and a finite-state recovery executor. We evaluate the framework with a deterministic coding-agent protocol using verifier-defined success, total cost, and process metrics such as macro adoption, failure recovery, route match, and transition correctness. Results show that fixed macro execution is efficient when applicable but brittle under mismatch, while runtime routing and explicit macro-to-micro recovery improve robustness and recover controlled macro failures that fixed-granularity execution leaves unresolved. Our findings suggest that skill libraries for coding agents should be treated not only as retrievable resources, but also as controllable, verifiable, and recoverable execution abstractions.
0
cs.SEcs.AIcs.MA Atharv Chandratre, Jai Datar · Oct 22, 2026

Feature flags become technical debt once fully rolled out, yet manually cleaning them at scale is prohibitively expensive. This paper describes a multi-agent LLM system deployed at DoorDash that automates stale flag removal by querying live rollout data via MCP, coordinating parallel cleanup agents in isolated git worktrees, and producing merge-ready pull requests. Evaluated on 50 stale flags across hundreds of repositories, the system produced usable PRs for 90% of cases at an average cost of $4.79 and 13.8 minutes per cleanup, offering one of the first quantitative industrial benchmarks for LLM-driven feature flag cleanup.

Feature flags are runtime configuration mechanisms used for gradual feature rollouts, experimentation, and kill switches. Once a feature is fully rolled out, the flag and its gated code become technical debt and can introduce operational risk through inadvertently enabling dormant code paths. At DoorDash, over 56,000 feature flags span 623 repositories, with 1,659 currently stale as of May 2026, with internal estimates of one to two hours per manual cleanup. Existing rule-based cleanup tools proved insufficient in DoorDash's codebases. Our contribution is an end-to-end automated LLM-based feature flag cleanup system that integrates querying live feature flag rollout data using MCP, Jira ticket processing, and end-to-end pull request creation. Our system successfully produced engineer-approved flag removal PRs for 45 (90%) of the 50 stale flags it was evaluated on, proving the system's operational viability at scale with each cleanup averaging only $4.79 and 13.8 minutes. We evaluated the system's quality and reliability boundary based on success rates, cost per cleanup and time metrics. Furthermore, we discuss our lessons learned when architecting this system, to provide practical guidance for developing similar multi-agent systems.
0
cs.SEcs.AI Mohammad Mehdi Gholinejad · Oct 22, 2026

The paper defines superintelligent software engineering as the discipline of building software with agents that exceed human reviewers, arguing that raw capability is necessary but insufficient without governance that scales mechanically. It proposes that correctness depends on decisions and contracts outside the code, that such knowledge decays, and that once agent throughput $r$ outstrips fixed human review capacity $c$, the share of stale-built changes caught by reading falls toward zero. An exploratory snapshot of 452 popular GitHub repositories finds widespread stale agent context files, and the paper introduces OSTEON, a released discipline of governed knowledge repositories, mechanical gates, and decay control. The author commendably marks OSTEON's unmeasured claims as opinion and frames a falsifiable research agenda.

Software agents are being trained to exceed human engineers; we argue that capability alone does not produce better software engineering. We define superintelligent software engineering as the discipline of building and evolving software with agents whose capability exceeds that of human engineers, in which governance (gates, contracts, decisions and decay control) scales with capability. The argument rests on three claims. First, correctness in a project rests on decisions and contracts that the code does not carry. Second, knowledge decays. Third, once an agent outpaces its reviewers, reading catches a shrinking share of the changes built on stale knowledge. A simple model shows that, past a fixed review capacity, escaping changes grow linearly with throughput while the share that reading catches falls toward zero; governance can lower the slope, capability alone cannot. An exploratory snapshot of 452 of the most-starred public GitHub repositories finds a root-level or .github agent context file in 48.67% (95% confidence interval 44.1 to 53.3); in the median file that names repository paths, 9.5% to 22% of those paths do not resolve, depending on how a reference is read. We then present OSTEON, a discipline for the regime, released with a DOI (10.5281/zenodo.23436020): each project gets a governed knowledge repository of decisions and contracts, every change is checked mechanically against it, and the knowledge itself is checked for decay at every session start; planning is gated, and sessions record what they learn without writing rules. We report no measured effect of OSTEON, mark claims about its mechanisms as opinion and the author's practice heuristics as design rationale, and state the questions that would falsify the thesis.
0
cs.SEcs.AIcs.ET Maria Gabriela Alves Zuppardo, Vinicius Cardoso Garcia · Oct 22, 2026

Multi-agent LLM pipelines are widely assumed to outperform single-call setups, yet it is unclear whether gains come from typed inter-agent contracts or merely from decomposition into specialized prompts. This paper conducts an 18-condition controlled experiment on requirements classification and MoSCoW prioritization using three small language models on the PROMISE NFR+ dataset. The core finding is that most accuracy gains are associated with decomposition and task-specific prompts rather than with Pydantic-validated typed states, though the typed contract shows other quality-assurance properties such as earlier fault containment.

Multi-agent LLM pipelines are often credited with gains in software engineering tasks, but it is rarely clear whether a gain stems from the typed contract between agents or from the specialized prompts that decomposition enables. We study this attribution problem in Requirements Engineering, comparing three architectures for classifying requirements as functional or non-functional and then prioritizing them with MoSCoW: a single-call baseline; a two-call variant that reuses the pipeline's specialized prompts but passes an unvalidated intermediate; and a pipeline with a Pydantic-validated typed state. The 18 conditions cover PROMISE NFR+ (625 requirements), three locally hosted small language models, and two languages. The F1 gain over the baseline is associated with the two-call, specialized-prompt variant (up to +0.075), whereas the typed state adds a small difference (-0.003 to +0.013) that is significant in one of six comparisons. Beyond accuracy, the typed pipeline contains out-of-range model outputs at the agent boundary, while the unvalidated variant fails later and drops the requirement, and it shows a small, reproducible increase in inter-model MoSCoW consistency whose cause our design cannot isolate. The study is associative: the contrasts bundle prompts, call count, and staged context, and the results come from three 7--8B models on one dataset. The implementation and replication package are archived on Zenodo (https://doi.org/10.5281/zenodo.23380444).
0
cs.SEcs.AI Jiajun Wu, Jian Yang, Yaxin Du et al. · Oct 22, 2026

Frontend coding agents are usually graded only on whether the requested target gets built, but real engineering demands that the rest of the site keeps working. ProductWebBench evaluates this second obligation—website continuity—through 400 frozen tasks where a simulated user reveals requirements stage by stage and every cleared gate remains armed for the rest of the run. Across 8,737 runs from 13 models, 28.2% of Change attempts that pass every requested-work check still fail a continuity check, showing that scoring a patch against the target alone is insufficient.

Frontend coding agents are usually graded on one question: did the requested target get built. Real engineering changes carry a second obligation, because the rest of the site has to keep working. We call that second obligation website continuity, and introduce ProductWebBench, a benchmark that scores both on living frontend repositories: 320 Change tasks over existing code and 80 long-horizon Build tasks. Every task freezes a repository snapshot, staged requirements, browser evidence and deterministic checks before evaluation, and enters only once a reference passes every check and plausible-wrong ones fail. A simulated user reveals the requirements one stage at a time, and every check cleared earlier stays armed for the rest of the run. Across 8,737 runs from 13 models the two come apart: of the Change runs passing every requested-work check, 28.2% still fail a continuity check -- a blank route, horizontal overflow, console errors -- and 10.8% push a browser state they had already passed back to failing. Because the same checks also run on the untouched repository, each regression carries exact provenance, not a post-hoc label: on the 586 runs where both readings exist, 18.3% are caught breaking a verified state. Interaction is a further blind spot, failing in 29.5% of runs whose static DOM already passes. ProductWebBench therefore scores a patch against the living system it lands in, not the target alone.
0
cs.SEcs.AI Abhijit Chakraborty · Oct 22, 2026

When agents share a tool catalog and pool their usage experience, adding that usage to the retrieval index boosts tools with usage but can push unused tools out of the top results. This paper shows that folding usage examples into the index severely lowers held-out Hit@5 on two of three catalogs, and proposes Synapse, which scores documentation and usage as separate z-normalized fields before combining them with a learned weight. The finding matters because multi-agent systems risk silently failing on rarely-used tools unless the combination rule explicitly protects them.

Agents that call tools from a shared catalog can pool what they learn about which tool serves which request. We measure what pooled usage examples do to tool retrieval, reporting separately the held-out tools, for which no agent has usage, and all other tools. Adding usage examples to the index as extra entries for used tools raises Hit@5 (whether a gold tool is in the top five) for those tools and lowers it for held-out tools, by a large margin on two of three catalogs and with both embedders we tested. Giving used tools the same number of equally long entries filled with other tools' text lowers held-out Hit@5 about as much, but gives little or none of the gain. We call our method of scoring usage as its own field SYNAPSE. On StableToolBench, the held-out gold tool appears in its top five more often than with a router that reserves slots for usage (0.785 against 0.683), and this held-out lead holds on all three catalogs with both embedders. This protection persisted when we replaced each tool's usage with other tools' text, and a constant score offset for tools with usage gives similar held-out Hit@5 in most settings. The gain for tools with usage, in contrast, needs usage about the right tool. The router keeps more of the gain on labeled queries on TOUCAN with both embedders and on ToolRet with one, so the better choice depends on the workload. Splitting the usage among ten simulated agents shows that pooling helps exactly as much as giving one agent the same records.
0
cs.SEcs.AI Bin Duan, Jintao Lin, Guowei Yang · Oct 22, 2026

VLTest addresses the problem of testing vision-language models (VLMs) where mutating an image, a text prompt, or both can change the expected answer, making naive output-change counting unreliable. Its core idea is to generate controlled visual variants via VQGAN latent code editing and textual variants via a rewrite–expand–prune pipeline, then confirm failures with an automated oracle and attribute joint failures to the specific image-text combination using matched four-cell evidence. This matters because VLMs are increasingly embedded in software systems, and existing robustness evaluations systematically overcount failures by ignoring whether an input still has the same correct answer.

Vision-language models (VLMs) are increasingly embedded in software systems. Testing them raises two problems. Mutating either input can change the expected answer, so an output change is not by itself a failure. Some failures appear only when both inputs are mutated; attributing them to the combination requires testing each mutation alone. We present VLTest, a black-box VLM testing approach. It generates image variants by editing VQGAN latent codes and text variants with a rewrite-expand-prune pipeline, filters variants likely to change the expected answer, and tests each variant alone before testing combinations, so every joint failure has four matched cells. A VLM judge confirms a failure only after checking that the input keeps the expected answer. On three tasks with eight VLMs, including two commercial API models, the oracle confirms 81.7% of the candidates, with 88.8% to 94.6% precision against human labels, and four-cell confirmation rejects 22.5% of joint candidates. Under the same budget, VLTest's generators find 1.8 to 2.5 times as many confirmed failures as SINVAD and TextFooler, and its joint tests find 91 to 197 attributed joint failures per 1,000 joint calls, 1.3 times as many as the same pairing applied to the baselines' variants.
0
cs.AIcs.CRcs.HC Simiao Ren, Xingyu Shen, Tommy Duong et al. · Oct 22, 2026

AI coding agents can now edit native PDF financial documents while preserving issuer layouts, making identity-swapped forgeries harder to spot than image-level fakes. This paper tests whether experienced loan underwriters and processors detect such edits in a first-pass document-only review. The authors gave three hired reviewers 132 agent-edited forged PDFs derived from 47 genuine documents and checked whether their concerns actually matched the identity-altering edits. The core finding that only about one in ten judgements contained an edit-supported concern is a clear warning about relying on visual human review for financial fraud detection.

AI-assisted editing can produce loan documents that preserve familiar issuer layouts while changing the applicant's identity. We investigated whether experienced underwriters and loan processors identify such forgeries in first-pass, document-only review. Three practitioners recruited through Upwork each received one applicant package drawn from 134 forged PDFs derived from 47 genuine financial documents supplied with full consent. The edits preserved amounts, dates and balances; identifier inconsistencies introduced by the pipeline were knowingly retained before distribution. Reviewers were not told that files had been altered and returned 132 file-level judgements. Checking their explanations against the originals yielded 14 edit-supported concerns (10.6%): 12 Suspicious judgements and two Insufficient information judgements. All supported concerns involved identifier disagreements within or across documents, and no reported visual cue identified an actual edit. Thus, approximately one in ten judgements contained evidence of the forgery, despite known inconsistencies remaining in the files. These observations motivate evaluating consistency checks and independent source verification alongside human review. With three reviewer-package pairs and no genuine-file controls, the findings describe this exploratory setting rather than population-wide detection accuracy.
0
cs.SEcs.LG Rakhshanda Jabeen, Morgan Ericsson, Jonas Nordqvist et al. · Oct 14, 2026

Architectural drift is expensive to detect when the mapping between source files and architectural modules is missing or outdated. This paper frames code-to-architecture mapping as semi-supervised node classification over a directed multi-relational dependency graph, expanding a small labeled seed via iterative self-training. By holding features, training loops, and classifier heads fixed across GCN, GAT, and a graph-free MLP, the authors isolate whether dependency structure genuinely improves mapping accuracy.

Architectural technical debt arises when a system's implementation drifts from its inten ded modular decomposition, while the mapping between source files and architectural modu les is missing, incomplete, or costly to maintain manually. We formulate code-to-archite cture mapping as semi-supervised node classification over a directed multi-relational de pendency graph, with files as nodes, typed dependencies as edges, and lexical features d erived from code identifiers and directory layout. Starting from a small labeled sample, an iterative self-training procedure expands the mapping to the remaining files. We com pare a graph convolutional network (GCN), a graph attention network (GAT), and a graph-f ree multi-layer perceptron (MLP), using identical features and training procedures for t he learned models, against a Naive Bayes reference. Across 100 runs on ten open-source J ava and C/C++ systems, all three neural models outperform the reference on both F1 metri cs. GAT achieves the highest averages of system-level median macro and micro F1, at 83.5 and 92.2, respectively, whereas MLP remains competitive or superior on several systems. On Chrome, the largest system with 18,343 files, GAT and GCN exceed MLP by 22 and 19 ma cro-F1 points, respectively, and have substantially fewer persistently misclassified fil es. Connectivity and homophily are associated with where neural message passing helps, w hile multi-relational aggregation outperforms a single merged edge type on every system for both GCN and GAT. A follow-up study finds that several model rankings depend on the training seed, qualifying smaller advantages without removing the large graph benefit ob served on Chrome.
0
cs.CLcs.AIcs.CV Qiushi Sun, Jingyang Gong, Yang Liu et al. · Oct 14, 2026

Multimodal code intelligence demands programs that are correct, well-structured, and visually faithful, yet existing training signals are either too coarse or confined to single tasks. This paper introduces PrismaForge, which synthesizes per-instruction evaluation rubrics that separately assess code-level and visual-level criteria, then uses them to filter training data and reward reinforcement learning. The resulting dataset, PrismaCoder-2M, and the trained 9B and 35B models advance the open state of the art and compete with proprietary systems on charts, webpages, and scientific graphics.

Multimodal code intelligence connects the symbolic world of programs with the visual world their execution creates. Interest in this capability is burgeoning, as models are increasingly asked to produce charts, webpages, animations, and semi-structured documents. Recently, proprietary models have pushed far ahead, producing interactive artifacts even from a text description or a screenshot alone. Yet their data and training remain closed, and open progress is held back by the quantity and quality of available data and by the pipelines and methods for producing it. Quality is the harder of the two, since a sample must be correct as a program, well built, and above all visually right once rendered. No existing signal covers all three. Execution often returns just a pass or fail, code similarity does not map to the visual output, and task-specific verifiers do not generalize. To push open progress further, we start from the data side with PrismaForge, a hierarchical data pipeline centered on a synthesized rubric that decomposes these factors into checkable criteria. The same rubric serves as both filter and reward: it curates the supervised corpus, then drives reinforcement learning on visual-coding tasks. Leveraging PrismaForge for data synthesis and filtering, we build PrismaCoder-2M, the most diverse open dataset for multimodal code intelligence and the largest to date. On the model side, we train PrismaCoder-9B and PrismaCoder-35B on this data and release both. They lead the open state of the art by a wide margin and rival leading proprietary systems. Our analyses further show that the proposed rubric-based pipeline improves multimodal coding performance across model backbones. We release our code and data at https://qiushisun.github.io/PrismaCoder-Home/.
0
cs.SEcs.AI Yuyao Ge, Shenghua Liu, Peizhong Gao et al. · Oct 14, 2026

Doc2Harness evaluates whether frontier LLMs can engineer a coding-agent harness from scratch, a capability that existing SWE benchmarks ignore by holding the harness fixed. The benchmark asks a build model to generate a complete harness from a development document and an interface-only skeleton, then evaluates it deterministically with a scripted mock model across $328$ black-box test cases. The results reveal a $26$-point performance gap between the best and worst models, with even the strongest scoring only $53.05\%$, suggesting substantial room for improvement in long-horizon infrastructure construction.

Agents driven by large language models are increasingly deployed on long-horizon tasks, where they use tools and modify real workspaces. How well they perform depends as much on the harness around the model as on the model itself. Existing benchmarks measure downstream task success under a fixed harness, leaving harness engineering itself unexplored. We propose Doc2Harness, a two-stage benchmark that evaluates long-horizon harness engineering directly. In Stage 1, a build model operating inside a fixed builder harness receives an interface-only contract skeleton and a development document that consolidates behavior across twelve frontier harnesses, and then constructs a complete candidate harness in an isolated container. In Stage 2, the frozen candidate harness runs in containers separate from the construction environment, one per test case, and is driven end to end by a scripted mock model. We score each test case using four observable channels, namely the requests sent to the model, the files on disk, the process exit code, and the command output; positive controls rule out vacuous passes. Across nineteen frontier models, each evaluated with three independent builds on 328 test cases, GPT-6 Astra achieves the highest pass rate at 53.05%, while the weakest model reaches 27.44%, a gap of roughly twenty-six percentage points. Even the strongest model fails nearly half of the test cases, and failures cluster around how cross-cutting functionality is split across modules. To our knowledge, Doc2Harness provides the first deterministic benchmark for measuring long-horizon harness engineering.
0
cs.CRcs.AIcs.SE Mohsen Iranmanesh, Sina Moradi Sabet, Sina Marefat et al. · Oct 14, 2026

Automated vulnerability repair typically validates patches against the same static alerts or proof-of-concept inputs used to generate them, risking overfitting to partial evidence. This paper introduces P2Patch, a counterexample-guided adversarial repair protocol in which an exploitation agent repeatedly tries to bypass the current patch, with each confirmed bypass becoming a permanent repair requirement. The core idea is to treat the patched program itself as a new attack target and to evaluate final patches against held-out security oracles strictly separated from construction-time evidence.

Large language models are increasingly deployed as autonomous agents for automated program repair, patching software vulnerabilities through multi-step reasoning and tool use. Yet these systems typically validate a patch against the same evidence used to construct it -- a static alert, sanitizer trace, published exploit, or test suite. A patch that blocks that one piece of evidence can therefore look successful while remaining vulnerable to the same vulnerability with some variation. We present P2Patch, a generative adversarial repair system that treats each patch as a new attack target. Starting from a normalized vulnerability finding, an exploitation agent constructs a reproducing proof of vulnerability (PoV), a patching agent repairs the program, and the exploitation agent then attacks the patched program for a distinct same-vulnerability exploit. Every successful exploit becomes a permanent repair requirement, and the final patch must block all PoVs accumulated during the patching process, with construction-time PoVs kept strictly separate from held-out evaluation oracles. Across 101 C/C++ and Java CVE subjects, this adversarial loop surfaces a distinct confirmed exploit in 41% of runs after the patch has already blocked its original construction-time PoV. Against single-pass repair from the same finding using Claude Code, P2Patch raises held-out fix-closed coverage from 78.1% to 84.7% and beyond-upstream coverage from 42.1% to 62.5%. Under the same held-out oracles, it also certifies more attack paths as blocked than recent state-of-the-art agentic repair systems on overlapping subjects. These results show that adversarial testing and independent security oracles expose repair gaps that one-shot validation misses.
0
cs.SEcs.AI Jiahao Zhang, Yifan Zhang, Yu Huang · Oct 14, 2026

Coding agents consume substantial tokens as they repeatedly decide where to look, what to try, and when to stop during automated repair. This paper asks which of these decisions can be offloaded to a cheap probabilistic judge that answers fixed questions without generating explanations. The authors introduce JevCoder, a workflow built around the proprietary Jev judge to recommend initial code snippets, guide action types during repair, and trigger submission. On 400 SWE-bench tasks across three repair models, the system cuts repair-model token use by $21.6\%$–$50.6\%$ while raising observed repair rates.

A coding agent repeatedly makes decisions as it repairs code. These decisions shape repair trajectories and affect the token cost of successive model requests. We ask which repair decisions can be delegated to a low-cost probabilistic judge to reduce token use while maintaining repair quality. The judges answer questions with probabilities over predefined answers, without generating explanations. We evaluate judgment quality across repair stages and test how individual interventions change subsequent repair work. We compare these interventions with unguided repair, which uses no judge, and with the same workflow using the repair model itself as the judge. The benefit depends on the work an intervention changes, rather than the cost of the judgment alone. Based on these studies, we propose JevCoder, a workflow built around Jev, a low-cost probabilistic judge. It combines code-snippet recommendations with action-type guidance and uses judgments to determine when to submit. We evaluate three repair models, each on the same 400 tasks: 200 from SWE-bench Verified and 200 from SWE-Bench Pro Verified. Compared to unguided repair, JevCoder reduces mean repair-model token use by 21.6%-50.6%, with higher observed repair rates across all three models.
0
cs.LGcs.SE Tianshuo Qiao, Naiqian Zheng, Xiaopeng Liu et al. · Oct 1, 2026

CI pipelines for LLM training frameworks are drowning in GPU-heavy end-to-end tests that can take hours per run. FastCI attacks this bottleneck by replacing coarse file-level mappings with a runtime evidence graph built from lightweight stack sampling, then pruning redundant tests via caller/callee context, scheduling risky tests first, and shrinking workloads along dimensions outside each test's validation scope. Deployed at ByteDance, it claims a 77.5% latency reduction and 63.9% GPU savings, though the evaluation rests on an internal codebase with no open-source artifacts.

As large language models (LLMs) keep growing in size and complexity, their training frameworks evolve at a rapid pace as well. Therefore, continuous integration (CI) is critical for maintaining the quality and stability of these frameworks. However, unlike traditional software, CI for LLM training frameworks relies on GPU-intensive tests, which usually involve complete model training or evaluation. This leads CI itself to become a new bottleneck for fast-paced development. In this paper, we introduce FastCI, a framework that improves the efficiency of CI for LLM training frameworks. FastCI leverages runtime evidence to select affected tests and prune tests that execute changed code in equivalent contexts. Then FastCI prioritizes high-risk tests to expose potential failures earlier, and optimizes test workloads along dimensions outside the intended validation scope of each test. Evaluated on the CI workload of our LLM training framework, FastCI reduces the CI latency by 77.5% and the GPU resource usage by 63.9%, while improving the modified code coverage retention by 3.2%, compared with the currently deployed CI pipelines. FastCI has now been integrated into the CI pipelines of our LLM training framework at ByteDance.
0
cs.SEcs.AIcs.CL Junyu Guo, Shangding Gu, Ming Jin et al. · Oct 1, 2026

The paper asks when a nominally weaker LLM can reliably audit patches produced by a stronger coding agent. Its central claim is that groundability—the property that evidence exposes an independently checkable claim about missing behavior—matters more than reviewer scale. On a benchmark of 411 real execution-labeled traces and 101 controlled cases, the authors show that weak reviewers given official execution evidence can achieve near-perfect catch and near-zero over-rejection, while a deployable cascade of static checks and generated tests recovers only part of that upper bound. The finding that parameter count is not a monotonic predictor of review quality reframes the oversight problem from building bigger judges to building better checks.

Coding agents can return plausible patches that omit required behavior. These failures are hard to review because long traces and confident summaries often hide what was missed. We ask when a nominally weaker reviewer can reliably decide whether a patch solves its issue. We study 411 execution-labeled traces from three agents and 101 controlled cases. On 154 GPT-5.4 traces, structured but unchecked evidence raises both defect catch and over-rejection. We then provide official execution evidence as an upper-bound diagnostic. After choosing and freezing one of two formats per reviewer, five of six reviewers improve both rates on 122 held-out traces; two classify every trace correctly. Reviewer size is not a consistent predictor of quality. Because official tests are unavailable in deployment, we also evaluate a frozen cascade with patch-caused static errors and generated tests that first fail on the unpatched repository. On 121 scored held-out GPT-5.4 traces and 59 Gemini traces, its coverage is 0.89 and 0.86, risk is 0.33 and 0.26, catch is 0.76 and 0.80, and over-rejection is 0.66 and 0.67. Most false rejections occur when unresolved cases reach the reviewer. Official execution evidence shows the potential of weak review when decisive checks are available. Producing equally reliable checks without official tests remains the main bottleneck.
0
cs.AIcs.SE Yixuan Li, Yiyun Zhou, Yao Long Teng et al. · Oct 1, 2026

Choosing an agent system means picking both a model and the execution harness around it, but most evaluations fix one and vary the other. This paper runs a full cross-product of four configurable harnesses (OpenHands, DeepSeek Harness, PI, openJiuwen) and five models across three terminal-use benchmarks (TUA-Bench, ALE-CLI, Terminal-Bench 4), plus two native vendor pairings, for 66 configurations total. The core finding is that model rankings reverse depending on the harness, best harnesses change across tasks for four of five models, and cost does not reliably predict score, suggesting that model-harness fit should be evaluated as a unit.

Choosing an agent system means choosing both a language model and the harness through which it acts. We ask whether a strong model, harness, or pairing stays strong when the setting changes. We evaluate 66 configurations: four configurable harnesses (OpenHands, DeepSeek Harness, PI, and openJiuwen) paired with five models on TUA-Bench, ALE-CLI, and Terminal-Bench 4, plus the native Codex-GPT and Claude Code-Claude pairings. Model rankings reverse across harnesses. On Terminal-Bench 4, Claude leads GPT by 7.94 points in OpenHands but trails it by 30.16 points in PI. For four of the five models, the best harness changes from one benchmark to another, yet some pairings hold: openJiuwen gives Kimi its highest score on all three benchmarks, by 5.61 to 11.11 points. A model's own vendor harness is not reliably its best, and higher cost does not reliably buy a higher score. On Terminal-Bench 4, GPT scores higher under PI than under DSH at less than a quarter of the cost per task. Matched trajectories suggest why fit varies. Models start almost all repairs themselves, so much depends on whether the harness hands failures back in a form the model can use. GPT does best with PI's lean scaffold, while Kimi, which often issues malformed tool calls, does best in openJiuwen. We argue that the model, the harness, and the task should be evaluated together, and we release the harness adapters, evaluation code, and all 6,204 scored trajectories at https://github.com/liyix/finding-the-right-fit and https://huggingface.co/datasets/yixuanli97/finding-the-right-fit.
0
cs.AIcs.CLcs.LG Sungho Park, Wonjoong Kim, Jue Zhang et al. · Oct 1, 2026

ActiveSaddler addresses the overlooked problem of which training scenarios to use during automated LLM-agent harness optimization. It treats curriculum selection as a non-stationary bandit whose arms are dynamically instantiated failure patterns, allowing the scenario distribution to co-evolve with the harness rather than being fixed upfront. On GAIA2 and Terminal-Bench 2.0, this yields test Pass@1 gains of 4.4 and 7.5 percentage points over the same optimizer with a fixed scenario order, arguing that adaptive curricula are a critical new dimension for harness optimization.

Automated harness optimization can substantially improve LLM agents by iteratively updating their prompts, tool interfaces, and control logic from execution feedback. However, existing methods primarily optimize how the harness is updated while largely fixing which training scenarios generate the feedback that drives those updates. As the harness evolves, the scenarios most useful for further optimization can change, suggesting that the training curriculum itself should adapt alongside the harness. We formulate this missing dimension of harness optimization as an automated curriculum learning problem and introduce ActiveSaddler. ActiveSaddler models the evolving curriculum as a non-stationary bandit with dynamically instantiated optimization targets. It abstracts recurring failures into reusable failure-pattern arms, estimates the potential learning progress from further targeting each pattern, and adaptively balances revisiting known weaknesses with exploring unseen scenarios for new ones. Optimization outcomes continually update both the set of discovered failure patterns and their priorities, allowing the curriculum to co-evolve with the harness. Experiments on GAIA2 and Terminal-Bench 2.0 show that ActiveSaddler consistently discovers stronger harnesses, improving test Pass@1 by 4.4 and 7.5 percentage points over the same harness optimizer using a scenario order fixed before optimization, respectively. Ablations further show that these gains depend on dynamically constructing optimization targets, estimating their evolving utility, and balancing continued optimization with new failure discovery. Together, these results establish automated curriculum learning as a new crucial optimization dimension for harness optimization.
0
cs.SEcs.AI Asad Ur Rehman, Syed Mohammad Kashif, Ruiyin Li et al. · Oct 1, 2026

The paper mines 22,848 closed GitHub issues from 21 open-source LLM-based multi-agent systems, filtering down to 944 MAS-related reports to catalog what goes wrong in practice. Through qualitative coding, the authors map issues, causes, and solutions, finding that orchestration and workflow design dominate practitioner pain points. It matters because it replaces anecdotal MAS debugging lore with an empirical taxonomy grounded in actual maintenance traces.

With the advancement of LLM-based multi-agent systems (MAS), an increasing number of opensource projects are adopting multi-agent architectures as the foundation of their core functionality. Although research and practice on MAS have attracted considerable attention, limited studies have explored the challenges faced by practitioners of open-source LLM-based MAS, the causes of these challenges, and potential solutions. To address this gap,we conducted an empirical study to understand the issues that practitioners encounter when developing and using open-source LLM-based MAS, the possible causes of these issues, and potential solutions. We collected 22,848 closed issues from 21 open-source LLM-basedMASand applied a mixed automated and manual filtering approach to reduce the dataset to 944 issues related to LLM-based MAS.We then analyzed these issues to understand the frequent issues encountered by practitioners, their underlying causes, and potential solutions. Our study results show that (1) Orchestration & Execution Issue is the most common issue faced by practitioners, (2) Workflow Problem, Tool Integration Problem, and Memory Problem are identified as the most frequent causes of the issues, and (3) Optimize Workflow is the predominant solution to the issues. Based on the study results, we derive empirically grounded implications for practitioners and researchers aimed at improving orchestration, tool integration, and memory mechanisms in LLM-based MAS.