AI agents

What I learned

Major US banks are blocking third-party AI agents from customer accounts

Axios broke the story that banks are detecting unauthorized third-party agents operating inside customer accounts, and the cascade was everywhere: Digg logged Amazon, JPMorgan, Schwab and Delta limiting agent access (30 posts, 26 authors), a parallel Digg thread on bank-hack liability pulled 68 posts, and Fox Business ran a segment where the top comment - "i almost panicked but then i remembered i'm broke" (388 likes) - said more than the anchors did. Jamie Dimon reportedly confirmed Chase is blocking outside agents from logging in or making payments. USA Today confirmed the list is wider than first reported - Citi, Wells Fargo, Bank of America and JPMorgan Chase have all moved to limit third-party agent access, with Citi carving out an exception for "limited, read-only access to account information" through Citi-approved open banking providers, while stating it hasn't yet seen actual reports of agent-driven account breaches. That distinction, between blocking blind and blocking because of a confirmed incident, is becoming the real fault line in how each bank frames its policy.

A hacker used AI agents and a few thousand dollars to break into 100+ companies

Reuters reported a researcher watched the attack hit John Deere, SharkNinja and Cummins, and it landed on both Digg (39 posts) and Hacker News via The Verge. The companion Verge piece on websites closing their doors to agents hit 159 points and 149 comments on HN - the agent-vs-web arms race is officially the subplot. A separate TikTok thread on @ceomind.clips (23,528 likes, 795,416 views) dug into whether OpenAI's autonomous agents really hacked Hugging Face, or whether that framing oversold what happened. The underlying mechanics line up with what security researchers have been warning about for months: OWASP's Agentic AI Security Cheat Sheet names prompt injection, direct and indirect, as the dominant attack vector, where malicious instructions smuggled in through a webpage, document or email can hijack an agent's behavior entirely without touching the underlying model. Palo Alto Networks frames the resulting shift bluntly - "the attack surface isn't the response, it's the workflow" - which is exactly the multi-step, tool-using surface that let one attacker with a few thousand dollars scale across 100+ companies.

"Is anyone else finding AI agents way too unreliable for real workflows?"

That r/AI_Agents thread hit 107 upvotes and 98 comments with the money quote: "for anything multi-step, it feels like a roll of the dice whether it completes the task right or quietly breaks on step three." It rhymes with the Ars Technica piece on HN (365 points) - "AI coding agents generate more code, but not more software" - and a related r/AI_Agents thread (97 upvotes) on builders forgetting basic software engineering around prompt injection and goal hijacking. An Instagram reel from thereviewuniverse framed the same gap as "Agents That Survive," arguing the hard part isn't building an agent, it's keeping one alive in production once model choice, security and cost all collide, a theme r/LocalLLaMA regulars echo when they compare self-hosted setups against the same multi-step failure modes. A recent academic survey on LLM agent evaluation backs up the practitioner gripes with harder language, noting that enterprise deployments demand "reliability guarantees" across an agent's entire chain, memory access, orchestration logic, and inter-agent handoffs, that most current agent stacks simply weren't engineered to provide.

Anthropic launched Claude Duet, a proactive agent that texts you first

Per @malikontech (592 likes, 13,608 views), Duet watches your inbox and calendar, runs on Claude Opus 5.5 as a standalone iPhone/Android app, and is waitlist-only for Pro and Max subscribers. The "always-on agent" wars got framed by @tjrobertson52 (730 likes) as Claude Duet vs ChatGPT Dots vs Meta Muse - TechCrunch's roundup of agents that "live in your text messages" confirms the category is real. a16z investor Justine Moore made a related bet on Instagram that editing agents, not generation agents, are the next frontier, arguing the real time sink was never filming, it was the 80% spent editing afterward.

"I let Opus 5.5 try to make money on its own. It made $13. Then the farm blew up."

That r/ClaudeCode update hit 165 upvotes and 102 comments - 551 dead business ideas, a self-built "graveyard," then thirteen framed dollars. It pairs with r/AI_Agents at 131 upvotes arguing Anthropic's own data shows we're "becoming middle managers for AI agents" - babysitting pipelines jumped from 10% to 22% of the average employee's agent sessions. On X, @heisblesse made the enterprise case plainer with a thread on Understanding How B.AI's Agent Infrastructure Can Support Automated Workflows, arguing agents beat rule-based automation precisely because they interpret requests instead of just executing fixed scripts, which is the same bet the Opus 5.5 experiment was quietly testing.

Agency Agents hit 155,000 GitHub stars for a 200+ specialist open-source library

Per @ai.with.andrew (5,349 likes, 97,996 views), it runs devs, designers, marketers and ops like a real agency. It's part of a wave of practitioner "one agent, many skills" takes: @jakevanclief (11,434 likes, 279,885 views) argued "people are wasting their time building AI agents" because harnesses like Claude Code already let one AI become whatever agent you need, and @itsborjao (4,285 likes) pushed "one agent with a playbook for every job." A companion Instagram reel from lostandlucky made the same argument in text form, and @buildwithai.club (2,608 likes, 41,812 views) shipped a free 11-skill Agent Skill pack that turns Claude into a whole YouTube production team. On the voice side, Hermes Talk shipped as a free plugin for Hermes Agent that hands work to a background agent while you keep talking. Elsewhere, a Super Agent setup for Roblox development, per @trevsagents (9,105 likes, 137,773 views), claims games now get built overnight while the dev sleeps.

Regulators and standards bodies are racing to catch up with agent identity and access risk

NIST argues agentic AI needs its own identity foundation, warning that credential-sharing between humans and agents "creates accountability gaps" with real security, privacy and legal fallout. A Gartner report distributed via IBM goes further, arguing legacy IAM systems fall short for three distinct categories of risk: enterprise-managed agents, anonymous web-interfacing agents, and undeclared agents operating inside ordinary multimedia channels. The banking-specific version of this concern shows up in the Financial Stability Board's final report on responsible AI adoption, which flags data breaches and manipulation of customer details as top-line risks and notes that banks are starting to test an agent's "entire workflow," including memory access and orchestration logic, before granting it more autonomy based on performance. China got there first on paper, at least - Shanghai Jiao Tong University's white paper released during China's 2025 National Cybersecurity Awareness Week proposed a "full-stack and full-lifecycle security protection framework" for AI agents, explicitly assigning risk management responsibilities and control boundaries, months before Western banks started publicly blocking agents at the door.