AWARE Terminal Experience
Boot once, come back to the exact workspace every time. AWARE Terminal stitches together tmux, GNOME, and AI providers so threads in Studio or aware-cli reopen with all panes running—no manual tab herding.
Everyday Flow
-
One-time bootstrap
uv run aware-terminal setup --autoinstalls tmux + plugins, enables the user systemd service, and applies the GNOME Auto Move Windows rules. If providers (Codex, Claude, Gemini) are available, setup auto-installs them too—doctor shows confirmations and remediation hints. Prefer to approve provider installs manually? Append--provider-policy skipand the guided flow will prompt before updating each agent.Provider manifests refresh automatically when you run setup from the repo. In packaged builds we reuse the bundled manifest data; a banner will tell you whether a refresh happened or if the bundled versions are in use. Provider prompts highlight installed vs latest versions (
codex-cli 0.48.0 → 0.49.0) with release notes so you can upgrade confidently. -
Thread-scoped terminals
aware-cli object call --type terminal --function create --id <thread> ...spins up a tmux window tied to a thread. Descriptors land in.aware/threads/<thread>/terminals/<id>.json, so Studio or Control Center can render panels instantly, andterminal attachreopens the shell without re-running commands. -
Daemons that persist
Terminal sessions survive reboots: the tmux service starts on login,aware_terminal.runtimerestores panes, and Studio/CLI poll the manifest to reconnect. Providers launch in the same window, so agent runs (Codex/Claude/Gemini) share the thread history. -
Control Center (optional)
uv run aware-terminal controlopens the TUI overlay for live streaming; it reads the same manifests as Studio, so actions stay in sync. We’re refining this view to match the new lifecycle (thread → terminal → optional provider).
Why it matters
- Zero setup drift: once auto-configured, every terminal reappears on the right workspace with the same panes; no manual tmux scripts or window moves.
- Provider-ready: AI launchers inherit thread context—
ensure_provider_sessionplugs Codex, Claude, or Gemini into the same tmux session used for human work. - CLI ↔ Studio parity: descriptors + pane manifests give both aware-cli and Studio the same contract, letting us bundle a consistent open-source experience (aware-cli + aware-terminal + providers + rules/release helpers).
Looking ahead: provider binding (terminal bind-provider) and Control Center updates will round out the Studio integration. For install specifics and release bundling guidance, see tools/terminal/RELEASE.md.
Metadata
Release files for aware-terminal 0.3.3
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-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / aware_terminal-0.3.3-py3-none-any.whl
| Download URL | aware_terminal-0.3.3-py3-none-any.whl |
|---|---|
| Size | 108.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
167138a7fde29b8ddfe67768cdd98033f79ccb3e57de4f2ce960ac76f5d23238
|
|
BLAKE2b-256 checksum How to use checksums |
93a06dde50be024dad28f65cdf97f027d5024428a734e56368ed7702b6730b86
|
| 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