Give your AI CLI the installation guide.
For Claude Code CLI, Codex CLI and AGY CLI, even before Holmes-Kit is installed. Copy the request below. The agent explains the options, waits for your choice, then installs and reports what is actually ready.
Documentation basis: 0.40.0 · You choose the version policy before installation. · Read the plain Markdown source ↗
Paste into the CLI you use
Read https://holmes-lab.web.app/agents/holmes-kit/install.md and help install Holmes-Kit. Inspect root, OS, CLI and current Node/npm/Git/Kit versions and paths. Ask me to choose a version policy: guide basis or latest at installation time. Show current/proposed versions, compatibility and impact for each tool; never invent unrecorded verified prerequisites. Explain separate user folder, project local and global npm tradeoffs too. Wait for both decisions and approval of required prerequisite changes before installing or upgrading. Reuse already explicit choices. Preserve settings and local rules, keep autonomy off, and report installation/configuration/restart/binding separately.
Choose the version policy separately.
- Guide-basis policy
- Holmes-Kit 0.40.0 documentation basis. Keep compatible installed prerequisites. Exact verified Node/npm/Git versions were not recorded; the AI must disclose that and propose any missing-tool changes.
- Latest-at-install policy
- Inspect official releases and show compatible exact versions and impacts for Node/npm/Git/Kit. Compare Node LTS/Current and bundled/latest npm. Install or upgrade only after your decision.
The AI waits for both version-policy and installation-location decisions, plus approval for prerequisite changes. Existing choices are reused. A table separates current, proposed and actually installed versions; unverified combinations stay unverified.
You choose the installation mode.
- 1. Separate user folder
- Keeps project dependencies and global npm installation unchanged; separate versioned folder. Manage its path and updates separately; retain the folder while workspaces use it.
- 2. Project local
- Project/team versioning through a lockfile; recommended for the practice project. Changes package.json and lockfile; may introduce npm metadata to a non-Node project.
- 3. Global npm
- Convenient shared installation across projects. Check write permissions and update impact on all projects sharing this installation.
No default is chosen for you. A mode you already specified is reused. Package location and client configuration are separate: even a local install may require user-level client changes, which must be previewed. Model downloads are deferred; no autonomous approval is enabled.
Understand the completion report
- Installed: exact package file/version/path verified.
- Configured: actual settings diff applied; a preview is not application.
- Restart required: start/reconnect the selected CLI and review native trust.
- Binding verified: actual session reports the intended root/store/build; unknown hook observation stays unverified.
This static page does not execute commands, inspect your computer or grant authority. Native support is only claimed where measured.