AGENTS

Google's asynchronous coding agent. Point it at a GitHub repo, it clones to a cloud VM, plans with Gemini, and opens a pull request. Tiered plans from 15 to 300 tasks per day.

Open-source AI agent built in Rust, now governed by the Agentic AI Foundation at the Linux Foundation. Desktop app, CLI, and API. 15+ model providers, 70+ MCP extensions.

Mac app for running parallel Claude Code, Codex, and Cursor agents in isolated workspaces. Watch every agent work at once, then review and merge their changes.

Open-source cloud sandboxes for AI agents. Isolated environments that start in under 200ms, run code in Python, JavaScript, and more, and persist sessions up to 24 hours.

Fable 5 ships with safety classifiers that route flagged requests away from the model. In production you need to handle this, and Anthropic shipped three ways to do it. Here's how each one works, with code, plus the billing rules nobody has written up.

Graphify is trending because coding agents keep hitting the same wall: they can edit files, but they still need a durable map of how the codebase, docs, schemas, and decisions connect.

InsForge is trending because coding agents can scaffold UI faster than they can safely operate databases, auth, storage, functions, and deployments. The backend now needs an agent-readable control plane.

Open-source terminal agent runtime with approval modes, rollback snapshots, MCP servers, LSP diagnostics, and a headless HTTP API. Uses DeepSeek models by default.

GitHub is filling with multi-agent frameworks, skills, and coding harnesses. The useful lesson is not that every team needs a swarm. It is that every agent needs receipts: tests, logs, diffs, and reviewable checkpoints.

SNEWPAPERS is a useful Show HN signal: the strongest agentic search products do not replace search results with prose. They teach the agent to operate a real search system.

DeepSeek V4 is trending because it is close enough to frontier coding models at a much lower token price. The real question for developers is where cheap reasoning belongs in an agent stack.

Flue is trending because it names the part of agent infrastructure that is becoming product-critical: the programmable harness around the model.

jcode is trending because it competes on a less glamorous but important agent metric: how cheap it is to keep many coding sessions alive.

Hugging Face's ml-intern is trending because it narrows the agent loop around one domain: papers, datasets, model training, Hub traces, and ML shipping workflows.

Open Design is trending because it turns Claude Code, Codex, Cursor, Gemini, and other CLIs into a design engine. The useful lesson is not design automation. It is artifact-first agent wrappers.

A trending refusal-direction paper is a reminder that model safety cannot be treated as a thin refusal layer. Builders need layered controls around the model.

GitHub trending is full of agent skill frameworks. The real shift is not bigger prompts or more agents. It is turning team process into inspectable, reusable operating instructions.

Cloudflare's Agent Memory primitive. What it stores, latency profile, how it compares to mem0, and how to wire it into your stack.

GPT-5.4 ships state-of-the-art computer use, steerable thinking, and a million-token window. Here is the implementation guide for builders, with real OpenAI SDK code, the 272K pricing cliff, and where it actually beats 5.3 and 5.5 in production.

GPT-5.5 and 5.5 Pro hit the API on April 24. Here is what changes for builders: pricing, agentic tasks, tool-use, and the real benchmarks I ran the day it dropped.