Skip to main content

tai42-cli

License: Apache 2.0

The tai command-line client for operating a tai42 server over its HTTP API. It ships the tai console script: thin, typed clients over the server's /api/* surface — the same routes the Studio calls — for tools, presets, agents, extensions, connectors, hooks, channels, storage, keys, scopes, roles, configuration, and the rest of the operator surface. Human-readable tables by default; raw JSON under --json for scripting. Typed package (py.typed).

Position in the ecosystem

TAI is an open-source runtime for MCP tools, agents, and workflows. tai42-cli is the terminal client half of the tai command: it talks to a running server over HTTP and depends only on the interface contract, so it installs and runs on its own without the server package.

tai42-contract  <--  tai42-cli
(interfaces)      (the remote client)

Installing the server package adds its own local and runtime commands (serve, db, doctor, catalog, openapi, backend, metrics, offline config/manifest validation) to the same tai command through an entry-point group, so one binary covers both remote and local operation when both are installed.

Install

Requires Python 3.13+. Install from PyPI:

uv add tai42-cli

Or as a standalone tool:

uv tool install tai42-cli

Usage

Point the client at a server and authenticate. The server URL resolves from the --server flag, then TAI_SERVER_URL, then ~/.config/tai/config.toml, then a local default. The API key resolves from --api-key-stdin, then TAI_API_KEY, then the config file, then an interactive prompt (there is deliberately no --api-key VALUE flag — a value on the command line leaks through ps and shell history). The HTTP read window resolves from --timeout SECONDS, then TAI_CLI_TIMEOUT_SECONDS, then a 120s default sized for fleet-broadcast config writes; values must be positive and finite.

export TAI_SERVER_URL=https://your-server.example
export TAI_API_KEY=sk-...

tai tools list
tai tools list --json
tai config env get
tai version

Install shell completion:

tai completion install bash > /etc/bash_completion.d/tai

Development

uv venv --python 3.13
uv pip install --no-sources --editable ".[dev]"
uv run --no-sync ruff check .
uv run --no-sync ruff format --check .
uv run --no-sync pyright
uv run --no-sync pytest --cov --cov-report=term-missing

Documentation

The whole platform — concepts, guides, and the generated reference — lives in the unified documentation site:

License

Apache-2.0. See LICENSE and NOTICE.

Metadata

Release files for tai42-cli 17.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tai42-cli 17.0.0
File Size Uploaded Provenance Actions
tai42_cli-17.0.0.tar.gz 118.3 kB Without provenance Details for tai42_cli-17.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tai42-cli 17.0.0
File Interpreter ABI Platform Actions
tai42_cli-17.0.0-py3-none-any.whl Python 3 none any Details for tai42_cli-17.0.0-py3-none-any.whl

Total release size: 275.8 kB

Release files / tai42_cli-17.0.0.tar.gz

Download URL tai42_cli-17.0.0.tar.gz
Size 118.3 kB
Tags Source
SHA-256 checksum
How to use checksums
5a01951a5d3ae21a269b1848d966f3414b759b5508e3fe1673472887e976b0fe
BLAKE2b-256 checksum
How to use checksums
015be7ab7b2ca01723e5914305df42b74e7df14a0769ef96ceef3bb9be59c3c4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / tai42_cli-17.0.0-py3-none-any.whl

Download URL tai42_cli-17.0.0-py3-none-any.whl
Size 157.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5c6245edbf8402058b92a83d733985373b7d7914a156794e28c1d652e2995a6f
BLAKE2b-256 checksum
How to use checksums
5e9a1e08bfcd2513e8dbef34b5a1e85e5a67b04cfa873654bc9889bc3e296a3f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Security for tai42-cli 17.0.0

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

17.0.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page