agentpypi 0.0.2

agentpypi — both ends of the Python distribution pipe for the AgentCulture mesh.

agentpypi

Status: v0.0.1 baseline landed. Packaging metadata, the Python package, tests, CI, and the agent-affordance verb surface are all checked in. The roadmap below describes the evolving surface; any verb listed under "Planned" is catalog-known but not yet registered as an argparse subcommand.

PyPI for the agents. agentpypi is the AgentCulture sibling that manages both ends of the Python distribution pipe:

• Online PyPI — release orchestration for AgentCulture siblings (afi-cli, cfafi, ghafi, shushu, steward, zehut, …): version checks, TestPyPI smoke installs, PyPI publishing dashboards. Uses the pypi / testpypi GitHub Environments that ghafi provisions, and the Trusted Publishing flow each sibling already wires into .github/workflows/publish.yml.
• Local PyPI — a private index running on the Culture mesh so agents can publish and pull intra-mesh wheels (pre-release builds, internal-only packages, vendored mirrors) without leaving the org's trust boundary.

Part of the AgentCulture OSS org — maintained jointly by agents and one human (Ori Nachum). Sibling to afi-cli (the agent-first CLI scaffolder this repo will be built from), ghafi (GitHub-side bootstrapper), and steward (alignment / skills supplier).

Install

uv tool install agentpypi
agentpypi --version

Python ≥ 3.12. uv tool install is the supported path — not pip install. First release lands on PyPI on merge of v0.0.1 via OIDC Trusted Publishing; until then, uv pip install -e . from a checkout works.

Surface (v0.0.1, with planned roadmap)

Every verb defaults to dry-run; --apply to commit. Every command supports --json. Exit-code policy follows the afi rubric (0 success / 1 user error / 2 env error).

# Registered (v0.0.1) — agent-affordance + localhost introspection
agentpypi learn                       # self-teaching prompt; --json supported
agentpypi explain <path>              # markdown for any noun/verb (incl. planned)
agentpypi overview                    # probe localhost: devpi:3141, pypiserver:8080
agentpypi doctor [--fix]              # same probes + diagnoses; --fix starts servers
agentpypi whoami                      # which PyPI / TestPyPI / local index am I on?

# Planned (v0.1.0) — orchestrate releases of AgentCulture siblings
agentpypi online status SIBLING       # PyPI vs CHANGELOG vs main vs latest tag
agentpypi online release SIBLING      # dry-run: would-be tag + workflow trigger
agentpypi online release SIBLING --apply

# Planned (v0.2.0) — manage the in-mesh local PyPI index
agentpypi local serve                 # run the local index (foreground)
agentpypi local upload PATH           # publish a wheel/sdist to the local index
agentpypi local mirror PACKAGE        # snapshot a public package into local
agentpypi local list                  # what's hosted locally

agentpypi explain online and agentpypi explain local resolve to status: planned entries in the explain catalog at v0.0.1; calling the verbs themselves errors with argparse's invalid choice until the respective milestone lands.

Develop

uv sync                          # install + dev deps
uv run pytest -n auto -v         # tests
uv run agentpypi --version       # smoke
uv run pre-commit install        # enable lint hooks

Quality pipeline mirrors the rest of the AgentCulture mesh: black, isort, flake8 (+ flake8-bandit, flake8-bugbear), pylint, bandit, markdownlint-cli2. CI runs on every PR + push to main.

Trusted Publishing

Once pyproject.toml lands, ghafi provisions the pypi / testpypi GitHub Environments and .github/workflows/publish.yml follows the same OIDC Trusted Publishing pattern every sibling uses — no secrets in the repo.

License

MIT. © 2026 Ori Nachum / AgentCulture.

— Claude