Operations | Monitoring | ITSM | DevOps | Cloud

Recent findings from Anthropic’s Project Glasswing offer a useful indication of where vulnerability discovery may be heading. Anthropic reported that it and its partners had used Claude Mythos Preview to identify more than 10,000 high- or critical-severity vulnerabilities across the software they reviewed. More significantly, Anthropic reported that the bottleneck had shifted from finding vulnerabilities to having the capacity to verify, disclose, and patch them.

At some point this year, you likely approved a request to expand AI coding tool access across the team. The pitch was straightforward: engineers write code faster, the team ships more, the investment pays for itself. The first half happened. Engineers are writing code faster. If you're now being asked whether the investment paid off, and you're finding the honest answer is more complicated than a yes, you are not alone, and you have not been sold something broken.

15 AWS cost optimization tactics across compute, storage, networking, and monitoring plus a quick-reference table by effort and savings potential.

Large language models are effective at security review for the same reason they are effective at many other tasks: they reason rather than pattern match. In plain terms, a traditional scanner checks code against a list of known bad patterns, the way a spell checker flags a misspelled word, regardless of what the sentence means. An LLM can instead follow the program's logic: trace a piece of attacker-controlled input through several layers of application code to determine whether it is reachable.

The hard part of a feature flag is rarely adding it. It is remembering to remove it months later, when the rollout is over, the original context has faded, and there is always a more urgent piece of work waiting. Since April 2026, one Atlassian team has used Agentic Pipelines to clean up their monthly backlog of stale feature flags. The workflow prepares the change and opens a pull request, while engineers still review and merge the pull request.

Improving agent experience (AX) is one thing. Keeping it good as your product changes is harder. A renamed field, different error response, or overlapping tool can turn a workflow that worked yesterday into extra retries, wasted tokens, or human intervention. CI gives teams a way to catch AX regressions as part of the development process. You can test the interfaces agents depend on, run representative agent workflows against product changes, and preserve fixed failures as regression cases.