Search “Agents”

Nathan Lambert says he doesn't know how to try out Gemini in the agent era

On October 29, 2026, Nathan Lambert said he didn't know how to try out Gemini in the agent era and believed he needed to make up for this gap. He mentioned that Gemini seemed to have been absent since December 2025, but might be making a comeback. The tweet quoted Sundar Pichai's post announcing Gemini 4 Carbon, which stated that the model ranked first with 59 points on the Artificial Analysis Intelligence Index v5.0, and scored 88.2% on SEC-bench Pro, 54.8% on ExploitGym, and 71.0% on CWE-bench. There have been no further developments so far.

Nathan Lambert says he doesn't know how to try Gemini in the Agent era

On October 29, 2026, Nathan Lambert said he didn't know how to try out Gemini in the agent era and believed he needed to make up for this gap. He mentioned that Gemini seemed to have been absent since December 2025, but might be making a comeback. The tweet quoted Sundar Pichai's post announcing Gemini 4 Carbon, which stated that the model ranked first with 59 points on the Artificial Analysis Intelligence Index v5.0, and scored 88.2% on SEC-bench Pro, 54.8% on ExploitGym, and 71.0% on CWE-bench. There have been no further developments so far.

View story:Nathan Lambert says he doesn't know how to try out Gemini in the agent era

Anthropic discloses four Agent safety incidents in IPO prospectus

Anthropic publicly filed its Form S-1 registration statement on October 26, planning to list on Nasdaq under the ticker ANT. The prospectus shows that its revenue grew from $41 million in 2023 to $16.3 billion in the first half of 2026, with $11.6 billion in the second quarter alone and operating profit of $974 million; about 48% of first-half revenue flowed through Bedrock, Vertex and Azure Marketplace, and it listed NVIDIA compute commitments of up to $120.5 billion. Subsequently, on October 27, World Trade Securities estimated that its cash reserves could approach $400 billion by the end of 2027; in the cover letter of its IPO filing, Anthropic reiterated that Claude will not display ads, and on October 28 it acknowledged that its life sciences business lacks physical laboratory experience. On October 28, Goldman Sachs secured the lead-left seat on the prospectus, and TechCrunch reported that public shareholders have almost no say over board nominees. On October 29, the prospectus disclosed four previously unreported Agent safety incidents. On October 30, Reuters reported that its IPO fundraising cap could reach $100 billion; Steve Eisman accused the prospectus of deliberately omitting third-quarter data, and Anthropic has not yet responded.

View story:Anthropic Publicly Submits S-1 Registration Statement for Proposed IPO on Nasdaq

AMD Unveils CPU-Centric Helion Rack Design for Agentic AI

At OCP Global Summit, AMD announced Helion, a CPU-centric AI data center compute infrastructure design for running large numbers of AI agents simultaneously. Unlike Helios, which stacks large numbers of GPUs, this design targets the CPU demands created by agents repeatedly executing programs and accessing databases. A configuration for large data center operators can hold up to 32,768 sixth-generation EPYC Venice CPU cores in a single rack, with model inference requests handed off to separate GPU systems; the enterprise configuration places EPYC CPUs and Instinct MI350P GPUs in the same rack, holding up to 16 GPUs, and integrates a token router that routes requests to high-performance models or self-hosted open-source models to lower AI operating costs. AMD will offer Helion as an open reference design and contribute the specification to OCP; eight server vendors including Cisco, Dell, HPE, Lenovo and Supermicro are developing related systems, with launch planned for November.

Playwright 1.60 makes Test Agents production-ready

Playwright 1.60 makes Test Agents (planner, generator, healer) production-ready. According to the report, Playwright has shifted from a testing framework to a runtime for agents to operate browsers; the MCP server has matured further, and ARIA snapshots now include bounding boxes. The report breaks this change into four layers: perception, execution, diagnosis, and roles: ARIA snapshots provide structured page information, browser.bind() lets exploration, the test runner, and MCP share the same browser instance, traces are folded into HAR network capture, and planner, generator, and healer form a closed loop from plan to heal. The report also stresses that the healer does not touch assertions, and fixes should be submitted as PR diffs for human review rather than merged automatically. This news currently comes from a single-source report, with no additional independent sources or official statements yet.

