Skip to content

Releases: Kirchlive/kimi-code-mods

Release list

kimi-code-mods 1.00.0

kimi-code-mods 1.00.0 Latest
Latest

Choose a tag to compare

View all tags
@Kirchlive Kirchlive released this 22 Aug 10:54
v1.00.0
84bc9f5

First tagged release. Patch your Kimi Code install from a terminal menu, and put it back whenever you like.

Install

curl -fsSL https://raw.githubusercontent.com/Kirchlive/kimi-code-mods/main/install.sh | bash
kimi-code-mods

Windows installs into WSL:

iwr -useb https://raw.githubusercontent.com/Kirchlive/kimi-code-mods/main/install.ps1 | iex

The installer fetches the repository and links the kimi-code-mods command. It touches no Kimi installation — patching happens when you choose Apply in the menu. The source archives below work too, but the installer is the path that keeps updating to a git pull.

What is in it

Verified against Kimi Code 0.38.0. 17 patches, 25 settings, 132 system prompt overrides, 29 tests.

  • Behaviour — reasoning effort per turn, the tool catalogue, transcript window, subagent models, hooks on any of Kimi's 20 events, loop control, skills, AGENTS.md alternatives, and ten switches under Misc.
  • Look — two spinners settable apart from each other, rotating thinking verbs, message marker/frame/weight, a 19-token palette editor with live preview, and a welcome banner with horns.
  • Prompts — all 132 system prompts extracted as Markdown. Edit one, it replaces the original on the next run. A prompt whose anchor moved is reported and skipped, never guessed at.
  • Fullscreen renderer — patched into the binary, so it holds however Kimi is started rather than only through a launcher.

Undoing it

Every run starts from a pristine copy of your Kimi binary, frozen on first use. Patches never stack, and restoring is a file copy:

kimi-code-mods              # menu -> Restore Original Kimi Code
kimi-patch.sh --restore

Worth knowing

macOS only for patching — it reads a Mach-O header and re-signs with codesign. On Linux and WSL the menu runs but Apply refuses. Re-signing is ad-hoc, so the hardened runtime and notarisation are gone from the patched binary; that is inherent to modifying a signed application. A Kimi auto-update replaces the binary and removes every patch — your settings survive, run Apply again.

Assets 2
Loading