Papers for

devops engineers

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.

Context segmentation improves task solving in local cybersecurity AI

Evaluating Context Segmentation in Locally Deployable SLMs for Cybersecurity CTF Tasks

Abstract: The proliferation of highly capable open-weight Small Language Models (SLMs) democratizes access to advanced cybersecurity capabilities, posing a escalating risk as these models can bypass proprietary API guardrails when deployed locally. However, SLMs deployed as autonomous agents often struggle with long-horizon, exploratory tasks like cybersecurity Capture The Flag (CTF) challenges due to context bloat and cognitive degradation from accumulated tool-call outputs. To understand and mitigate this cybersecurity threat, we introduce \textit{context segmentation}, a two-level agentic framework that divides complex exploitation tasks into manageable, contextually isolated sub-problems. Evaluating on the \texttt{picoCTF} dataset using memory-constrained \texttt{gemma-4} models, we demonstrate that for the E4B model, our strategy acts as an intelligent search, achieving competitive rewards with superior token efficiency compared to brute-force retries, and successfully solving 18.52\% of tasks that standard agentic execution fails to complete. Code is available at https://github.com/9xeb/context-segmentation.

Fri 11 SeptCryptography and SecurityArtificial Intelligence
The gist
Small language models (SLMs) can help with cybersecurity problems but often get overwhelmed when working on complex tasks because they mix too much information at once. The authors created a method called context segmentation that breaks big problems into smaller, separate parts so the AI can focus better. They tested this on a cybersecurity challenge set and found their method solved more tasks and used computing resources more efficiently than usual approaches. This helps demonstrate how local AI tools can be made smarter for security tasks without needing cloud-based software.
Open 2609.12839v1

Optimizing repository skill documents improves coding agent performance modestly

Skill Issue: Lessons from Optimizing Repository SKILLs for Coding Agents

Abstract: Coding agents increasingly read repository knowledge from SKILLs --- plain \texttt{.md} files versioned alongside the code. Recent work synthesizes these files automatically, by optimizing the document against a benchmark. A bare repository comes with no benchmark, and the synthetic tasks prior work builds are small enough that a capable agent saturates them with no document at all. We mine harder tasks --- merged pull requests of the repository, reverted at a single frozen base commit; and score a candidate document by whether the same agent does better with it than without it. On three Kotlin repositories, the documents GEPA finds raise this score by $4.9$pp on average, and the ones SkillOpt finds leave it where it started, $0.1$pp above the seed. The GEPA gain matches what prior work reports with the same optimizer, and at the dataset size a single repository supplies it cannot be separated from the agent's run-to-run variance; settling that would take more tasks than one repository's history yields. The documents themselves read better than the score: a maintainer of one repository found in them knowledge one only gets by working in the project.

Fri 11 SeptArtificial Intelligence
The gist
Coding agents use special text files called SKILLs that explain a repository’s code to help them solve coding tasks. The authors studied how well automatically improved SKILL files help agents handle harder coding challenges taken from real project histories. They found one method, GEPA, can slightly improve agent success, but the improvement is small and may overlap with normal variation. Still, the improved SKILL files contained useful insights that a real project maintainer recognized.
Open 2609.12742v1

Hybrid graph learning improves splitting of monolithic software into microservices

TripleBound: Triplet-Guided Heterogeneous Graph Learning for Microservice Decomposition

Abstract: Cloud computing and DevOps have made microservices a common architecture for scalable, maintainable software systems. However, migrating monoliths to microservices remains challenging due to tight coupling and unclear service boundaries. Existing decomposition approaches typically rely on either structural dependencies or semantic similarity signals, but rarely integrate both within a unified representation learning objective. This paper proposes TripleBound, a hybrid framework for automated monolith-to-microservices decomposition that augments a heterogeneous graph neural network with weakly supervised triplet constraints derived from parser-inferred service groups based on package structure, naming conventions, and code location. TripleBound injects triplet-based constraints directly into the shared structural latent space, enabling both signals to be jointly optimized during representation learning. Structural dependencies are captured using CHGNN, which models the monolith as a heterogeneous graph with program nodes, resource nodes, CALL edges, and CRUD edges. Semantic relationships are incorporated through triplet constraints generated from parser-inferred service groups. Evaluation on AcmeAir, DayTrader, PlantsByWebSphere, and JPetStore shows that TripleBound achieves the highest composite decomposition score under the selected weighting on AcmeAir, DayTrader, and JPetStore compared to CHGNN and MonoEmbed, while CHGNN remains stronger on PlantsByWebSphere. Per-metric analysis reveals trade-offs: gains in structural modularity and inter-partition coupling are accompanied by higher entity distribution imbalance on some datasets. Alternative composite weightings preserve TripleBound's first-place ranking on AcmeAir and DayTrader but not on JPetStore, showing that the aggregate ranking is metric-dependent.

