Agents

All topics

Models that plan, call tools and finish multi-step tasks on their own — from Claude Code and Manus to agent frameworks and benchmarks.

1,465 picksRelated topicsMCP & tool use AI coding Reasoning

Latest picks

841–860 of 1,465

May 21Thursday

AI HOT (Curated Pool)May 21, 07:28

Tencent Launches OS-Level AI Assistant Mavis on Windows, Mac, and Android

Tencent launched the OS-level AI assistant Mavis on May 21 across Windows, Mac, and Android, with document parsing, image recognition, system maintenance, partial offline use, model dispatching, and desktop control of mobile apps listed as supported functions.

Why it matters: HKR-H/K/R all pass: Tencent’s OS-level assistant spans Windows, Mac, and Android with concrete tool abilities. Model, pricing, and permission design are not disclosed, so it stays at the lower featured band.

Take

Mavis has one serious card: Tencent launched it on Windows, Mac, and Android at once, with local models and task routing. The pitch is clear. Move the agent out of the chat box and into files, system maintenance, and phone-app control. That is a better productivity-entry bet than another Yuanbao-style assistant feature.

The proof is still thin. Tencent says Mavis can do basically everything current agents do, but the article gives no task success rate, permission model, model list, or hardware floor. “Works after unplugging the network cable” is a good hook, yet offline task coverage is not specified. Microsoft Copilot has had the Windows surface for ages; the hard part was never placement. It is permissions, error cost, and user trust. Tencent has shipped the entry point first, and the product debt lands with it.

Latent SpaceMay 21, 06:42

Railway: The Agent-Native Cloud — Jake Cooper

Railway serves 3 million users with a 35-person team, adds about 100,000 signups per week, has raised $124 million, and has moved most workloads to its own bare-metal data centers with a reported three-month payback versus rented cloud capacity.

Why it matters: HKR-H/K/R all pass: the Railway interview has concrete growth, funding, and bare-metal details tied to agent infrastructure. It is a strong practitioner story, not a core model or major AI product release, so 74 fits the featured threshold.

r/LocalLLaMAMay 21, 05:25

What happened to Cohere’s Command-A series of models?

Cohere launched Command A+, describing it as its first MoE model under the Apache 2.0 license, with quantization work that lets it run well on 1 or 2 GPUs; the post says top-line performance still needs work.

Why it matters: HKR-H/K/R pass: Cohere open model news has clear local deployment facts. Reddit-level sourcing and missing parameter count, benchmarks, and context window keep it in the low featured band.

Take

Cohere is rebuilding open-weight credibility here, not claiming frontier status. Command A+ has three concrete hooks: Cohere’s first MoE, Apache 2.0 licensing, and quantization that runs on 1 or 2 GPUs. The missing pieces are louder: no parameter count, active size, context window, or benchmark table for SWE-bench, MMLU, GPQA, or even a clean latency setup. “Fastest and most responsive in our category” stays a house claim.

I like the Apache 2.0 choice because Cohere still sells enterprise agent infrastructure, and open weights let smaller teams clone parts of that workflow. But Qwen, DeepSeek, and Mistral trained the market to expect a three-part receipt: performance, inference cost, license. Command A+ has shown the license and deployment posture; it still owes the performance bill.

AI HOT (Curated Pool)May 21, 05:18

Google Stitch update: AI design assistant supports end-to-end building

Google updated its AI design partner Stitch with real-time streaming design builds, direct edits and feedback, codebase or Design.md imports, dynamic UI generation, shareable URL exports, and global availability.

Why it matters: HKR-H/K/R pass: Google Stitch adds streaming builds, codebase/Design.md import, and global access. It stays at the featured threshold because model details, pricing, and measured output quality are not disclosed.

Take

Stitch’s upgrade is aimed at the dirty gap between Figma prototypes and frontend implementation. The concrete hooks are useful: real-time streaming builds, direct edits, codebase or Design.md imports, dynamic UI generation, and shareable URL exports. That is a product-shaped answer to design-to-code, not just another prompt-to-mockup toy.

I don’t buy “full workflow build” yet. The snippet gives no supported frameworks, pricing, design-token handling, component-mapping error rate, or generated-code quality. v0, Lovable, and Bolt are already fighting over the same handoff layer. The gap is not whether a tool can produce a nice screen; it is whether it can enter an existing repo without creating cleanup work. If Stitch only assembles branded components into polished demos, it stays a Google showcase. If it respects production constraints, it becomes a workflow wedge.

The Verge · AIMay 21, 00:00

Google Search’s AI Evolution Includes More Ads

Google is adding Gemini-generated product explanations to Search ads for product queries, including Sponsored Product placements and some ads with built-in chatbots; the snippet cites a compact espresso pod machine example, but the post does not disclose rollout scope or pricing.

