the brief

Agent tooling took a step forward: Claude’s auto mode broadened access, Railway gave agents safe computers, Grok added real connectors, and Claude Code exposed MCP-level costs. Security stayed hot with Perplexity’s Bumblebee scanner and Anthropic’s Glasswing surfacing 10k+ critical vulns. Research pushed on latency with diffusion-style LMs, while hardware constraints loomed large in the background.

the poursit · sip · 11 items

alerts

(01)
  • @unknownMay 22, 07:38 PM

    Glasswing surfaces 10k critical vulns

    Anthropic’s Project Glasswing and partners report 10k+ high/critical flaws found in essential software in a month—expect a surge in coordinated disclosures and patching workload.

    Last month we launched Project Glasswing, our collaborative AI cybersecurity initiative. Since then, we and our partners have found more than ten thousand high- or critical-severity vulnerabilities in essential software.

    signal 5hype 4ai_securityinitiativeprogress_updatesource ↗

pulse

(06)
  • @perplexity_aiMay 22, 05:03 PM

    Perplexity open-sources Bumblebee scanner

    A read-only macOS/Linux scanner for risky packages, extensions, and AI configs, Bumblebee also hooks into Computer to trigger deeper scans as new threats emerge.

    Today we're open-sourcing Bumblebee, a read-only scanner for macOS and Linux. It checks developer machines for risky packages, extensions, and AI tool configs. Connected to Computer, it can trigger deeper scans whenever a new supply-chain risk emerges. github.com/perplexityai/b… pic.x.com/wXauD4wDOT

    signal 8hype 2open_sourcesecuritysupply_chainsource ↗
  • @ClaudeDevsMay 22, 10:08 PM

    Claude auto mode hits Pro plan

    Auto mode is now available to Pro users and supports Sonnet 4.6 alongside Opus 4.7, making hands-off task runs more accessible.

    Two updates to auto mode: · Now available on the Pro plan · Sonnet 4.6 is now supported, alongside Opus 4.7 Shift+tab, and let Claude run.

    signal 7hype 2auto_modeproduct_updateclaudesource ↗
  • @unknownMay 22, 04:01 PM

    DeepSeek V4 Pro pricing slashed

    DeepSeek makes its 75% discount permanent, with near-free cache pricing—resetting cost expectations for high-end inference and pressuring competitors.

    We are making our discount permanent! 🎉 Enjoy building with DeepSeek-V4-Pro and bring your innovative ideas to life! 🚀 pic.x.com/V8atbTaogH x.com/deepseek_ai/st…

    signal 3hype 6pricingmodel_providerdeepseeksource ↗
  • @unknownMay 22, 06:46 PM

    Grok adds Vercel, Canva, Gamma, S&P connectors

    New connectors expand Grok’s automation surface from site building and creative tooling to market data, enabling richer end-to-end agent workflows.

    New connectors available Build sites with Vercel, create anything in Canva, design decks in Gamma, and tap into market data from S&P Global. pic.x.com/UbRINA2CLw

    signal 5hype 2product_updateconnectorsintegrationssource ↗
  • @RailwayMay 22, 09:21 PM

    Railway gives chat agent sandbox VMs

    Priority Boarding users get sandbox VMs for the chat agent plus HA static egress and org guardrails—bringing safer real-computer control to agents.

    We gave the agent a computer Changelog #0291 • Sandbox VMs for the chat agent to Priority Boarding • HA static egress to Priority Boarding • GitHub org guardrails railway.com/changelog/2026…

    signal 7hype 2platform_updateagent_runtimesandbox_vmssource ↗
  • anthropics/claude-code· feedMay 22, 10:09 PM

    Claude Code adds granular usage costs

    v2.1.149 surfaces per-category and per‑MCP‑server usage drivers, adds UI polish and enterprise controls—giving teams clearer cost and limit visibility.

    v2.1.149 — What's changed /usage now shows a per-category breakdown of what's driving your limits usage — skills, subagents, plugins, and per-MCP-server cost /diff detail view can now be scrolled with the keyboard (arrows, j/k, PgUp/PgDn, Space, Home/End) Markdown output now renders GFM task list checkboxes (- [ ] todo / - [x] done) instead of plain bullets Enterprise: added the allowAllClaudeAiMcps managed setting to load claude.ai cloud MCP connectors alongside managed-mcp.json Fixed a Powe...

    signal 9hype 1release_notesclaude_codemcpsource ↗

findings

(02)
  • huggingface/blog· feedMay 23, 12:02 AM

    Diffusion language models promise speed

    Hugging Face details NVIDIA’s Nemotron‑Labs work on diffusion-style LMs targeting near speed‑of‑light text generation via highly parallelizable sampling with competitive quality.

    Towards Speed-of-Light Text Generation with Nemotron-Labs Diffusion Language Models

    signal 8hype 3diffusion_lmperformancebenchmarkssource ↗
  • @unknownMay 22, 02:24 PM

    Query 2.19B webpages via DuckDB

    April 2026 CommonCrawl and URL index on Hugging Face Buckets are directly queryable over hf:// with DuckDB, enabling ad‑hoc SQL at web scale without downloads.

    You can now run SQL over 2.19 BILLION web pages. Zero download! @CommonCrawl April 2026 crawl + URL index are on @huggingface Storage Buckets. @duckdb reads it straight over hf:// I counted all 2.19B in ~35s. Or point your own agent at it 👇 huggingface.co/spaces/davanst… pic.x.com/3NdWEuS0k2

    signal 7hype 3common_crawlduckdbhuggingfacesource ↗

voices

(02)
  • simonw/blog· feedMay 22, 10:01 PM

    Memory shortage reshapes device pricing

    Simon Willison spotlights David Oks’ argument that AI‑driven DRAM/NAND constraints will raise consumer electronics costs, a planning reality for AI builders.

    The memory shortage is causing a repricing of consumer electronics — <p><strong><a href="https://davidoks.blog/p/ai-is-killing-the-cheap-smartphone">The memory shortage is causing a repricing of consumer electronics</a></strong></p> David Oks provides the clearest explanation I've seen yet of why consumer products that use memory are likely to get significantly more expensive over the next few years.</p> <p>The short version is that memory manufacturers - of which there are just three remaini...

    signal 6hype 2supply_chainsemiconductorsmemorysource ↗
  • @mattpocockukMay 22, 04:00 PM

    Test seams list for agent reliability

    Matt Pocock argues teams should maintain an explicit registry of agreed test seams so agents don’t make poor testing choices, improving safety and maintainability.

    Another layer of documentation I'm considering (along with CONTEXT.md and ADR's) is a list of all the agreed test seams in the app Agents simply cannot be trusted to make good decisions about what to test, and at what seam. For every small change, they extract out only what

    signal 6hype 1testingdocumentationagentssource ↗