Autotune Python SDK
Typed synchronous and asynchronous interfaces for the autotune command-line tool. The CLI remains the execution engine and the authority for option validation.
Requirements
- Python 3.10 or newer
- Node.js 22 or newer
- An
autotuneexecutable onPATH
Select another executable with binary=..., AUTOTUNE_CLI_BIN, or AUTOTUNE_BIN.
Usage
from autotune_cli import Autotune
autotune = Autotune()
space = autotune.analyze("train.py", agent="codex")
result = autotune.run("train.py", trials=20, yes=True, agent="codex")
print(result.best_trial)
run() is intentionally noninteractive: pass yes=True, or provide config="search-space.yaml". A configured run is automatically passed to the CLI with --yes.
Use invoke() for raw CLI features:
print(autotune.invoke(["--help"]).stdout)
The async client has the same API:
from autotune_cli import AsyncAutotune
result = await AsyncAutotune().run("train.py", trials=20, yes=True)
1 maintainer
Metadata
1 maintainer
Release files for autotune-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 | Provenance | Actions |
|---|---|---|---|---|
| autotune_cli-0.3.1.tar.gz | 26.4 kB | With provenance | Details for autotune_cli-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| autotune_cli-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for autotune_cli-0.3.1-py3-none-any.whl |
Total release size: 51.3 kB
Release files / autotune_cli-0.3.1.tar.gz
| Download URL | autotune_cli-0.3.1.tar.gz |
|---|---|
| Size | 26.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b7fc46428c860fa9b3fff9685ce22f1f9b345a4f8de68fe56c8c9b3d666d349
|
|
BLAKE2b-256 checksum How to use checksums |
71fdbd7f47b614176a75264b4b11c912fb49e480ec04b841c6a515baeab42fb5
|
| 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 Aug 2, 2026.
Transparency logRelease files / autotune_cli-0.3.1-py3-none-any.whl
| Download URL | autotune_cli-0.3.1-py3-none-any.whl |
|---|---|
| Size | 25.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f0d63fcb05055e1d4a2accf73b96c4e3b6c1b6109ee2a97184079449341c0d0d
|
|
BLAKE2b-256 checksum How to use checksums |
ec91899b49524ff3c77462fd7cfe32a05329811117f7171bae9b223d9bc04097
|
| 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 Aug 2, 2026.
Transparency logSecurity for autotune-cli 0.3.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for autotune_cli-0.3.1.tar.gz
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 Aug 2, 2026.
Transparency logA 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.
