For people who
run agents.

Three places. Choose an agent. Read what changed. Check the evidence behind a skill or MCP server. The rest of the site supports those three jobs.

Registry stats loading…

Every report answers

1

What actually changed?

We separate release-note language from the behavior, policy, price, limit, or compatibility change that matters in practice.

2

What could it cost or break?

We look for pricing changes, migration risk, reliability regressions, security exposure, and hidden operational limits before recommending an update.

3

What should you do next?

Each report ends with a practical verdict: update, wait, test first, pin a version, change configuration, or ignore the announcement.

Latest intelligence2026-09-22

"Anthropic's Claude API Took a 1h20m Hit on Opus 5, Fable 5/5.1, and Mythos 5/5.1 on September 22. Agent Stacks That Routed Everything Through Anthropic Stopped"

On September 22, 2026 at 00:50 UTC, Anthropic returned elevated error rates simultaneously on Claude Opus 5, Claude Fable 5 and 5.1, and Claude Mythos 5 and 5.1 for one hour and twenty minutes. Agent stacks that routed everything through Anthropic's top tier stopped. Independent user-impact confirmation from Downdetector, Reddit, and two news outlets. Recommended action: audit your routing table, wire Status-page alerts, and test the fallback before you need it.

What this site is

We have been writing about agents. This is the map, so you do not have to guess which page does which job.

How the change log is written

We do not rewrite launch posts. We connect primary sources, reproducible tests, scanner evidence, Registry records, and technical guides to the decision in front of you.

Primary sources before commentary

Pricing, policy, security, compatibility, and incident claims start with official documentation, repositories, advisories, or status pages. Community reports are labeled as experience, not proof.

Tests are reproducible or clearly untested

Field reports name the version, environment, method, inputs, and limitations. If we only compared documentation, we say so.

Registry and scanners support the story

The skills and MCP Registry remains free. Its source links, scan states, provenance, and explicit evidence gaps help test whether an ecosystem claim survives contact with real artifacts.

Blueprints and guides remain practical

Durable technical guides and inspectable workflow manifests turn a news event into implementation work you can adapt and validate in your own environment.

Start with an agent

See the full list →
Coverage

The list is short on purpose.

A landing page that says "AI agent" is not a listing. The directory covers coding, ops, voice, research, and go-to-market runtimes. Autonomy is a tested facet, not a slogan.

// CHANGES_WITH_CONSEQUENCES

Follow the changes that matter.

Weekday impact reports, a weekly Before You Update brief, and tested comparisons when the evidence supports them. No quota filler.

The change log is the news. Agent dossiers are the catalog.

Open the change log

Choose an agent. Then follow what changes.

Live registryRegistry loading…Snapshot date unavailable