| name | jetbrains-cli-pin |
| description | Use when pinning or unpinning the CLI version the Kilo JetBrains plugin uses, or fresh-regenerating the local repo CLI. Cleans all leftover CLI binaries and build artifacts in the current worktree so every operation starts from a fresh, artifact-free state. |
JetBrains CLI Pin
Pin the Kilo JetBrains plugin to the latest released CLI, unpin it to use the local
repo CLI, or fresh-regenerate the local CLI while unpinned. Every command first cleans
all CLI/pin build artifacts and binaries in the current worktree so the result never
carries state from a previous run.
Run all commands from the repository root of the worktree you want to affect. Paths are
relative, so they resolve to the current worktree, not the main checkout.
Two Controls
The plugin's CLI behavior is governed by two independent values:
| Control | Location | Meaning |
|---|
| Pin mode | packages/kilo-jetbrains/gradle.properties -> kilo.cli.pinned | true = download the released CLI at build/connect time. false = build and bundle the local repo CLI. |
| Pinned version | packages/kilo-jetbrains/package.json -> version | Which GitHub CLI release is downloaded and generated from when pinned=true. |
"Pin to latest" means kilo.cli.pinned=true and package.json set to the latest
stable CLI release. "Unpin" means kilo.cli.pinned=false with a freshly built local CLI
bundled.
Commands
bun .kilo/skills/jetbrains-cli-pin/script/cli-pin.ts <command> [--no-verify]
| Command | Steps |
|---|
pin | Clean -> set kilo.cli.pinned=true -> remove the repo-CLI Bun path hint -> bump package.json to latest release (via set-pin.ts --latest, which validates release assets) -> verify with a cold gradlew clean typecheck. |
unpin | Clean -> set kilo.cli.pinned=false -> write the repo-CLI Bun path hint -> :backend:buildRepoCli (fresh CLI) -> :backend:stageRepoCli -> assert staged kilo-cli.zip -> verify with gradlew typecheck. |
regen | Fast dev loop while unpinned: refresh the repo-CLI Bun path hint -> rm -rf dist -> buildRepoCli -> stageRepoCli. Refuses to run unless kilo.cli.pinned=false. |
clean | Run the shared artifact clean only. |
--no-verify skips the gradle verification build (rewrites + clean only). Use it when
offline or without Java 21.
Cleaned Artifacts
clean() runs ./gradlew clean plus targeted deletes. All paths are gitignored, so
tracked files are never touched. The clean removes the stale artifacts that otherwise
leak across a pin/unpin flip:
| Artifact | Path |
|---|
| Repo CLI binaries | packages/opencode/dist/ |
| Staged CLI archive | packages/kilo-jetbrains/backend/build/generated/kilo-cli-res/kilo-cli.zip |
| Generated props / checksums / OpenAPI client | packages/kilo-jetbrains/backend/build/generated/ |
| Compiled resources (bundled zip on classpath) | packages/kilo-jetbrains/backend/build/resources/ |
| CLI download cache | packages/kilo-jetbrains/backend/build/cli-cache/ |
The staged kilo-cli.zip is the nastiest leak: once it lands in backend/build/resources/main/
from an unpinned build, runtime prefers the bundled zip over downloading. A full clean is
the only reliable reset.
Bun Path Hint
In repo CLI mode, Gradle's generateOpenApiSpec task runs the local CLI source through
bun run --conditions=browser ./src/index.ts generate. IDE-launched Gradle runs can have
a stripped PATH where bun isn't resolvable. The unpin/regen commands write an ignored, worktree-local hint:
packages/kilo-jetbrains/.gradle/kilo-cli-pin.properties
The file contains bun.path=<absolute path> and is consumed by backend/build.gradle.kts
for repo CLI tasks. pin removes it because pinned mode should not depend on local Bun.
Notes
- Verification builds pass
--no-configuration-cache so the changed kilo.cli.pinned
value is re-read instead of served from the on-disk Gradle configuration cache.
- The
pin verification is a cold build: it downloads the pinned CLI release via
generateOpenApiSpec and needs network access plus Java 21. Use --no-verify offline.
kilo.cli.pinned=false is dev-only and not releasable. Production Gradle builds,
script/build-version.sh, and the release scripts hard-fail on false -- run pin
before releasing.
Related
- Version-bump and release-gating logic lives in the
release-jetbrains skill
(.kilo/skills/release-jetbrains/SKILL.md); this skill reuses its set-pin.ts and
pin-common.ts helpers.
- Background on the build wiring: the "CLI Pinning, Unpinning, and Bumping" and "CLI
Integration" sections of
packages/kilo-jetbrains/AGENTS.md.