Why it matters: HKR-H/K/R all pass: Google is inserting Sponsored Product units and ad chatbots into Gemini shopping results. Scope, pricing, and performance data are not disclosed, so this stays in low featured rather than a major product-release band.

Take

Google is spending Search’s remaining trust on ad inventory, and the placement is ugly. In product queries, Gemini will generate a purchase explainer for a Sponsored Product; Google’s own example is a “compact espresso pod machine” search showing a Nespresso Vertuo Up. Some ads also get built-in chatbots. Rollout scope and pricing are not disclosed, so this reads as a product-direction signal rather than a complete commercial launch.

I don’t buy the “better shopping help” framing. Classic Search ads were constrained by labels, bidding, and ranking slots. AI Overviews already blur answers and source material on the same screen. Now Gemini is writing the reason to buy the sponsored item. That moves model output from retrieval into sales copy. Great for advertisers; another withdrawal from Search credibility.

May 20Wednesday

The Verge · AIMay 20, 21:24

If Google Can’t Make AI Agents Useful, Maybe No One Can

The Verge says Google announced multiple AI agents at I/O 2026 for information gathering, event planning, and inbox or calendar summarization; the RSS snippet says the agents can run continuously in the background, but the post does not disclose launch timing, pricing, or evaluation results.

Why it matters: HKR-H and HKR-R are strong because the Verge frames Google agents as a sector test; HKR-K is limited to background-running agents. Missing launch timing, pricing, and evals keeps it in the lower featured band.

TechCrunch · AIMay 20, 21:00

Figma adds an AI assistant to its collaborative canvas

Figma added an AI agent to its collaborative canvas, letting users use natural-language prompts to create new designs, edit existing ones, or automate tasks such as generating design iterations.

Why it matters: HKR-K and HKR-R pass: Figma puts an AI agent into a core collaborative design surface. Details stop at capability scope, with no model, pricing, or rollout timing, so this sits at the featured threshold.

Alibaba Technology · WeChatMay 20, 19:04

Zhenwu M890 AI Chip Debuts as Agentic Compute Foundation

Alibaba released a 128-card supernode server based on T-Head’s Zhenwu M890 AI chip, with P2P latency below 150 ns and rack bandwidth at the Pb/s level; it is live on Alibaba Cloud Bailian and supports Qwen, DeepSeek, and Kimi.

Why it matters: HKR-H/K/R all pass, but the source is Alibaba’s own tech post and lacks third-party benchmarks, pricing, or production volume. Score stays in the featured-threshold band for an AI infrastructure product update.

Xinzhiyuan · WeChatMay 20, 12:27

Behind Jensen Huang’s Douzhi Moment, Chinese GPUs Are Filling CUDA’s Moat

Moore Threads presented progress on its MUSA GPU ecosystem, with SDK 5.1.0 targeting CUDA 12.8 and supporting 761 driver and runtime APIs. The post says MUSA has entered SGLang’s mainline, is listed for 2026 Q2 hardware support, and supports automated library migration via MUSACODE.

Why it matters: HKR-H/K/R all pass: the headline has a meme hook, the post gives 761 APIs plus SGLang mainline support, and CUDA-lock-in anxiety is real. It remains a single-vendor ecosystem update, so it sits in mid featured rather than P1.

Take

MUSA’s move reads less like launch-stage theater and more like the grim work domestic GPUs must do: reduce CUDA migration pain. The summary gives three hard anchors: SDK 5.1.0 targets CUDA 12.8, supports 761 driver/runtime APIs, and SGLang has merged MUSA into mainline with 2026 Q2 hardware support listed. For inference teams, SGLang mainline support matters more than a vendor demo because it touches a real serving stack.

I don’t buy the “closing the CUDA moat” framing yet. CUDA’s moat is not API count alone; it is NCCL, compilers, profiling, kernel libraries, debugging scars, and operational trust. The article body is inaccessible, and there is no benchmark, board availability, memory spec, throughput, or pricing. Moore Threads has shown the migration door is getting narrower, not that NVIDIA’s moat has been filled.

Xinzhiyuan · WeChatMay 20, 12:27

UISEE Lists in Hong Kong as a Full-Scenario L4 Autonomous Driving Stock

UISEE listed on the Hong Kong Stock Exchange at HK$60.30 per share, with its public offering oversubscribed 6,777.29 times and a 90.5% share of the Greater China airport L4 commercial vehicle market in 2025.

Why it matters: HKR-H/K/R all pass: the IPO hook is concrete, with subscription and market-share numbers, and it ties to AV commercialization. It stays below 85 because this is not a foundation-model company IPO.

Take

UISEE is stretching the “all-scenario L4” label; the hard number supports airport autonomy, not general autonomy. The disclosed facts are concrete: HK$60.30 listing price, 6,777.29x public-offering oversubscription, and 90.5% share of the Greater China airport L4 commercial-vehicle market in 2025. That is a strong fenced-site story, especially for airports where routes, rules, and operating domains are tightly controlled.