Thu 10 SeptSoftware Engineering
The gist
Breaking a big software program into smaller microservices is hard because the parts are often tightly connected or unclear. The authors developed a method called TripleBound that uses a combination of software structure and naming rules to better identify these parts by representing them as a graph with multiple types of connections. TripleBound uses special constraints during learning to combine these signals in one model. Tests on several example software programs show TripleBound often outperforms other methods, though results vary depending on how success is measured.
Open 2609.11212v1

Sandboxed live programming helps users safely edit shell scripts

ShellVis: Sandboxed Live Programming for Shell Scripts

Abstract: Live programming provides visibility to programmers by running and tracing programs as they are edited. However, for programs with potentially harmful side effects, liveness can turn mistakes into disasters. We propose enabling live programming in environments with side effects via sandboxing: confining effects to a simulation of the true environment. We apply sandboxed live programming in the challenging context of shell scripting: a ubiquitous and powerful---yet notoriously opaque and error-prone---tool. ShellVis provides line-by-line feedback on a shell script's run-time behavior, with file operations sandboxed via a safe overlay of the file system. A qualitative user evaluation finds ShellVis to be helpful to participants, replacing tedious existing practices and instilling confidence. Participant responses also reveal areas for future research, particularly bridging the gulf of execution alongside the gulf of evaluation. ShellVis serves as a case study of how sandboxing can bring live-programming techniques into the many real-world programming contexts where side effects are important.

Thu 10 SeptHuman-Computer InteractionProgramming Languages
The gist
Editing and testing shell scripts can be risky because mistakes might cause real damage to files or systems. The authors created ShellVis, a tool that lets users see what happens in their shell scripts as they write them, but in a safe fake environment that blocks harmful effects. This makes it easier and safer to write and debug shell scripts. Users found it helpful and replacing tedious manual checks, but the authors also identified ways to make the tool even easier to use in the future.
Open 2609.11000v1

Static code checks miss many exploitable vulnerabilities in Python code

Beyond Static Guarantees: Measuring the Static-Pass Dynamic-Fail Gap in Security-Sensitive and LLM-Generated Python Code

Abstract: Advances in large language models (LLMs) fuel the quest for scalable methods to assess the security of generated and security-sensitive software. Static analysis is widely adopted as a scalable, reproducible, and inexpensive security gate, but cannot directly observe runtime exploit behaviour. Vulnerabilities dependent on adversarial inputs, execution context, or exploit chaining may evade static checks while remaining exploitable in practice, yet passing static analysis is often treated as evidence of secure behaviour. This paper introduces the Static-Pass Dynamic-Fail (SPDF) phenomenon and a three-stage agentic pipeline combining static scanning, LLM-driven Common Weakness Enumeration (CWE) reasoning, and autonomous exploit verification in isolated Docker containers. We evaluate 1,355 Python samples from SecurityEval, RedCode, and CyberNative datasets. Of the 654 samples producing no findings under the composite Bandit-Semgrep gate, the LLM detection stage identified 394 candidate vulnerabilities across 235 files. Dynamic verification confirmed or partially confirmed exploitability in 95 files, yielding an inclusive pipeline rate of 14.53% (roughly 1 in 7 statically clean samples). This rate represents the proportion of Bandit-Semgrep-clean samples for which the pipeline identified a candidate vulnerability and obtained runtime evidence supporting exploitability. Outcomes varied by dataset: among candidate file--CWE pairs, confirmed exploitability was 33.7% for RedCode, 28.6% for CyberNative, and 5.4% for SecurityEval. Several frequently confirmed classes, including CWE-338 and CWE-916, were flagged by neither Bandit nor Semgrep. These findings indicate that static-analysis success and runtime security are hierarchical layers of software assurance rather than interchangeable measures, and have the potential to reshape how AI-generated and security-sensitive code is evaluated.

