cytario-cli
CLI for working with Cytario storage connections as the signed-in user — designed for AI agents and analysts who need to work with connection data using the workstation's standard AWS tooling.
What it does
cytario auth login --host <url>— browser sign-in (OAuth 2.0 Authorization Code + PKCE against the deployment's identity service; a loopback redirect receives the result). The refresh grant is stored user-private (~/.config/cytario/cli,0600).cytario connections list [--json]— the connections visible to you, with the storage role and access level your grant resolves to.cytario connections setup [--all | <name>]— writes one AWS CLI profile per connection into~/.aws/config([profile cytario-<name>]) withweb_identity_token_file, soaws/ boto3 / pandas performAssumeRoleWithWebIdentitythemselves — with exactly your grant's authorization, never wider.cytario auth token/cytario auth refresh— a fresh ID token on stdout, and a rewrite of all managed token files (tokens live ~1 hour).
Agents: see skills/cytario-cli.md for the
tool-neutral agent workflow shipped with this repo.
Install
uv tool install cytario-cli # or: pip install cytario-cli
Python ≥ 3.10. The CLI is a public OIDC client — no secrets are shipped or stored beyond your own refresh grant.
Usage
cytario auth login --host https://app.cytario.com
cytario connections list
cytario connections setup --all
aws s3 ls --profile cytario-mybucket
Host resolution order: --host, then CYTARIO_HOST, then the last
signed-in host.
Security model
- Your authorization is exactly your Cytario grant on each connection
(
read-only/annotate/read-write/admin); bucket sharing stays confined to the web app. - No long-lived AWS keys are written; the AWS CLI federates per operation from the token file, and the CLI refreshes tokens before expiry.
- Revocation: revoking the CLI session in the identity service (or removing your group membership) ends the CLI's access within one token lifetime.
Development
uv sync
uv run ruff format --check && uv run ruff check
uv run pytest
Releases are cut by python-semantic-release on Conventional Commits and published to PyPI via trusted publishing.
License
MIT — see LICENSE.
Metadata
Release files for cytario-cli 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cytario_cli-1.0.0.tar.gz | 76.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cytario_cli-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 89.4 kB
Release files / cytario_cli-1.0.0.tar.gz
| Download URL | cytario_cli-1.0.0.tar.gz |
|---|---|
| Size | 76.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82cc91d707e41db39ac19fd191900b8ec03150f04cfb9c35fa976ce34d7263fe
|
|
BLAKE2b-256 checksum How to use checksums |
a3a74a83acff0b92ee9ac0a25318d466fd32a85c5ad23f14edb7ca124ad119fa
|
| 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 14, 2026.
Transparency logRelease files / cytario_cli-1.0.0-py3-none-any.whl
| Download URL | cytario_cli-1.0.0-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
402f7db0e22fc4fdd14f1d404db4deb7f4e55b67b9250098d44bd740c38baf64
|
|
BLAKE2b-256 checksum How to use checksums |
9e725f65fccb5c21d26a8b09b02321063ef981867c723d5e86d6a68dad69d601
|
| 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 14, 2026.
Transparency log