The accessible body is only a WeChat verification page, so revenue, gross margin, fleet size, incident rate, and unit economics are not given. Compared with Waymo’s city-scale public-road proof, airport L4 looks closer to industrial automation than Robotaxi-style autonomy. That can be a good business; it just should not borrow the prestige of open-world L4 without the evidence.

Synced · WeChatMay 20, 11:49

After I/O, Google turns the search box into an agent entry point

Google announced Gemini 3.5 Flash at I/O and added AI Mode directly to Search; the company said its AI services now process over 3.2 quadrillion tokens per month, with more than 8.5 million developers using Gemini.

Why it matters: HKR-H/K/R all pass: Google I/O combines a model update, Search distribution, and concrete usage numbers. AI Mode inside the search box is heavier than a routine feature release, so it clears the same-day must-write band.

Take

Google’s sharpest move is putting Gemini 3.5 Flash inside the Search box, turning search intent into agent dispatch. AI Mode already has over 1 billion monthly users, Gemini handles 3.2 quadrillion tokens per month, and 8.5 million developers use it. Those numbers matter more than the 76.2% on Terminal-Bench 2.1. Benchmarks get matched; default placement inside Search does not.

I don’t buy the “Gemini 3.5 era” framing yet. Google shipped Flash, while Gemini 3.5 Pro is still internal, with Pichai promising “next month.” This smells like an entry-point land grab: wire agent behavior into 13 billion-user products first, then let the flagship model arrive later. For builders, Antigravity and Spark inside Workspace are the actual surface area. The singularity quote is conference theater.

Latent SpaceMay 20, 11:34

Google I/O 2026: Gemini 3.5 Flash, Omni, Spark, and Antigravity 2.0

Google announced Gemini 3.5 Flash at I/O 2026 with a 1M-token context window, 65k max output, four thinking levels, and pricing of $1.50 per 1M input tokens and $9.00 per 1M output tokens.

Why it matters: HKR-H/K/R all pass: this is a Google I/O model-and-product bundle with concrete context, output, thinking-tier, and pricing facts. It has same-day relevance for Claude, OpenAI, and coding-agent competition, so it clears P1.

AI HOT (Curated Pool)May 20, 10:39

Microsoft reportedly warns internally that GitHub faces existential risk as AI coding tools reduce hosting need

Microsoft internally warned that GitHub faces an existential risk from AI coding assistants such as Cursor and Claude Code, and told some teams to stop using Claude Code by the end of June 2026 and move to GitHub Copilot CLI.

Why it matters: HKR-H/K/R all pass: the angle is sharp, the summary gives a Claude Code-to-Copilot CLI deadline, and the workflow stakes are real. Single-source “reported” framing and no Microsoft response keep it below the 85 must-write band.

Take

GitHub’s problem is not that repositories vanish; developers are moving daily work into Cursor and Claude Code. The concrete tell is Microsoft asking some Windows, Microsoft 365, Outlook, Teams, and Surface teams to stop using Claude Code by late June 2026 and move to GitHub Copilot CLI, with security workflow and FY2027 cost control as the official rationale.

I don’t buy the “toolchain consistency” story cleanly. Copilot in 2021 lived inside editor autocomplete. Cursor in 2024 made the IDE a task surface. Claude Code in 2025 pushed multi-step engineering into the terminal. The repo can stay on GitHub while the decision layer moves elsewhere. The wild part: Copilot CLI still keeps access to Claude models. Microsoft is not blocking Anthropic’s intelligence; it is blocking Anthropic’s product doorway.

AI HOT (Curated Pool)May 20, 10:00

Qwen3.7: Agent Frontier

Qwen Studio released Qwen3.7 with chatbots, image and video understanding, and image generation. It also covers document processing, web search integration, tool calling, and artifact generation. The RSS snippet frames it as an agent-focused model, but the post does not disclose context length. It also omits benchmark scores, pricing, API limits, release schedule, and reproducible evaluation conditions.

Why it matters: HKR-H/K/R all pass: this is a Qwen flagship-model update with concrete capability coverage. Lack of benchmarks, pricing, and context-window details keeps it at the low end of the 85–94 band.

AI HOT (Curated Pool)May 20, 06:08

Gemini launches personal AI agent and Daily Brief

Gemini added Gemini Spark and Daily Brief: Spark acts as an always-on personal AI agent across Gmail, Google Docs, and Slides after user authorization, while Daily Brief is available to Google AI subscribers in the U.S. aged 18 or older.

Why it matters: HKR-H/K/R all pass: Google is adding Gemini Spark’s authorized actions across Gmail, Docs, and Slides, plus Daily Brief eligibility for US 18+ AI subscribers. This is a same-day Google agent product update.

