pl8-cli

Agent-friendly command line for PL8, a lightweight issue tracker backed by DynamoDB. It invokes the pl8-interface Lambda from pl8-services through the Lambda Invoke API, authenticated with your AWS credentials. PL8 has no UI; this is how people and agents use it.

Getting started

Run it without installing, with uv:

uvx pl8-cli --env dev space list

or install the shorter pl8 command:

uv tool install pl8-cli
pl8 --env dev space list

To run an unreleased revision, point uvx at the repo: uvx --from git+https://github.com/dchenstealth/pl8-cli pl8 ....

Configuration

Flags beat environment variables, and a function name beats an env. Connection flags may go before or after the command.

Your credentials need lambda:InvokeFunction on the function. pl8-services tags it Type=PL8Interface for granting that; the grant itself is managed outside these repos. aws login sessions work.

Output contract

Every command prints exactly one JSON document on stdout, pl8-interface's response envelope:

{"ok": true, "data": {"issue_id": "abc123", "status": "TODO", ...}}
{"ok": false, "error": {"type": "DDBStillBlockedError", "message": "..."}}

Failures on the CLI side use the same shape. --pretty indents it. The exit status says what kind of failure it was:

Writes are never retried automatically, since a write that timed out may already have been applied. Reads are retried on transient errors.

See pl8-interface's contract and pl8-base's errors for what each DDB* error means.

Commands

Every command has --help, which spells out the rules it enforces.

pl8 space create SPACE_ID --name NAME --description TEXT
pl8 space get SPACE_ID
pl8 space list
pl8 space update SPACE_ID --name NAME --description TEXT [--if-version N]
pl8 space delete SPACE_ID

pl8 issue create --title TITLE --description TEXT [--status STATUS]
pl8 issue get ISSUE
pl8 issue list --status STATUS
pl8 issue update ISSUE --title TITLE --description TEXT [--if-version N]
pl8 issue transition ISSUE --status STATUS [--if-version N]
pl8 issue delete ISSUE

pl8 blocker add --blocking ISSUE --blocked ISSUE
pl8 blocker remove --blocking ISSUE --blocked ISSUE
pl8 blocker list (--blocked ISSUE | --blocking ISSUE)

pl8 invoke OPERATION [--params JSON | --params-file PATH]

• Spaces must exist before you create Issues in them, and must have no Issues left before you delete them.
• Issues are named SPACE/ISSUE_ID, e.g. ENG/abc123. A bare ISSUE_ID takes its space from --space or PL8_SPACE; a space in the reference always wins, so cross-space blockers need nothing extra.
• Descriptions can come from a file with --description-file PATH, or from stdin with --description-file -, which avoids shell quoting.
• Lists return {"items": [...], "cursor": ...}. Pass --cursor back for the next page, set the page size with --limit (1-100), or use --all to fetch every page at once.
• Updates replace both fields. --if-version N makes the write fail with DDBVersionConflictError if the item changed since you read version N.
• invoke sends any operation and params unchanged, for operations that don't have a subcommand yet.

Example

export PL8_ENV=dev PL8_SPACE=ENG

id=$(pl8 issue create --title "Fix login" --description-file notes.md | jq -r .data.issue_id)
pl8 blocker add --blocking OPS/k8s123 --blocked "$id"
pl8 issue list --status BLOCKED --all

An Issue that gains a blocker moves to BLOCKED. It returns to TODO in the background once every Issue blocking it is DONE or deleted, or its blockers are removed.

Development

uv sync
uv run ruff check .
uv run pytest

tests/test_contract.py checks every subcommand against a pinned copy of pl8-interface's operations.yaml; see tests/contract/README.md to refresh it.

Releases publish to PyPI when a vX.Y.Z tag matching pyproject.toml's version is pushed.