For people who
run agents.

Choose an agent and understand the harnesses around it. See what each can do, what it costs, and where it can fail. Follow the releases and practical guides that affect your work.

30 agent ecosystem briefs · Source-backed reporting · Testing labeled honestly

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 intelligence

AI Agents Are Building Office Alternatives. The Factory Is the Story.

ArtCraft's public code, release artifacts and agent-facing commands show a serious software-factory experiment. Its own alpha and compatibility gaps explain why that isn't yet a dependable Office replacement.

What this site is

Agent dossiers help you choose. The change log helps you keep up. Practical guides help you put the work to use.

How the change log is written

We connect primary sources, clearly labeled tests, operational limits, 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.

Permissions and limits stay visible

A useful agent review explains what the runtime can change, which accounts it can reach, when it needs approval, and who owns a failed run.

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