<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>IceShore Radar</title>
  <link href="https://iceshore.ai/en/radar/"/>
  <link rel="self" href="https://iceshore.ai/en/radar/feed.xml"/>
  <id>https://iceshore.ai/en/radar/</id>
  <updated>2026-11-07T00:00:00Z</updated>
  <author><name>IceShore Radar Editorial Team</name></author>
  <entry>
    <title>58% of GitHub Copilot's pull requests got no human input along the way, study says</title>
    <link href="https://iceshore.ai/en/radar/rn-1046/"/>
    <id>https://iceshore.ai/en/radar/rn-1046/</id>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary>Researchers studied 7,581 pull requests written by GitHub Copilot's coding agent with public session logs. In 58%, no developer stepped in while the agent worked; when developers did, the exchange was brief, a median of two rounds. After the first intervention, the agent's work trail dropped significantly, by 20.8 iterations.</summary>
  </entry>
  <entry>
    <title>Six-week log of 118 AI agent failures finds stale docs the top cause, at 48</title>
    <link href="https://iceshore.ai/en/radar/rn-1048/"/>
    <id>https://iceshore.ai/en/radar/rn-1048/</id>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary>A single-author case study tracked the author's own markdown repository edited daily by three AI agent tools under one rule set. Of 118 recorded failures, stale documentation was the largest class, at 48. An AI-run audit found about half of known stale statements, with at least 93% of its findings correct, and the author urges retesting old rules.</summary>
  </entry>
  <entry>
    <title>Multi-agent AI that ports whole codebases passed 18% more tests than prior method</title>
    <link href="https://iceshore.ai/en/radar/rn-1052/"/>
    <id>https://iceshore.ai/en/radar/rn-1052/</id>
    <updated>2026-11-07T00:00:00Z</updated>
    <summary>CodeMeepo, from an arXiv preprint, splits a whole-repository language migration among eight specialized AI roles and checks each milestone against a fixed test oracle the agents cannot edit. Across nine projects and three language pairs it passed 18% more tests than a leading multi-agent baseline using the same model.</summary>
  </entry>
  <entry>
    <title>Blitzy announces a collaboration with Microsoft to modernize legacy software</title>
    <link href="https://iceshore.ai/en/radar/rn-0010/"/>
    <id>https://iceshore.ai/en/radar/rn-0010/</id>
    <updated>2026-11-06T00:00:00Z</updated>
    <summary>Blitzy, which builds an AI platform for large company codebases, announced a collaboration with Microsoft. Blitzy says its platform maps older, poorly documented systems, then hands the work to many AI agents that build from a specification a person has approved. It will also bring Microsoft's GitHub Copilot and Azure services into its platform.</summary>
  </entry>
  <entry>
    <title>Trimming coding agents' history saved money in zero of 42 tests under cache-based pricing</title>
    <link href="https://iceshore.ai/en/radar/rn-1056/"/>
    <id>https://iceshore.ai/en/radar/rn-1056/</id>
    <updated>2026-11-06T00:00:00Z</updated>
    <summary>Researchers ran 9,400 experiments with two coding agents to test 42 ways of deleting old conversation history to save money. Under flat per-token pricing, estimated costs fell in 26 of the 42 setups. Under pricing that discounts cached input, none lowered costs, because trimming breaks the cached prefix and agents often re-fetched what was deleted.</summary>
  </entry>
  <entry>
    <title>AI-written unit tests: 15.6% of failures came from wrong expected results</title>
    <link href="https://iceshore.ai/en/radar/rn-1047/"/>
    <id>https://iceshore.ai/en/radar/rn-1047/</id>
    <updated>2026-11-06T00:00:00Z</updated>
    <summary>An arXiv preprint analyzed 14,320 Java unit tests written by four AI models under four prompting styles. Incorrect assertions caused 15.6% of test failures, and the tests rarely checked null, negative or empty inputs, showing a bias toward the happy path. The gaps appeared even in simple functions.</summary>
  </entry>
  <entry>
    <title>Google research design cuts first mitigation in simulated outages to 1.8 seconds</title>
    <link href="https://iceshore.ai/en/radar/rn-0006/"/>
    <id>https://iceshore.ai/en/radar/rn-0006/</id>
    <updated>2026-11-05T00:00:00Z</updated>
    <summary>Google published a research reference design for AI agents that respond to production outages on their own. In simulated Black Friday sale outages, the time until the first mitigation fell from 15–45 minutes to 1.8 seconds. Permanent changes to how the agents are organized still require sign-off from site reliability engineers.</summary>
  </entry>
  <entry>
    <title>GitHub now lets Copilot approvals count toward required pull request reviews</title>
    <link href="https://iceshore.ai/en/radar/rn-0007/"/>
    <id>https://iceshore.ai/en/radar/rn-0007/</id>
    <updated>2026-11-05T00:00:00Z</updated>
    <summary>GitHub made Copilot approvals generally available for its AI code review. When admins turn the feature on, an approval from Copilot counts toward a repository's required approvals. Adding commits after Copilot signs off cancels its approval, so a fresh review is needed.</summary>
  </entry>
  <entry>
    <title>Inkitt has AI agents carry small code fixes all the way to a draft pull request</title>
    <link href="https://iceshore.ai/en/radar/rn-0008/"/>
    <id>https://iceshore.ai/en/radar/rn-0008/</id>
    <updated>2026-11-05T00:00:00Z</updated>
    <summary>In a post on its engineering blog, Inkitt described a system in which AI agents take small, low-risk code changes from the initial request to a draft pull request. Steps such as checking the work and repairing failed automated test runs get at most two attempts each. A person still has to mark the pull request ready for review and approve it.</summary>
  </entry>
  <entry>
    <title>Catching coding agents' invalid commands before they run cut task time by 15.8%</title>
    <link href="https://iceshore.ai/en/radar/rn-1049/"/>
    <id>https://iceshore.ai/en/radar/rn-1049/</id>
    <updated>2026-11-04T00:00:00Z</updated>
    <summary>A preprint describes StateMirror, which checks an agent's planned commands against the live repository before they run, catching references to missing files or packages. In 4,398 logged sessions such errors cost a median of three extra steps. On 79 live tasks it cut execution time 15.8% and token use 11.8% without lowering the solve rate.</summary>
  </entry>
  <entry>
    <title>AI coding agents back up files before risky changes only 15.2% of the time</title>
    <link href="https://iceshore.ai/en/radar/rn-1040/"/>
    <id>https://iceshore.ai/en/radar/rn-1040/</id>
    <updated>2026-11-04T00:00:00Z</updated>
    <summary>Researchers built 205 tasks from cases where users said they regretted not saving something an agent later changed. Six frontier models finished 86.1% of tasks on average but backed up the affected files, environments or settings beforehand only 15.2% of the time. An add-on backup layer the team built covered every such action.</summary>
  </entry>
  <entry>
    <title>AI agent instruction files now appear in 59.6% of the most-starred GitHub projects</title>
    <link href="https://iceshore.ai/en/radar/rn-1043/"/>
    <id>https://iceshore.ai/en/radar/rn-1043/</id>
    <updated>2026-11-04T00:00:00Z</updated>
    <summary>A preprint study of 22,854 widely used, active GitHub projects found instruction files for coding agents, AGENTS.md or CLAUDE.md, in 26.3% of them and in 59.6% of the most-starred. Of 341,852 statements analyzed, 74.0% of directives gave no reason, and projects split on whether to disclose AI use.</summary>
  </entry>
  <entry>
    <title>New AI method ports whole C projects to Rust at 66.1% lower cost than prior work</title>
    <link href="https://iceshore.ai/en/radar/rn-1053/"/>
    <id>https://iceshore.ai/en/radar/rn-1053/</id>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary>SpeC2Rust, described in an arXiv preprint, has an AI model write specifications for each module of a C codebase, then translate and repair the code against them. All eight test projects compiled in Rust and passed their original end-to-end tests with no unsafe code. Against an earlier AI-based approach, cost fell 66.1% and input tokens 84.7%.</summary>
  </entry>
  <entry>
    <title>Preprint catalogs 13,919 mistakes AI models make when translating code between languages</title>
    <link href="https://iceshore.ai/en/radar/rn-1042/"/>
    <id>https://iceshore.ai/en/radar/rn-1042/</id>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary>Researchers had seven AI models translate code across six language pairs on three benchmarks and hand-labeled 13,919 cases where the output strayed from the original. They sort the errors into three types, including semantic conflicts and lost project context, and propose a fix that retrieves similar past translations.</summary>
  </entry>
  <entry>
    <title>Linus Torvalds says Linux wants competent developers to use AI as a tool</title>
    <link href="https://iceshore.ai/en/radar/rn-1059/"/>
    <id>https://iceshore.ai/en/radar/rn-1059/</id>
    <updated>2026-11-03T00:00:00Z</updated>
    <summary>Linus Torvalds, creator of the Linux kernel, told a Register columnist that arguments against using AI for commit messages are misguided, and that Linux wants capable developers to use AI as a tool. He said submitters who send AI-made patches they don't understand should be discouraged. The Register published the remarks on Oct. 23.</summary>
  </entry>
  <entry>
    <title>When requirements shift, coding AIs recover from just 15.4% of failures in two tries</title>
    <link href="https://iceshore.ai/en/radar/rn-1057/"/>
    <id>https://iceshore.ai/en/radar/rn-1057/</id>
    <updated>2026-11-02T00:00:00Z</updated>
    <summary>A preprint introducing the FeatureLoop benchmark tested 12 frontier models on 61 human-reviewed tasks from 34 repositories, with requirements changing mid-project. The best model finished 72.1% of tasks, but only 15.4% of failed stages recovered within two rounds of corrective feedback. The authors also saw incomplete repairs and regressions.</summary>
  </entry>
  <entry>
    <title>Coding agents fully delivered at most 14% of enterprise product specs in a new test</title>
    <link href="https://iceshore.ai/en/radar/rn-1035/"/>
    <id>https://iceshore.ai/en/radar/rn-1035/</id>
    <updated>2026-11-02T00:00:00Z</updated>
    <summary>A benchmark of 43 tasks in mature enterprise codebases, checked against 750 expert-audited points, measures whether coding agents fulfill full product requirement documents. Across 11 model and tool setups, the best complete-delivery rate was 14.0%, by OpenAI's GPT-5.6 Sol; missing integration was a main cause.</summary>
  </entry>
  <entry>
    <title>GitHub's Copilot can now fix bugs reported in Microsoft Teams and propose the change</title>
    <link href="https://iceshore.ai/en/radar/rn-1045/"/>
    <id>https://iceshore.ai/en/radar/rn-1045/</id>
    <updated>2026-11-02T00:00:00Z</updated>
    <summary>GitHub said on Oct. 23 that its app for Microsoft Teams now brings in Copilot, its AI coding assistant. When a bug report lands in a Teams chat, users can mention GitHub to have Copilot investigate, fix the bug and open a pull request for the team to review. The old GitHub app for Teams will be retired on Nov. 16.</summary>
  </entry>
  <entry>
    <title>Forrester predicts a bug in AI-written code will cause a global outage in 2027</title>
    <link href="https://iceshore.ai/en/radar/rn-1044/"/>
    <id>https://iceshore.ai/en/radar/rn-1044/</id>
    <updated>2026-11-01T00:00:00Z</updated>
    <summary>Research firm Forrester released its 2027 technology and security predictions on Oct. 21. It expects AI-assisted coding and patching to outpace teams' capacity to test, and forecasts that a bug or regression in AI-generated code will trigger an outage spanning several industries worldwide.</summary>
  </entry>
  <entry>
    <title>Checks for AI-driven COBOL-to-Java migration catch 61 defects but miss rounding errors</title>
    <link href="https://iceshore.ai/en/radar/rn-1039/"/>
    <id>https://iceshore.ai/en/radar/rn-1039/</id>
    <updated>2026-11-01T00:00:00Z</updated>
    <summary>Aimed at agent-driven migrations, a preprint generated 849 end-to-end test cases for a 33,429-line COBOL program to check its Java translation, finding and fixing 61 defects in the code generator. When the authors planted 450 defects, the check caught 47.6%, including every deleted write in executed code, but no rounding errors.</summary>
  </entry>
  <entry>
    <title>Martin Fowler backs letting AI debugging agents read the code last, not first</title>
    <link href="https://iceshore.ai/en/radar/rn-1038/"/>
    <id>https://iceshore.ai/en/radar/rn-1038/</id>
    <updated>2026-11-01T00:00:00Z</updated>
    <summary>On his site Oct. 21, software author Martin Fowler recommended an essay by Cindy Sridharan on debugging with AI agents. Her view, which he summarized approvingly, is that an agent should first gather evidence about how the system behaves and only then form hypotheses from the code. Fowler noted that a human is still needed to steer the agent.</summary>
  </entry>
  <entry>
    <title>OpenAI says its newest model now gets COBOL migrations right 86.6% of the time</title>
    <link href="https://iceshore.ai/en/radar/rn-1041/"/>
    <id>https://iceshore.ai/en/radar/rn-1041/</id>
    <updated>2026-10-31T00:00:00Z</updated>
    <summary>OpenAI says GPT-6.1 Sol correctly migrated COBOL programs to languages such as Java or Python without changing their behavior 86.6% of the time at a low reasoning setting, up from 5.4% for GPT-5.6 Sol, and 97.9% with more reasoning. The tests are OpenAI's own. BleepingComputer notes that real migrations would still need expert review and testing.</summary>
  </entry>
  <entry>
    <title>Grafana Labs proposes managing AI agents with service-level objectives and error budgets</title>
    <link href="https://iceshore.ai/en/radar/rn-1032/"/>
    <id>https://iceshore.ai/en/radar/rn-1032/</id>
    <updated>2026-10-31T00:00:00Z</updated>
    <summary>InfoQ reports Grafana Labs wants teams to measure AI agent behavior, such as hallucination and task fulfilment, and manage it with service-level objectives and error budgets. Its example target: 95% of conversations judged as fulfilled over 30 days, with the rest as the error budget.</summary>
  </entry>
  <entry>
    <title>HERE expects AWS Kiro agents to cut its task investigation phase by more than half</title>
    <link href="https://iceshore.ai/en/radar/rn-1033/"/>
    <id>https://iceshore.ai/en/radar/rn-1033/</id>
    <updated>2026-10-31T00:00:00Z</updated>
    <summary>On an AWS blog, map company HERE Technologies said it uses multiple Kiro agents to turn customer requirements into Jira tickets that keep the traceability automotive audits demand. Based on early internal measurements, it expects to cut the investigation phase for new tasks by more than 50%.</summary>
  </entry>
  <entry>
    <title>LY Corp. says AI design help cut planning on its 27-year-old shopping site to one month</title>
    <link href="https://iceshore.ai/en/radar/rn-1058/"/>
    <id>https://iceshore.ai/en/radar/rn-1058/</id>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>LY Corp. said on its tech blog that AI agents now draft requirements and designs for its Japanese shopping site, a service with over 3,000 repositories and 27 years of history. The team first organized domain knowledge and system diagrams for the AI, and senior engineers review each stage. Planning time fell from about two months to roughly one.</summary>
  </entry>
  <entry>
    <title>CyberAgent used generative AI to review about 200 live Lambda functions and refactor 38</title>
    <link href="https://iceshore.ai/en/radar/rn-0004/"/>
    <id>https://iceshore.ai/en/radar/rn-0004/</id>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>Japanese internet company CyberAgent said on its engineering blog that it used generative AI to catalog about 200 AWS Lambda functions, small cloud programs running in production and managed by multiple people. It refactored and redeployed 38 of them. Risky steps such as production deploys required explicit approval from a human engineer.</summary>
  </entry>
  <entry>
    <title>AWS has its DevOps Agent watch resilience tests and report root causes and impact</title>
    <link href="https://iceshore.ai/en/radar/rn-1027/"/>
    <id>https://iceshore.ai/en/radar/rn-1027/</id>
    <updated>2026-10-30T00:00:00Z</updated>
    <summary>Amazon Web Services said Oct. 15 that Resilience Hub, its service for checking how applications withstand failures, now starts a DevOps Agent investigation to watch each resilience test and report symptoms, root cause, impact and recovery actions.</summary>
  </entry>
  <entry>
    <title>Gartner expects half of organizations to use low-touch AI agents in IT operations by 2030</title>
    <link href="https://iceshore.ai/en/radar/rn-0001/"/>
    <id>https://iceshore.ai/en/radar/rn-0001/</id>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>Research firm Gartner said on Oct. 26 that by 2030, 50% of organizations will use AI agents that need minimal human involvement in IT operations, up from nearly 0% in 2026, Japan's ITmedia reported. In a Gartner survey, 58% of IT operations leaders said moving AI into production was an important priority.</summary>
  </entry>
  <entry>
    <title>GitHub says AI agents now kick off over 40% of pull requests, up from 17% in March</title>
    <link href="https://iceshore.ai/en/radar/rn-0002/"/>
    <id>https://iceshore.ai/en/radar/rn-0002/</id>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>GitHub's annual Octoverse report says that as of September, more than 40% of pull requests, the proposed code changes submitted for review, began with a developer directing an AI agent, up from 17% in March. The report describes code review as the way developers shape what the agents return.</summary>
  </entry>
  <entry>
    <title>AWS demonstrates DevOps Agent tracing a failure caused by another team's Terraform change</title>
    <link href="https://iceshore.ai/en/radar/rn-0003/"/>
    <id>https://iceshore.ai/en/radar/rn-0003/</id>
    <updated>2026-10-29T00:00:00Z</updated>
    <summary>Amazon Web Services published a walkthrough of AWS DevOps Agent, its AI operations tool, tracing a failure across separately managed Terraform stacks. In the example, an infrastructure team's tighter network rule cuts an app team's function off from its database, and the agent uses alarms, dependencies and change logs to point to the likely cause.</summary>
  </entry>
</feed>
