Skip to main content

Standalone Agent Execution Graph — migration notice

Version: aac-aeg 0.1.1.

Use aac-cli for new installations and upgrades. The publicly released aac-cli 0.2.4 supplies both aac and aeg in one installation. This is the final migration-notice release of the standalone aac-aeg package. Its legacy renderer, aac-aeg command and optional online extra retain their existing behavior; there is no ongoing standalone renderer release stream.

Read the AEG guide and command reference for current usage, profiles and migration instructions.

Move to the supported commands

For pip, activate the Python environment you intend to keep, then install or upgrade the owning CLI and verify both commands:

python -m pip install --upgrade aac-cli
aac --version
aeg --version

Change saved scripts from aac-aeg to aeg. Once the new commands work, remove aac-aeg only from the environment where you previously installed it:

python -m pip uninstall aac-aeg

For separate pipx installations, inspect pipx list. Use pipx install aac-cli for a new CLI environment or pipx upgrade aac-cli for an existing one. Verify aac --version and aeg --version, then use pipx uninstall aac-aeg only if that is the legacy environment you intend to remove. Removing a legacy aac-aeg[online] environment does not upgrade a different CLI environment.

Keep your AAC CLI home (~/.aac by default or AAC_CLI_HOME), profiles, credentials, agent folders, retained evidence and generated graphs. Package migration does not require deleting that material or unrelated environments.

The owning CLI uses your selected profile and existing tenant API key for online queries. Offline graph rendering and local listing need no login. Neither this migration nor installation creates a tenant or uploads your local evidence.

Legacy compatibility and retention

The standalone package alone owns aac-aeg; aac-cli owns aac and aeg. They can coexist without overlapping renderer or command files. Removing the legacy package leaves the owning CLI's commands intact. If your shell still finds an older command, inspect command -v aac and command -v aeg, refresh its command cache where supported, and select the environment you upgraded.

Historical release files and this project name will be retained when the project is archived. Archival does not prevent downloads or make an existing pinned installation stop working. New CLI installations do not depend on this standalone project.

License

Apache-2.0. Existing dependency notices remain included.

Release files for aac-aeg 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aac-aeg 0.1.1
File Size Uploaded
aac_aeg-0.1.1.tar.gz 66.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aac-aeg 0.1.1
File Interpreter ABI Platform
aac_aeg-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 136.9 kB

Release files / aac_aeg-0.1.1.tar.gz

Download URL aac_aeg-0.1.1.tar.gz
Size 66.0 kB
Tags Source
SHA-256 checksum
How to use checksums
8c8018a815d026ca53f6d94d96ab65fd9e54b304fcbae7670f7813d31d436824
BLAKE2b-256 checksum
How to use checksums
2aef6345c7d62903e7ffb072a30edcf51f97a6ad4cc9b084833a7b753164844a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release files / aac_aeg-0.1.1-py3-none-any.whl

Download URL aac_aeg-0.1.1-py3-none-any.whl
Size 70.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9fdebd96e3eea4437a79e1d04f05d28a6cda285d3f688d66ac6ccc9b03509ba2
BLAKE2b-256 checksum
How to use checksums
bf1212a01f1a01c42aa1f87cb4a7a5f7c94b33c157d664fd81e44095bd749944
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page