Overview

One Rust interface to the coding agents installed on a machine.

Users already have Claude Code, Codex, Cursor, opencode, Kiro, and friends installed and logged in. Each one has its own CLI, protocol, and quirks, so an app built on top of them ends up with a driver per agent.

anyagent is that layer, written once. It finds the agents, speaks each one’s protocol (native or ACP), and gives you one typed API.

Quickstartcrates.io

Three objects

Runtime::discover()  ->  Runtime::open()  ->  (Session, Events)

  your app ── prompt / answer / configure ──►  Session
                                                  │
                                                  ▼
                                            agent process
                                                  │
  your UI  ◄── text / tools / requests / usage ── Events

Object	Role	You call it for
Runtime	Finds agents, opens sessions	discover, probe, open, generate, plan_usage
Session	Command handle for one live conversation	prompt, answer, configure, cancel, rollback, close
Events	The stream everything comes back on	one match on EventKind

Who owns what

anyagent owns	Your app owns
Finding and launching agent processes	The transcript store
Speaking each wire	Titles, threads, worktrees
Turn rules: one TurnEnded per turn, steer or queue, request lifetimes	The UI and the policy behind it
Normalizing events and tool calls	What to do with a permission request

Design rules

1. Same types for every agent. Provider-specific data rides in extensions instead of leaking into the API.
2. Capabilities are reported, not assumed. After open, the session tells you what this agent can do on this connection. Gate features on that, not on the agent’s name.
3. A turn ends exactly once. Whether the wire said so or anyagent inferred it, you get one TurnEnded.

Where to go

Quickstart

Install, discover, open, prompt, stream, answer one permission.

Core API

Runtime, Session, SessionOptions, every EventKind, requests, errors.

Features

Each thing anyagent does, in a few sentences and one snippet.

Agents

The catalog, the capability matrix, per-agent quirks, custom ACP agents.

Building an app

How the pieces fit in a real chat app: threads, streaming, permissions, persistence.

Architecture

The codebase map and how an event travels from wire to your UI.

License

MIT or Apache-2.0.