Package catalog
Distribution names, imports, source locations, runnable examples, and release groups.
Find the library, application, or example for your integration. Python distributions use hyphens (a13n-harness); imports use underscores (a13n_harness).
Python packages
| Distribution | Source | Purpose and guide |
|---|---|---|
a13n-harness | packages/a13n-harness | Agent composition and execution, tools, state, and providers |
a13n-stream-protocol | packages/a13n-stream-protocol | Convert Harness observations to AG-UI events |
a13n-harness-ui | packages/a13n-harness-ui | Terminal and browser workbench, also available as an embeddable App |
a13n-envd-client | packages/a13n-envd-client | Python EIP client for sessions, files, processes, and output |
a13n-service | packages/a13n-service | Managed-agent runtime with identity, resources, and durable execution |
a13n-logging | packages/a13n-logging | Structured logging for libraries and applications |
Environments is part of Harness and can also be used without an agent.
Native daemon
crates/a13n-envd builds the Envd daemon. It provides sessions, files, commands, processes, and retained output through EIP. See installation, configuration, and the Python client.
Harness's Local Envd provider connects the daemon to an Environment. Harness UI can acquire a matching executable automatically when that provider is selected.
Service SDKs and CLI
Service clients live in independent Python, TypeScript, Go, and Rust repositories. The Rust repository also supplies a13n-service-cli. They call the Service HTTP API; use Harness to embed agent execution directly.
SDKs and CLI links to each client's installation instructions and examples. The HTTP reference describes this repository's Service API.
Frontend source
| Source | Purpose |
|---|---|
frontend/apps/a13n-console | Service's browser interface for resources and conversations |
frontend/apps/a13n-harness-ui | Harness UI's interactive browser workbench |
frontend/packages/a13n-ui | Shared React components, design tokens, and brand assets |
Console ships with Service; the Harness UI browser ships with the Python UI distribution. Both are bundled in their wheel and sdist, so installed users need no Node.js. For frontend development, follow the frontend README.
Runnable example projects
Each project has its own dependencies, tests, and run instructions. Start with its README:
| Example | Demonstrates |
|---|---|
| Agent application | Offline streaming turns, saved state, and restart recovery |
| Environment providers | Direct Local, Local Envd, and Docker lifecycles |
| Capabilities and plugins | Custom capabilities, Harness plugins, Environment providers, and run extensions |
| Installed provider plugin | Package an Environment provider and load its installed entry point |
| MCP App | A stdio MCP server with an interactive browser counter |
The examples index lists run commands and prerequisites. Environment examples covers additional built-in providers.
Releases
| Release group | Version relationship |
|---|---|
| Harness and Stream Protocol | Same release version; Stream Protocol requires that exact Harness version |
| Envd and its Python client | Same release version |
| Harness UI, Service, Logging | Independent releases; package metadata declares compatible dependencies |
The frontend ships with its owning application. Example projects are separate from production releases. Source workspace versions are development placeholders; use published package metadata when selecting deployed versions.
For contributor setup, see Contributing. For repository and release contracts, see the repository model.