takopi-engine-kimi
Kimi CLI engine plugin for Takopi.
Installation
With pip
pip install takopi-engine-kimi
With uv (in a project)
# Add to your project's dependencies
uv add takopi takopi-engine-kimi
# Or from git (before it's published)
uv add takopi git+https://github.com/z80dev/takopi-engine-kimi
# Or from local path during development
uv add takopi /path/to/takopi-engine-kimi
With uv (as a tool)
# Install takopi with the kimi plugin
uv tool install takopi --with takopi-engine-kimi
# Or from git
uv tool install takopi --with git+https://github.com/z80dev/takopi-engine-kimi
# Or upgrade an existing installation
uv tool upgrade takopi --with takopi-engine-kimi
With uv tool run (temporary)
# Run takopi with kimi support without installing
uv tool run --with takopi-engine-kimi --from takopi takopi
Usage
Once installed, the kimi engine is automatically available. The plugin defaults to:
- Model:
kimi-for-coding(Kimi's coding-optimized model)
Minimal configuration in takopi.toml:
[engines.kimi]
# Uses "kimi-for-coding" by default
Enable auto-approval (yolo mode):
[engines.kimi]
yolo = true # Auto-approve all actions
Full configuration options:
[engines.kimi]
model = "kimi-for-coding" # Or "kimi-k2", etc.
allowed_tools = ["Bash", "Read", "Edit", "Write"]
yolo = true # Auto-approve all actions
Verification
Verify the plugin is installed:
# Check available engines
uv run python -c "from takopi.engines import list_backend_ids; print(list_backend_ids())"
# ['claude', 'codex', 'kimi', 'opencode', 'pi']
Configuration Options
| Option | Type | Default | Description |
|---|---|---|---|
model |
string | kimi-for-coding |
Kimi model to use |
allowed_tools |
list[string] | ["Bash", "Read", "Edit", "Write"] |
Tools to allow |
yolo |
boolean | false |
Auto-approve all actions (Kimi's --yolo flag) |
use_api_billing |
boolean | false |
Use API billing mode |
Requirements
- Python >= 3.14
- Takopi >= 0.22.0
- Kimi CLI installed
License
MIT
Metadata
Release files for takopi-engine-kimi 0.1.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 | Provenance | |
|---|---|---|---|---|
| takopi_engine_kimi-0.1.0.tar.gz | 43.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| takopi_engine_kimi-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.4 kB
Release files / takopi_engine_kimi-0.1.0.tar.gz
| Download URL | takopi_engine_kimi-0.1.0.tar.gz |
|---|---|
| Size | 43.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d632717c578809cf4958b7d2b2ed08701a756a5631b9ca066793e432b384a98
|
|
BLAKE2b-256 checksum How to use checksums |
32bd2d868671ae9283596d24cb509361b1c0cb9c883559229bb7c13f18ab0130
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / takopi_engine_kimi-0.1.0-py3-none-any.whl
| Download URL | takopi_engine_kimi-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c50fbc0cc326cadec1c57b408363f30ed8314b3bef0b9d9995a82e67bc456631
|
|
BLAKE2b-256 checksum How to use checksums |
62676eb1670cc68d49f44e06475bd886aa64dc8a6774728641727902a44b3de6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for takopi-engine-kimi 0.1.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.