Repository navigation
v0.1.2
KAP v0.1.2
A patch release about setup: installing hooks once, and being able to tell whether recording works.
Added
kap installputs the Claude Code hooks in~/.claude/settings.jsononce per machine, so no
project or worktree needs its own setup. Existing settings and other hooks are preserved, and
kap uninstallremoves only what KAP added.kap install --settings <path>writes the same hooks into any Claude-compatible settings file,
so another CLI that fires the same events can be attached without KAP knowing its name.kap doctoranswers "will this session be recorded?" — it checks that the hooks exist, that
the binary they call still exists, that recording is not disabled, and whether the current
directory is one where hooks record. It exits non-zero when recording would not happen.- Turning recording off has three levels now:
KAP_DISABLED=1for one session,kap disable/
kap enablefor a repository,kap uninstallfor the machine. kap statussays whether the hooks are installed and whether recording is disabled here.
Changed
- A run no longer records which harness produced it. KAP talks to hooks, not to Claude Code, so any
CLI emitting the same events is equally supported. Migration 0009 drops the column.
Fixed
kap initoutside a repository reported.instead of the resolved directory.- Starting an attempt in a repository with no commits leaked git's
ambiguous argument 'HEAD'; it
now says that an initial commit is needed.
Install
cargo install kap-cliOr take a binary from the assets below (macOS arm64 and x86_64, Linux x86_64), each with a
.sha256. Then kap install once.