The Verge · AIMay 20, 05:00

Google’s AI Future Demands Trust — and Your Personal Data

Google presented Gemini Spark, Daily Brief, and expanded Gmail AI inbox access at I/O 2026; the Verge snippet says these tools depend on large amounts of personal information, but the post does not disclose detailed data-handling terms.

Why it matters: HKR-H/K/R all pass, but the body gives product names and a personal-data dependency without data-handling details. Google I/O makes it featured, not a same-day must-write.

Take

Google’s risky move is not an always-on Gemini Spark; it is making Gmail, Calendar, and tasks the model’s front door. I/O 2026 names Gemini Spark, Daily Brief, and Gmail AI inbox, spanning event planning, daily summaries, custom to-dos, and personalized replies. Every feature needs private context. The available RSS snippet gives no retention rules, training exclusions, enterprise-domain boundaries, or human-review conditions.

I don’t buy the “useful products earn trust” story here. Google’s moat is distribution through Gmail and Calendar, which OpenAI and Anthropic cannot easily copy. Its exposure is the same surface area. Microsoft has at least kept pointing Copilot buyers to M365 tenant boundaries; Google’s disclosed pitch looks more like occupying the default workflow first and asking users to supply the trust later.

Financial Times · TechnologyMay 20, 04:47

Google to Release Smart Glasses and Add AI Agents to Search Engine

Google will release smart glasses and add AI agents to its search engine; CEO Sundar Pichai says features powered by a new Gemini model will narrow the gap with Anthropic and OpenAI, while the RSS snippet does not disclose specs, launch timing, or pricing.

Why it matters: HKR-H/K/R all pass: Google is moving Gemini agents into Search and smart glasses, a core entry-point product story. Missing specs, pricing, and timing keep it below the top band, but it fits the 85–94 must-write range.

Take

Google is betting on owned surfaces, not a clean Gemini win over Claude or OpenAI. The disclosed moves are specific: agents inside Search, plus smart glasses. The snippet gives only Pichai’s claim about closing the gap; it gives no specs, timing, pricing, context window, or task boundary for the agents.

I don’t buy the “catch-up” framing yet. Google’s durable advantage over the last year has been default distribution: Search, Android, Chrome, Workspace, YouTube. OpenAI and Anthropic won developer and prosumer mindshare through ChatGPT and Claude; Google can push agents into workflows users did not actively choose. The glasses angle smells like an Android XR distribution test. Ray-Ban Meta already showed that camera, voice, and lightweight notifications land faster than a general assistant story.

AI HOT (Curated Pool)May 20, 04:32

Production Guide for Claude Operating Real User Interfaces

ClaudeDevs published a production guide for Claude computer use, and the snippet lists four mechanisms: click accuracy, thinking effort level selection, context retention in long sessions, and replayable demonstration logging.

Why it matters: HKR-H/K/R all pass: a practical Claude UI-control guide with 4 concrete mechanisms. It is not an official model or product release, so it fits the quality-tutorial band rather than same-day must-write.

AI HOT (Curated Pool)May 20, 04:25

Smarter Google AI Edge Gallery: MCP Integration, Notifications, and Session Continuity

Google AI Edge Gallery adds experimental MCP support on Android, letting Gemma 4 coordinate external data sources including Google Workspace and Google Maps; the update also adds scheduled notifications and persistent chat history for faster restoration of long-session context.

Why it matters: HKR-H/K/R all pass: Google’s developer update adds experimental MCP, notifications, and session continuity to AI Edge Gallery. It is a mid-weight product update, not a model release or major capability launch.

TechCrunch · AIMay 20, 03:15

Google takes a page from Meta, announces audio-powered smart glasses at I/O 2026

Google announced “audio glasses” at I/O 2026, letting users issue voice commands across its apps and services, including Gemini; the RSS snippet does not disclose price, launch timing, or hardware specifications.

Why it matters: HKR-H/K/R pass: Google announced Gemini-linked audio glasses at I/O 2026, a credible AI-hardware platform move. Missing price, launch date, and specs keep it in the low featured band.

Take

Google is claiming the glasses entry point before showing a real product. The RSS snippet only says “audio glasses” support voice commands and can call Gemini plus Google apps. It gives no price, launch date, chip, camera setup, battery life, weight, or distribution plan. For AI-device teams, those missing fields matter more than the Gemini name; glasses fail first on comfort and battery, not model branding.

Meta Ray-Ban already proved the lower-friction path: no display, voice-first, camera plus earbuds behavior. Google is walking that same lane, but with better native tools on paper: Android, Maps, Gmail, Calendar, and Assistant/Gemini hooks. The wild part is that Google should have owned this category years ago. Without hardware specs or shipping timing, this is still an I/O ecosystem marker, not a Meta problem yet.