The versions you are running

The version number disagrees with itself: the distribution is 4.1.0, but the packages inside report 3.2.2 and other numbers, so you trust the one the package manager recorded.

Last updated: 14 Oct, 2026 · Agent Governance Toolkit 4.1.0

The toolkit was assembled from several older packages that kept their own version strings. The result is that the same install answers the question what version is this with different numbers depending on who you ask. Knowing which to believe stops you chasing a bug in the wrong release.

Reading the version four ways

The distribution metadata, set by the package manager, says 4.1.0. The import packages carry their own __version__, left over from before they were merged.

import importlib.metadata as meta
import agent_os, agentmesh, agent_sandbox

# the package manager records the real, installed version
print("distribution :", meta.version("agent-governance-toolkit"))

# each inner package kept its own, older string
print("agent_os     :", agent_os.__version__)
print("agentmesh     :", agentmesh.__version__)
print("agent_sandbox:", agent_sandbox.__version__)

distribution : 4.1.0
agent_os     : 3.2.2
agentmesh     : 3.6.0
agent_sandbox: 0.0.0

The command line disagrees with itself too

The agt command reads the distribution metadata and reports 4.1.0. Its own verify subcommand reads agent_os.__version__ and prints 3.2.2. Same tool, same install, two numbers.

$ agt --version
agt, version 4.1.0

Which number to trust

• Trust importlib.metadata.version. It reads what the package manager recorded at install time, which is 4.1.0.
• Ignore the inner __version__ strings. They were never updated when the packages were merged, so 3.2.2 and 0.0.0 describe code that no longer ships under those numbers.
• The deprecation warning points nowhere useful. It tells you to switch to agent-governance-toolkit-core, which you already installed; the new layer ships no new import name, so there is nothing to change.

Where the version shows up

When the version matters

• Filing a bug, where naming 4.1.0 rather than 3.2.2 points the maintainers at the right code.
• Pinning a dependency, where only the distribution version is a real, installable number.
• Reading another tutorial, to tell whether it describes the 4.x install or an older package.

Related

• Previous: What installing gives you
• Next: One choke point for every tool call