Automic VaultAutomic Vault

brew

kimi-cli mit Homebrew, scoop, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für kimi-cli in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install kimi-cli

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install main/kimi-cli

Scoop official bucket manifest trees · bucket/kimi-cli.json · Quelle: api.github.com

Windows Package Managerverifiziert · 92%
winget install --id MoonshotAI.KimiCLI -e

Windows Package Manager source index · MoonshotAI.KimiCLI · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

CLI agent for MoonshotAI Kimi platform

Befehle und Aliase

  • kimi
  • kimi-cli

Verlauf

Projektgeschichte und Nutzung

Kimi CLI is MoonshotAI's terminal AI agent for software-development and shell workflows. Its README describes an agent that can edit code, execute commands, fetch web pages, plan, and adjust actions from terminal feedback.

Projektgeschichte

Kimi CLI was the earlier MoonshotAI terminal-agent package around the Kimi platform. The repository includes Python package structure, docs, examples, SDK material, tests, and release automation, showing a full CLI product rather than a thin API wrapper.

In 2026 the project began a transition to Kimi Code CLI. The README states that Kimi CLI is evolving into Kimi Code CLI, that installing Kimi Code CLI migrates configuration and sessions, and that the Kimi CLI project will be gradually wound down while docs and existing installations remain available.

Adoptionsgeschichte

Kimi CLI accumulated a visible developer audience on GitHub and was packaged for Homebrew in this batch. Its official README also documents integrations with VS Code, Agent Client Protocol-compatible editors, Zsh, and MCP servers, placing it in the 2025-2026 wave of terminal AI agent tooling.

The companion kimi-agent-rs repository describes a Rust rewrite of the Python kimi-cli runtime that must preserve wire protocol, message formats, ~/.kimi data layout, tool schemas, and externally observable behavior, which is a strong signal that Kimi CLI had become a compatibility target inside MoonshotAI's agent tooling.

Wie es verwendet wird

Users run Kimi CLI as an interactive terminal agent, authenticate with /login, connect MCP servers, and use it either directly in a terminal or as an ACP agent server for editors such as Zed or JetBrains IDEs.

Its configuration and credential paths matter to package users because Kimi Code CLI migration preserves that state rather than treating the successor as a clean-room replacement.

Warum Paket-Nerds sich dafür interessieren

Kimi CLI is interesting as a transition package: it represents the Python-era MoonshotAI terminal agent and the compatibility surface that newer runtimes and successor CLIs had to carry forward.

For package managers, the useful bit is not only the binary name but the state layout under ~/.kimi, because that is what determines whether upgrades and successor packages can avoid breaking developer sessions.

Zeitleiste

  • 2026: Kimi CLI release 1.46.0 included docs announcing the evolution to the Kimi Code successor project.
  • 2026: Kimi CLI release 1.47.0, released on 2026-06-05, renamed project docs to Kimi CLI and guided users to upgrade to Kimi Code.
  • 2026: Kimi CLI release 1.48.0 assets were published on 2026-06-22.

Related projects

  • Kimi Code CLI is the successor project named by the Kimi CLI README.
  • kimi-agent-rs is the Rust rewrite that preserves Kimi CLI compatibility.
  • Agent Client Protocol, MCP, Zsh integration, and the Kimi Code VS Code extension are adjacent integration surfaces documented by the project.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für kimi-cli wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 8 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 3 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
~/.kimi/config.toml~/.kimi/mcp.json

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.kimi/config.toml~/.kimi/credentials/<provider>.json~/.kimi/mcp-oauth/

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
kimicliglobales Executable
kimi-clicliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version1.48.0
Manager aktualisiert2026-07-17
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://moonshotai.github.io/kimi-cli/

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:kimi-cli
Version1.48.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/kimi-cli
Homepagehttps://moonshotai.github.io/kimi-cli/
Repositoryhttps://github.com/MoonshotAI/kimi-cli
Upstream-Dokumentationhttps://github.com/MoonshotAI/kimi-cli#readme
LizenzApache-2.0
Quellarchivhttps://files.pythonhosted.org/packages/e9/a9/3d25e80362abb7345a5dd05dc47cdcdc627e8d810d027943cc4647dcdb03/kimi_cli-1.48.0.tar.gz
Zuletzt aktualisiert2026-07-17T21:17:35+08:00
Pulseupdated
Abhängigkeitencertifi, cryptography, libyaml, pillow, pydantic, python@3.14, re2, rpds-py
Build-Abhängigkeitenpkgconf, pybind11, rust
Von macOS bereitgestellte Bibliothekenlibffi, libxml2, libxslt
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namekimi-cli
Version Scheme0
Revision1
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Scoop95%

main/kimi-cli

scoop install main/kimi-cli
  • normalized package name match
  • Abgeglichen nach: Kimi Cli
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/kimi-cli.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
winget95%

MoonshotAI.KimiCLI

winget install --id MoonshotAI.KimiCLI -e
  • normalized package name match
  • Abgeglichen nach: Kimi Cli
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: MoonshotAI.KimiCLI from https://cdn.winget.microsoft.com/cache/source.msix
winget92%

MoonshotAI.Kimi

winget install --id MoonshotAI.Kimi -e
  • installed executable or alias match
  • Abgeglichen nach: Kimi
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: MoonshotAI.Kimi from https://cdn.winget.microsoft.com/cache/source.msix

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment