Skip to content

fix(cli): rename kai console script to kaievolve (stop shadowing kai-agent)#34

Merged
aktasbatuhan merged 1 commit into
mainfrom
chore/cli-rename-kai-to-kaievolve
Jun 15, 2026
Merged

fix(cli): rename kai console script to kaievolve (stop shadowing kai-agent)#34
aktasbatuhan merged 1 commit into
mainfrom
chore/cli-rename-kai-to-kaievolve

Conversation

@aktasbatuhan

Copy link
Copy Markdown
Member

Problem

This package registers a kai console script (kai = kaievolve.cli:cli_main). kai-agent also registers kai for its CLI. With both installed, whoever is installed last owns ~/.local/bin/kai — so typing kai can launch the KaiEvolve TUI instead of the agent (observed in the wild).

Fix

Rename the TUI entry point to kaievolve (the runner stays kaievolve-run):

[project.scripts]
kaievolve = "kaievolve.cli:cli_main"
kaievolve-run = "kaievolve.cli:main"

Now kai unambiguously belongs to kai-agent, and the evolve TUI is kaievolve — order-independent, no more PATH collision.

Note

Existing installs keep the stale kai script until reinstalled (pip install -e . refreshes entry points).

🤖 Generated with Claude Code

…kai-agent)

kai-agent registers the `kai` console script for its CLI. Registering `kai`
here too means whichever package is installed last owns `~/.local/bin/kai`, so
on a machine with both, typing `kai` could launch this evolve TUI instead of
the agent. Rename the TUI entry to `kaievolve` (the runner stays
`kaievolve-run`) so `kai` unambiguously belongs to kai-agent.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@aktasbatuhan aktasbatuhan merged commit 57edde8 into main Jun 15, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant