30
55
55
55
55
60
45
The Evolution of the Agent Harness
Latent Space essay argues late-2025 agent gains came from models and harnesses maturing together, with harness logic absorbed into model weights.
The piece defines the agent harness as everything beyond model weights—tools, context, memory, guardrails—and charts its evolution from ReAct prompting (October 2022) through AutoGPT's premature autonomy, Cursor/Copilot's human-in-the-loop retreat, and Devin's roughly 15% success rate, to o1's capability overhang and Claude Code's February 2025 terminal agent with permission rules. It argues the Christmas 2025 jump cited by Transformer co-inventor Lukasz Kaiser reflected model and harness curves crossing, and that remaining harnesses will serve human attention rather than the model.
32
30
Evaluating Verified Autonomy in Quantum Engineering
Quantum-Harbor lab and QIQCBench (49 tasks) expose wide performance gaps across 17 frontier agentic systems in verified quantum engineering.
Researchers built Quantum-Harbor, a virtual laboratory providing a controlled execution environment where scientific AI agents interacting with quantum systems can have both actions and conclusions directly verified. QIQCBench contributes 49 expert-authored tasks spanning calibration and control, error correction and compilation, and sensing and networking. Across 17 frontier agentic systems, verified performance varied widely, exposing a substantial gap between demonstrated capability and reliable autonomous operation.
30
The Last AI Built by Humans: Toward Genuine Recursive Self-Improvement
Position paper defines recursive self-improvement for AI, introduces the Headroom-Closed Index and an autonomy roadmap toward genuine recursive meta-improvement.
The paper uses the Headroom-Closed Index to diagnose limitations of existing LLMs and frames recursive self-improvement (RSI) as a staged roadmap: improvement-execution, improvement-strategy, experience-acquisition, and environment-adaptation autonomy, culminating in recursive meta-improvement. It examines RSI across scientific discovery, embodied intelligence, and software engineering, highlighting differing requirements and development speeds. Drawing on industry practices and preliminary empirical evidence, it connects RSI research with practical systems and identifies key challenges to achieving genuine RSI.
25
The Last AI Built by Humans: Toward Genuine Recursive Self-Improvement
Position paper maps recursive self-improvement across autonomy levels from execution to meta-improvement, connecting RSI research to science, robotics, and software engineering.
The paper introduces the Headroom-Closed Index (HCI) to reveal limitations of existing LLMs for recursive self-improvement (RSI), then lays out a roadmap spanning improvement-execution, improvement-strategy, experience-acquisition, and environment-adaptation autonomy up to recursive meta-improvement. It examines RSI across scenarios such as scientific discovery, embodied intelligence, and software engineering, highlighting distinct requirements and development speeds. Drawing on industry practices and preliminary empirical evidence, it identifies key challenges to achieving genuine RSI.
46
30
GTIG AI Threat Tracker: From Prompting to Autonomy – The Evolution of Adversarial AI
GTIG's Q2 2026 tracker shows adversaries adopting agentic AI workflows, including credential harvesting in under six hours and supply chain attacks by UNC6780.
Google Threat Intelligence Group's Q2 2026 report documents adversaries moving from basic prompting to agentic AI workflows and automation, including a cloud compromise followed by agent-enabled mass credential harvesting executed in under six hours. It tracks financially motivated actor UNC6780 (TeamPCP) conducting large-scale open source supply chain compromises across PyPI, npm, and Docker Hub since March 2026, deploying credential stealers. The report also highlights growing targeting of proprietary AI models, source code, prompts, and API credentials, plus LLMJacking practices where adversaries steal developer credentials or hijack cloud infrastructure to run unauthorized AI workloads.
65
Why judgment is emerging as cybersecurity’s defining skill
CyberScoop op-ed argues CISOs should grant AI autonomy based on reversibility and blast radius rather than model confidence, and measure analyst overrides of AI recommendations.
A CyberScoop op-ed contends that as AI takes over analysis and recommendations in security operations, human judgment about context, reversibility and blast radius becomes the defining skill. The author argues autonomy decisions should rest on how reversible and impactful an action is rather than model confidence, citing examples such as patching vendor-certified medical devices and a service account whose 3 a.m. login spikes were normal quarterly-close activity. It also urges leaders to measure analyst approvals, edits and rejections of AI recommendations, and review latency, instead of automation rates or mean time to resolution.
12
Gartner: 70% of SOCs will pilot AI agents. Only 15% will see results
Gartner predicts 70% of large SOCs will pilot AI agents by 2028, but only 15% will achieve measurable improvements.
A Gartner report by analysts Craig Lawson and Andrew Davies projects that by 2028, 70% of large SOCs will pilot AI agents for Tier 1 and Tier 2 operations, but only 15% will achieve measurable improvements without structured evaluation. Prophet Security's State of AI in Security Operations 2026 survey found 40% of security teams use AI daily and 56% are evaluating or piloting it. The report offers evaluation questions covering workload reduction, TDIR outcomes, vendor viability, analyst upskilling, and autonomy boundaries to counter AI washing in the market.
28
55
55
42
30
30
Why 2026 is the Year to Upgrade to an Agentic AI SOC
Elastic Security Labs argues 2026 is the production inflection point for agentic AI in security operations centers.
Elastic Security Labs argues 2026 is the practical inflection point for agentic AI SOCs, noting nearly two-thirds of organizations are experimenting with AI agents while fewer than one in four have production deployments. The piece outlines operational challenges and recommendations: treat agents as non-human identities with least-privilege tool access, version-control system prompts as code, deploy unified agents with on-demand task packages, and enforce per-agent budgets and rate limits. It stresses explainability via RAG and transparent reasoning traces so analysts can verify and override autonomous decisions.
25
What the Data Says About AI in Security Operations in 2026
Prophet Security's 2026 survey of 250+ security pros: 40% use AI daily; AI users report 25%+ faster investigations and rising AI-driven attacks.
Prophet Security's State of AI in Security Operations 2026 report, based on a survey of 250+ cybersecurity professionals, found 40% of security teams use AI daily and only 4% have no adoption plans. Teams average 100 daily alerts (up to 1,000 at large firms), leave 28% of alerts uninvestigated, and 60% of respondents said missed alerts led to breaches or downtime. Among AI adopters, 72% report at least 25% faster investigations, 56% observed increased AI-driven attacks, and no respondents grant AI full unsupervised autonomy. Data privacy (44%) and explainability (41%) top the adoption hurdles.
32
30
30
55
30
42
30
42
55
55
30
60
42
42
30
57
30
What happens when AI agent governance is missing at scale
meshIQ engineering head Gourab Basu argues AI agent governance must inspect proposed tool calls in-flow, since prompts alone cannot control nondeterministic agents.
In a Help Net Security interview, Gourab Basu, Global Head of Engineering at meshIQ, argues that prompt instructions are an insufficient control boundary for nondeterministic AI agents. He advocates a framework-independent governance engine that inspects proposed tool calls and parameters before execution, citing an example of pausing refunds above $100 for human approval. He warns that scaling from ten to a thousand agents makes manual oversight and destination-side controls unworkable, so governance must sit inside the agent execution flow across frameworks such as FastMCP.
32