aware-terminal-providers
aware-terminal-providers supplies provider automation primitives for aware-terminal. The package bridges to the terminal-owned provider interface/registry and registers concrete implementations so desktop agents can install, update, launch, and resume third-party coding assistants (OpenAI Codex, Anthropic Claude Code, Google Gemini, and future providers).
Quickstart
# Run tests for the terminal provider registry
uv run --project libs/providers/terminal pytest
# Install the package locally (editable mode)
uv pip install -e libs/providers/terminal
# Trigger the GitHub workflow that refreshes provider manifests (agents/CI)
uv run --project tools/release-pipeline release-pipeline workflow trigger \
--workflow update-providers \
--dry-run
When
aware_sdkships, the public story will useaware-cli release terminal ...commands; the release-pipeline invocation above is for maintainers and CI.
Package Layout
aware_terminal_providers/
├── __init__.py # Ensures aware-terminal is importable and re-exports the shared registry
├── core/ # Shared helpers (installer/env/runners, provider base class)
│ └── ...
└── providers/ # Provider implementations (one folder per provider)
├── codex/
├── claude_code/
└── gemini/
scripts/
└── update_provider_versions.py # Fetch npm dist-tags and refresh release manifests
The accompanying tests live under tests/ and validate the registry contract.
Current Status
- Registry scaffolding with stub providers for Codex, Claude Code, and Gemini (registry hosted in
tools/terminal/aware_terminal/providers/). - Codex, Claude Code, and Gemini adapters now surface install/update detection (opt-in auto install via
AWARE_TERMINAL_PROVIDERS_AUTO_INSTALL=1) and return launch/resume specs ready for tmux orchestration. Version data is sourced from the checked-inreleases.jsonmanifests. - Core helpers scaffolded for installer/env/runner abstractions ahead of full automation.
- CLI integration work is tracked in
docs/projects/aware-agent-foundation/tasks/terminal-providers/. - Real install/update/resume automation is pending provider SDK evaluations.
- Release automation is routed through the shared pipeline modules:
release-pipeline workflow trigger --workflow update-providersrefreshes manifests via GitHub Actions.- Future
sdk buildorchestration will pull in the latest provider metadata alongside CLI bundles and rule versions.
Updating Supported Versions
Run the manifest updater (requires network access):
UV_CACHE_DIR=/tmp/uv-cache \\
uv run --project libs/providers/terminal \\
python scripts/update_provider_versions.py --write --verbose
This refreshes providers/<slug>/releases.json, which in turn powers the SUPPORTED_VERSION metadata used by aware-terminal doctor/setup.
- CLI integration work is tracked in
docs/projects/aware-agent-foundation/tasks/terminal-providers/. - Real install/update/resume automation is pending provider SDK evaluations.
Metadata
Release files for aware-terminal-providers 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aware_terminal_providers-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / aware_terminal_providers-0.1.1-py3-none-any.whl
| Download URL | aware_terminal_providers-0.1.1-py3-none-any.whl |
|---|---|
| Size | 23.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d0f938657e0faff3991e1b604a594ce8fb2a66593dc81ed6ea6dc8b5edefa4f9
|
|
BLAKE2b-256 checksum How to use checksums |
d20c6d86f9a719db0a0aa5d375fbffd2b66d6e4eb24a1e2366053854a3397515
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 5, 2025.
Transparency log