Skip to content

[Bug]: spec-kit init kimi fails — kimi assets missing from v0.2.0 release #1807

@Digi-Bo

Description

@Digi-Bo

Bug Description

After installing spec-kit from the official repository, running spec-kit init kimi
fails immediately. Kimi is listed as a supported agent in the code (merged via PR #1790)
but the corresponding release assets were not included in the v0.2.0 release,
which was published one day before the merge.

Steps to Reproduce

  1. Install spec-kit from the official repo:
    uv tool install "git+https://github.com/github/spec-kit.git"

  2. Run:
    spec-kit init kimi

  3. Observe the error.

Expected Behavior

spec-kit init kimi completes successfully and scaffolds the project with Kimi Code CLI configuration files.

Actual Behavior

No matching release asset found for kimi (expected pattern: spec-kit-template-kimi-sh)

The CLI lists all available assets from v0.2.0 — none of them is kimi.
Initialization failed: 1

Specify CLI Version

0.2.0

AI Agent

Not applicable

Operating System

macOS Sequoia 15.7.3

Python Version

Python 3.14.2

Error Logs

No matching release asset found for kimi (expected pattern: spec-kit-template-kimi-sh)

Available assets in v0.2.0:
spec-kit-template-agy-ps-v0.2.0.zip
spec-kit-template-agy-sh-v0.2.0.zip
spec-kit-template-amp-ps-v0.2.0.zip
spec-kit-template-amp-sh-v0.2.0.zip
spec-kit-template-auggie-ps-v0.2.0.zip
spec-kit-template-auggie-sh-v0.2.0.zip
spec-kit-template-bob-ps-v0.2.0.zip
spec-kit-template-bob-sh-v0.2.0.zip
spec-kit-template-claude-ps-v0.2.0.zip
spec-kit-template-claude-sh-v0.2.0.zip
spec-kit-template-codebuddy-ps-v0.2.0.zip
spec-kit-template-codebuddy-sh-v0.2.0.zip
spec-kit-template-codex-ps-v0.2.0.zip
spec-kit-template-codex-sh-v0.2.0.zip
spec-kit-template-copilot-ps-v0.2.0.zip
spec-kit-template-copilot-sh-v0.2.0.zip
spec-kit-template-cursor-agent-ps-v0.2.0.zip
spec-kit-template-cursor-agent-sh-v0.2.0.zip
spec-kit-template-gemini-ps-v0.2.0.zip
spec-kit-template-gemini-sh-v0.2.0.zip
spec-kit-template-generic-ps-v0.2.0.zip
spec-kit-template-generic-sh-v0.2.0.zip
spec-kit-template-kilocode-ps-v0.2.0.zip
spec-kit-template-kilocode-sh-v0.2.0.zip
spec-kit-template-kiro-cli-ps-v0.2.0.zip
spec-kit-template-kiro-cli-sh-v0.2.0.zip
spec-kit-template-opencode-ps-v0.2.0.zip
spec-kit-template-opencode-sh-v0.2.0.zip
spec-kit-template-qodercli-ps-v0.2.0.zip
spec-kit-template-qodercli-sh-v0.2.0.zip
spec-kit-template-qwen-ps-v0.2.0.zip
spec-kit-template-qwen-sh-v0.2.0.zip
spec-kit-template-roo-ps-v0.2.0.zip
spec-kit-template-roo-sh-v0.2.0.zip
spec-kit-template-shai-ps-v0.2.0.zip
spec-kit-template-shai-sh-v0.2.0.zip
spec-kit-template-tabnine-ps-v0.2.0.zip
spec-kit-template-tabnine-sh-v0.2.0.zip
spec-kit-template-vibe-ps-v0.2.0.zip
spec-kit-template-vibe-sh-v0.2.0.zip
spec-kit-template-windsurf-ps-v0.2.0.zip
spec-kit-template-windsurf-sh-v0.2.0.zip

Initialization failed: 1

Additional Context

Root cause: PR #1790 (feat: add Kimi Code CLI agent support) was merged into main
on March 10, 2026 — one day AFTER the v0.2.0 release was published (March 9, 2026).

The release script create-release-packages.sh already includes kimi in its agent list:
ALL_AGENTS=(... kimi)

No additional code change is needed. Publishing a new patch release (v0.2.1)
would immediately resolve the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions