Release v2.0.3 · kenryu42/cc-safety-net

Amp personal-scope install. install --amp now publishes the plugin to
your Amp Personal Plugins repository, so the safety net follows your account
to every machine — including remote Orb threads — instead of living in one
local config.
Native Kimi Code plugin. The release now ships kimi.plugin.json, so you
can install via /plugins install and let Kimi Code manage enable, disable,
update, and removal. The installer offers a choice between the global hook
and the native plugin when you select Kimi Code.

install --amp embeds a snapshot of your user policy in the published
plugin. A remote Orb with an empty home directory now enforces your policy
instead of only the built-in defaults.
Flagged installs (e.g. install --codex) show a loading spinner while the
host CLI runs, so slow network installs no longer look hung.

Windows: npm-installed CLIs ship as .cmd shims, which Node's spawn
cannot start directly. All native install probes and commands now route
through COMSPEC, so install --codex and the interactive picker work on
Windows (#69).
Amp: if an unmanaged file or symlink at
~/.config/amp/plugins/cc-safety-net.ts would mask the newly published
personal plugin, the install now fails with an actionable error instead of
reporting success while the hook may never run.
Amp: the machine-generated commit in the throwaway checkout now carries
an explicit git identity, so the install works on machines with no global
user.name/user.email configured.
A stalled host CLI is now killed after 120 seconds and reported as a
failure, so an install can no longer hang forever.
The Amp install now stops immediately when its staged-status probe fails
instead of attempting the commit anyway.

The release pipeline validates kimi.plugin.json alongside the other
manifests, preserves manifest formatting when bumping versions, and lints
the prepared files before tagging — the failure class that blocked v2.0.2
can no longer reach a tag.

Navigation Menu