Wed 9 SeptCryptography and SecurityArtificial IntelligenceSoftware Engineering
The gist
Static code analyzers, tools that scan software before it runs, often miss vulnerabilities that only show up during execution. The authors studied Python code, including AI-generated samples, and found that many pieces of software passing static checks still had real security problems when tested in action. They created a system combining static scans, AI reasoning about common weaknesses, and live testing to find these hidden issues. Their results suggest that passing static analysis does not guarantee real-world security.
Open 2609.10762v1

Code generation guardrails struggle to block malware requests effectively

CS-Guard: Benchmarking LLM Guardrails for Code Generation Security

Abstract: Large language models (LLMs) have been ex- ploited to generate malware, but the effective- ness of guardrails for code generation secu- rity remains unclear. We introduce CS-Guard, the first benchmark to systematically evalu- ate guardrails for code generation security. It covers 1) text-to-code generation with 1000 high-quality malware-generation prompts, 7 jailbreak attacks, and a novel fictional scenario attack (FSA) that embeds malicious intent in a legitimate fictional software-development sce- nario; and 2) code-to-code generation with 331 code prompts spanning code infilling, code completion, and code translation. We empiri- cally evaluate 9 guardrails across seven LLMs. We find that current guardrails perform poorly against malicious code-generation re- quests: for text-to-code, the average attack success rate (ASR) after jailbreaks reaches about 50% for many guardrails; for code-to- code, average ASR approaches 100% on base LLMs and remains high across many guardrails (14.4% to nearly 100%). Our FSA also achieves ASR close to 100% across many guardrails, raising major reliability concerns for real-world software development. To sup- port future research, CS-Guard uses a modular three-layer guardrail taxonomy that lets devel- opers register guardrails for evaluation. We release the benchmark and data to enable fur- ther community evaluation.

Wed 9 SeptCryptography and SecurityArtificial Intelligence
The gist
Large language models can produce harmful computer code when asked, but it is unclear how well safety controls, called guardrails, prevent this. The authors created a new test called CS-Guard to measure how good these guardrails are at stopping malware code generation. They found that many guardrails often fail, letting dangerous code slip through half the time or more. They also showed some new clever ways to trick these controls, raising concerns for using these models safely in software development.
Open 2609.09798v1

Authority checks improve safety in multi-agent workspace updates

Beyond Agent Harnesses: Cross-Substrate Authority for Multi-Agent Systems

Abstract: Agentic systems persist model-visible memory while mutating workspaces, while a runtime, registry, or approval service may hold authority state outside both. Identical final files can then require opposite safe actions. We call this the cross-substrate authority gap: decision- relevant authorization information resides outside the planner-visible workspace or memory state. Across two controlled mini-benchmark families, three experiments compare planner-observation augmentation with an execution-time authority check using real Git lineage, durably recorded agent execution attempts, deterministic oracles, and two model routes. Experiment 1 is a 128-cell controlled evidence ablation: authority-blind candidate evidence obtains 0/32 final semantic success, while raw receipts and a typed relation both obtain 32/32. The missing authority fact accounts for the gain; typed packaging provides no observed planning-accuracy gain over equal raw information. Experiment 2 uses 96 planning calls: workspace-visible evidence yields 12/16 unsafe publication decisions, and planning with the typed relation remains unreliable (15/32 first actions correct; 11/32 invalid or absent). Experiment 3 replays the same 32 fixed model-generated first-action intents with zero additional model calls; a deterministic execution guard prevents all six unsafe intents from becoming effects and permits all 12 valid authorized publish intents. These results position authority enforcement at the mutation boundary as the operational endpoint of memory governance.

Tue 8 SeptMultiagent SystemsSoftware Engineering
The gist
When multiple computer programs (agents) work together, they often change shared files or data. The paper shows that important permission information is sometimes kept separate from what the agents can see, which can cause unsafe behaviors. The authors run experiments comparing methods that keep permission info visible to the agents versus checking permissions only right before changes happen. They find checking permissions at the last moment stops errors better, making the whole system safer.
Open 2609.08472v1

Capabilities limit coding agents to prevent unauthorized actions

Authority Is Not a String: A Capability-Scoped Harness for Prompt-Injection-Resistant Coding Agents

