Agent UI
a13n-ui is the local single-user Host for Agent Foundation Harness. Its accepted interface selects WebUI by default and also exposes a TUI:
a13n-ui
a13n-ui webui
a13n-ui tui
Both surfaces share one application service, local session authority, Harness execution path, and a13n-stream-protocol AG-UI projection.
The repository Make aliases preserve the same default and surface selection:
make agent-ui
make agent-ui tui
make agent-ui invokes the package-provided a13n-ui command with no positional surface, selecting its default WebUI. Appending the tui goal forwards that positional argument and invokes a13n-ui tui exactly once. Asset preparation remains an independent build concern.
The repository directory is packages/agent-ui, the Python distribution is a13n-ui, and the import package is a13n_ui. The private browser source lives in apps/harness-ui.
Local Store Development
Agent UI owns its SQLite schema and Alembic history independently from Foundation Service. Generate a reviewed revision from the repository root against a disposable SQLite database:
make agent-ui-db-migrate msg="describe the schema change"
The generator upgrades the disposable database to the current package head before comparing it with Agent UI metadata. Application startup only applies committed migrations; it never autogenerates against a user's data root.
Dependencies
The source manifest declares unversioned dependencies on a13n-environment-provider, a13n-harness, and a13n-stream-protocol, so uv resolves all three from the workspace during repository development. Before tagging an Agent UI release, set [tool.a13n.agent-ui-release].harness-version to one published canonical Harness release such as 1.2.3 or 1.2.3-rc.1; the 0.0.0 placeholder blocks a real release. Agent UI release automation pins all three dependencies to that exact normalized Python version before building publishable artifacts.
Browser Assets
Compiled frontend files are not committed to Git. Repository builds compile Harness UI and copy it into the generated a13n_ui/static/ tree before building Python artifacts. Both the sdist and wheel contain those files, and rebuilding a wheel from the sdist does not require Node.js. A source-checkout package build fails when the assets have not been prepared.
Versioning
Agent UI releases independently through release/agent-ui-v<version>, where <version> is stable X.Y.Z or RC X.Y.Z-rc.N. Its version does not need to match the selected Harness release; Python package metadata represents either RC as X.Y.ZrcN. Harness UI has no independent npm artifact, version, tag, or release workflow.
The accepted architecture is defined in the Agent UI specification.
Metadata
Release files for a13n-ui 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| a13n_ui-0.0.3.tar.gz | 58.5 kB | Without provenance | Details for a13n_ui-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| a13n_ui-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for a13n_ui-0.0.3-py3-none-any.whl |
Total release size: 131.6 kB
Release files / a13n_ui-0.0.3.tar.gz
| Download URL | a13n_ui-0.0.3.tar.gz |
|---|---|
| Size | 58.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7728e3b9e086d1a59b7d8b3740bf2948c0d4efb29e0a9e7118d932873c85d49c
|
|
BLAKE2b-256 checksum How to use checksums |
24be78593a6824f7677d3b653e8d2ad33f27f4c426c7340e4eea10fce0858f3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.7 {"installer":{"name":"uv","version":"0.12.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / a13n_ui-0.0.3-py3-none-any.whl
| Download URL | a13n_ui-0.0.3-py3-none-any.whl |
|---|---|
| Size | 73.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e432cd8b636c7751914bdd761d94dfd6571c372cb460b2ef871ac7289808abc6
|
|
BLAKE2b-256 checksum How to use checksums |
86ad5af70cc7873314cdc1df084e75f7dce2788575cc5714e769e41a822ef029
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.7 {"installer":{"name":"uv","version":"0.12.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for a13n-ui 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.