graph-agents-cli
Build, evaluate and deploy LangGraph agents on your own Kubernetes, with one CLI and six skills for your coding agent.
Get started · Guides · Reference · Changelog
What you get
- A LangGraph service, ready to run: a streaming chat API, threads, an A2A endpoint, answers in a JSON shape you declare when a program reads them, and shared-key, OIDC/JWT or custom authentication on every route.
- Outbound calls under a policy:
api-policy.yamldeclares the APIs tools may call, the agent refuses anything else,lintchecks it in CI, and chosen calls wait for a human approval. - Agents that ask other agents:
peer adddeclares the agents one asks over A2A, each agent knows the user and the agent in between, a person's approvals stay with that person, andsystemchecks, wires and deploys several projects as one. - An eval gate CI can enforce: deterministic checks and model judges, with an exit code that is the gate and a deterministic fake model for keyless runs.
- Deploys to any cluster: a hardened Helm chart,
deploystraight from your machine or through GitHub Actions or Argo CD, andsecretsfor the app's Secret. - Works with your coding agent: skills teach Claude Code, Codex, Gemini CLI, Cursor, Antigravity and others the same lifecycle.
Nothing is specific to one domain or one consumer: a project picks its auth policy, declares its APIs and configures the rest through environment variables and chart values.
Install
You need Python 3.12 or 3.13 and uv.
Deploying also needs helm, kubectl, git and a docker that builds with BuildKit.
uv tool install graph-agents-cli
graph-agents-cli setup # optional: install the skills into your coding agents
pipx install graph-agents-cli or pip install graph-agents-cli (into a virtual
environment) work too. To install a release tag from GitHub instead:
uv tool install git+https://github.com/ss7172/graph-agents-cli@v0.3.1
More options (extras, mirrors, disconnected installs): Installation & setup.
Quick start
Run a new agent locally. The fake model needs no key; for a real one, leave out the
export line and login --write-env asks for OPENAI_API_KEY.
graph-agents-cli create my-agent && cd my-agent
cp .env.example .env
export MODEL_PROVIDER=fake # the keyless, deterministic test model
graph-agents-cli login --write-env # checks the setup, generates API_KEY
graph-agents-cli install
graph-agents-cli run "What's the weather in San Francisco?"
graph-agents-cli eval run # the exit code is the gate
Or ask your coding agent to "use graph-agents-cli to build ..." once setup has installed
the skills. The Quickstart
walks through each step and switches to a real provider.
Documentation
The documentation site is built with MkDocs
Material from website/.
| Section | Pages |
|---|---|
| Get started | Installation & setup · Quickstart · Tutorial: build with a coding agent · Tutorial: manual workflow · The lifecycle |
| Build | Develop your agent · Authentication · Outbound API policy · Human approval · Agents calling agents · Evaluation · Extensions |
| Operate | Deploy to Kubernetes · CI/CD · Secrets · Observability · Upgrading projects · Offline profile · Security & production |
| Reference | CLI · Environment variables · HTTP API · api-policy.yaml · graph-agents-system.yaml · Project manifest · Exit codes · Skills · Compared with google-agents-cli |
To preview the site from a checkout, for example while editing it:
uv run --group docs mkdocs serve -f website/mkdocs.yml # http://127.0.0.1:8200
On the command line, graph-agents-cli <command> --help prints the same reference as the
site's CLI page.
Status
Version 0.3.1, alpha (release notes). Interfaces may still change between minor versions; the changelog lists every breaking change with its migration steps. Released on PyPI and as tags on GitHub.
- Known issues: parked issues, each with its impact and workaround.
- Changelog: every release and its migration steps.
- Contributing: development setup, tests, templates, releases and the upstream-sync process.
License
Apache-2.0: see LICENSE. graph-agents-cli is a fork of google-agents-cli with the Google Cloud specific parts removed; NOTICE lists the attribution and the modifications.
Metadata
Release files for graph-agents-cli 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| graph_agents_cli-0.3.1.tar.gz | 1.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| graph_agents_cli-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.3 MB
Release files / graph_agents_cli-0.3.1.tar.gz
| Download URL | graph_agents_cli-0.3.1.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
211a48834b167d3bee2d8b78dbb78d276a8104638e7c63a13c0207dabc869287
|
|
BLAKE2b-256 checksum How to use checksums |
65513565d8698008baeb1999cb6438018f0764d08f8480fa99044cb9890d243a
|
| 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 29, 2026.
Transparency logRelease files / graph_agents_cli-0.3.1-py3-none-any.whl
| Download URL | graph_agents_cli-0.3.1-py3-none-any.whl |
|---|---|
| Size | 1.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0256c66c59d98e0e5fa056f2dfb7ef7cf5c1d24ac4b2fa62602b04e2e59e463f
|
|
BLAKE2b-256 checksum How to use checksums |
9cf360f55e070d65af9db2fd09e665beac5e5f2e2329b3ba761b8a7bfbf230bc
|
| 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 29, 2026.
Transparency log