Playwright 1.60 makes Test Agents production-ready

Playwright 1.60 makes Test Agents (planner, generator, healer) production-ready. According to the report, Playwright has shifted from a testing framework to a runtime for agents to operate browsers; the MCP server has matured further, and ARIA snapshots now include bounding boxes. The report breaks this change into four layers: perception, execution, diagnosis, and roles: ARIA snapshots provide structured page information, browser.bind() lets exploration, the test runner, and MCP share the same browser instance, traces are folded into HAR network capture, and planner, generator, and healer form a closed loop from plan to heal. The report also stresses that the healer does not touch assertions, and fixes should be submitted as PR diffs for human review rather than merged automatically. This news currently comes from a single-source report, with no additional independent sources or official statements yet.

View story:Playwright 1.60 makes Test Agents production-ready

Google releases AQuA quality Agent reference implementation

On October 8, the Google Developers Blog publicly released the AQuA (Ambient Quality Agent) reference implementation. This implementation has a quality Agent run alongside production Agents, responsible for clustering failed conversations, reviewing issues, and anchoring diagnoses to deployment source code snapshots. Related coverage argues that this will not make testing disappear, but rather hands over to test teams the tasks of defining anomalies, calibrating evidence, and bearing release responsibility, and presents three validation methods: implanting known faults, blind-review controls, and root-cause replay. There are currently no facts about subsequent developments.

Google releases AQuA quality Agent reference implementation

On October 8, the Google Developers Blog publicly released the AQuA (Ambient Quality Agent) reference implementation, which places a quality Agent alongside the production Agent, responsible for clustering failed conversations, reviewing issues, and anchoring diagnoses to deployment source code snapshots. Related reporting notes that this type of outer-loop quality inspection may still share blind spots with the production Agent in terms of models, logs, and business definitions, and that testing teams need to shift toward designing observation surfaces, calibrating anomaly labels, maintaining evidence chains, and defining escalation rules. The reporting also presents three verification methods—injecting known faults, blind-review controls, and root-cause replay—as well as a phased adoption path for small teams. There are currently no follow-up developments.

Google releases AQuA quality agent reference implementation

On October 8, the Google Developers Blog publicly released the AQuA (Ambient Quality Agent) reference implementation. This implementation has a quality Agent run alongside production Agents, responsible for clustering failed conversations, reviewing issues, and anchoring diagnoses to deployment source code snapshots. Related coverage argues that this will not make testing disappear, but rather hands over to test teams the tasks of defining anomalies, calibrating evidence, and bearing release responsibility, and presents three validation methods: implanting known faults, blind-review controls, and root-cause replay. There are currently no facts about subsequent developments.

View story:Google releases AQuA quality Agent reference implementation

Google releases AQuA quality agent reference implementation

On October 8, the Google Developers Blog publicly released the AQuA (Ambient Quality Agent) reference implementation, which places a quality Agent alongside the production Agent, responsible for clustering failed conversations, reviewing issues, and anchoring diagnoses to deployment source code snapshots. Related reporting notes that this type of outer-loop quality inspection may still share blind spots with the production Agent in terms of models, logs, and business definitions, and that testing teams need to shift toward designing observation surfaces, calibrating anomaly labels, maintaining evidence chains, and defining escalation rules. The reporting also presents three verification methods—injecting known faults, blind-review controls, and root-cause replay—as well as a phased adoption path for small teams. There are currently no follow-up developments.

View story:Google releases AQuA quality Agent reference implementation

Microsoft proposes using Guardian Agents to monitor enterprise AI agents

Microsoft has proposed a plan to use Guardian Agents to monitor and regulate the actions of enterprise AI agents. Hayete Gallot, Executive Vice President of Microsoft's security division, said in a blog post that Guardian Agents should be deployed to monitor and intervene before AI agents execute actions, and stated that frontier models cannot be trusted no matter where they come from. The plan intends to bring enterprise agents under centralized management, assigning each agent an identity, container, and permission policy, then combining identity, data, cloud, endpoint, network, and runtime signals to assess risk in real time, with red team and blue team agents intervening when risk rises. The plan will be implemented through Microsoft's Project Perception security system announced in July. The plan is still at the proposal stage, and there are no public facts about further implementation progress.