Abstract: Coding agents use system-level tools to read files, execute commands, and modify source code. Within the agent's sandbox, these tools often carry ambient authority: naming a resource is sufficient to act on it. Indirect prompt injection exploits this authority by placing instructions in repository files or tool output that cause the agent to perform actions the user did not request. We propose CapScope, a harness-level authorization mechanism that restricts tool use without requiring the model to identify malicious text. Before repository contents or tool output are read, CapScope derives a task-wide authority ceiling from trusted input. It then assigns each agent a separate set of typed capabilities, stored outside the model's context. Every tool call is checked against the capabilities of the agent that issued it. Permissions assigned to one sub-agent are therefore not automatically available to another. An injection may cause an agent to request an action, but the request is blocked unless that agent already has the required capability. We implement CapScope on the Pi coding agent and evaluate it in a repair workflow where an orchestrator delegates subtasks to separate sub-agents. The evaluation covers five Python tasks, five injection surfaces, four authorization conditions, and three trials per cell (300 runs). The injected effect executes in 33-47/75 runs under the ambient-authority and global-policy baselines, compared with 3/75 under CapScope. CapScope completes 68/75 repairs, while the baselines complete 68-72/75.

Tue 8 SeptSoftware Engineering
The gist
Coding agents often have broad access to files and commands, which can let hidden instructions trick them into doing unintended things. The authors created CapScope, a system that tightly controls what these agents can do by giving each specific permissions that can't be misused by others. Their tests show this method drastically reduces harmful actions from hidden instructions while still allowing agents to complete their main tasks effectively.
Open 2609.08371v1

Agent ATO visualizes AI coding agent actions from logs

Agent ATO: Visualizing Agent Interaction Timelines from Logs

Abstract: AI coding agents are becoming part of developers' workflows, but their behavior is difficult to understand from final code changes alone. During a task, agents interact with software repositories through sequences of actions such as searching for files, reading code, editing programs, and running tests or build commands. These interactions, together with token usage, are often recorded in console logs, but raw logs are difficult for developers to inspect. In this paper, we propose Agent ATO (Agentic Trajectory Observer), a tool for visualizing AI coding agent interaction timelines from console logs. Agent ATO extracts agent interactions, classifies them by command or tool type, and visualizes them as timelines. In addition to an all-interaction timeline, Agent ATO provides filtered timelines that emphasize file discovery, file reading, file editing, and execution while preserving surrounding context. We illustrate how Agent ATO may help developers inspect and compare agent actions using selected runs from two repair tasks. Future work will apply Agent ATO to more agents, tasks, and development environments, and will evaluate whether it reduces the effort needed to compare trajectories.

Tue 8 SeptSoftware Engineering
The gist
AI coding helpers do many actions during coding tasks, but just seeing their final code changes doesn't show what they did step by step. The authors created Agent ATO, a tool that reads the AI's activity logs and turns them into easy-to-understand timelines. These timelines show when the AI searched, read, edited, or ran code, helping developers see the AI’s thinking process. This makes it clearer how the AI works and how different runs compare.
Open 2609.08301v1

EnvPilot improves software setup by reusing past experience

EnvPilot: Systematic Design and Evaluation of an Experience-Augmented Agent for Software Environment Setup

Abstract: Environment Setup is a critical yet complex task in software engineering that relies heavily on expert knowledge. Existing automated environment setup methods lack the ability to accumulate experience from past execution trajectories and to evolve over time. As a result, their performance is limited because they often perform redundant exploration, ignore useful past solutions, and fail to generalize across diverse software ecosystems. We present the systematic design and empirical validation of EnvPilot, an experience-augmented agent that operationalizes trajectory-derived experience reuse for software environment setup. EnvPilot maintains an expandable Trajectory-Derived Memory (TDM), initialized with 667 high-quality experiences. It systematically transforms implicit knowledge from historical execution trajectories into structured experience and retrieves the most relevant guidance during task execution through the Context-aware Retrieval mechanism. This enables EnvPilot to combine multiple validated setup strategies, providing more precise and detailed guidance than methods that rely solely on static project files or web retrieval. To evaluate EnvPilot, we construct AES-Bench, a multilingual benchmark of 112 real-world GitHub instances across 9 programming languages. Experiments show that EnvPilot achieves a new state-of-the-art (SOTA) with a 75.00% Pass@1 success rate while reducing reasoning costs. Our empirical study shows that both the structured experience representation and the Context-aware Retrieval mechanism are essential.

Mon 7 SeptSoftware Engineering
The gist
Setting up software environments is often tricky and needs expert know-how. The authors created EnvPilot, a system that learns from past setup attempts to guide new ones more efficiently. It stores and retrieves useful setup experiences to avoid repeating mistakes and to work better across different programming languages. Tested on many real projects, EnvPilot was more successful and quicker than previous methods.
Open 2609.07357v1