feat(jetbrains): add Rules settings page; pin CLI to v7.4.13 - #12437
Merged
Conversation
…laude Code compatibility Adds a Rules page under Agent Behavior for managing additional instruction files (config `instructions`) with a Skills-style list: open in editor, in-dialog content editor, and delete. Unifies the add/edit path dialog into a shared SettingsPathDialog (OK button, focused input) and hides in-place list action buttons when the list is not focused.
…port The plugin runs the CLI release pinned in package.json (was 7.4.11), which contains the pre-fix cloud-import path that returns HTTP 400 BadRequest in compiled builds. The fix (#12329) first ships in CLI v7.4.13. No stable release contains it yet (7.4.14 is a draft with no assets), so pin to the v7.4.13 pre-release; the automated jetbrains-cli-pin-bump PR will move to a stable release >= 7.4.13 later. kilo.cli.pinned stays true.
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge All issues from the previous review were addressed in
No new issues found in the incremental changes. Files Reviewed (4 files in incremental diff)
Previous Review Summary (commit c7c7d77)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit c7c7d77)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (40 files)
Reviewed by claude-sonnet-5 · Input: 26 · Output: 4K · Cached: 546.7K Review guidance: REVIEW.md from base branch |
johnnyeric
approved these changes
Jul 21, 2026
- Drop test-only component() seams on SettingsPathDialog and InstructionEditDialog; test layout helpers and public dialog API directly - Remove unused settings.rules.files.remove bundle key across all locales - Note cloud session history import fix in the changeset
t7tran
pushed a commit
to t7tran/kilocode
that referenced
this pull request
Aug 14, 2026
…settings feat(jetbrains): add Rules settings page; pin CLI to v7.4.13
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Two JetBrains changes:
Implementation
Rules settings page
instructionsconfig) in a Skills-style list.CLI pin
7.4.11→7.4.13JetBrains history loading is broken for cloud-only sessions. Loading such a session triggers a cloud import, which fails against the pinned CLI:
The root cause is the pinned CLI binary, not the plugin. The plugin runs the CLI release pinned in
packages/kilo-jetbrains/package.json(was7.4.11). That binary contains the pre-fix cloud-import path, which fails in installed/compiled CLI builds and returnsHTTP 400 BadRequest. The bug exists in every stable CLI release up to and including7.4.11— it is not a regression. The fix (#12329) landed onmainand first ships in CLI v7.4.13; no plugin-side code change is required (the request/response contract is unchanged).Why a pre-release pin: the normal path is to pin to the latest stable release, but none contains the fix yet:
When a stable release ≥ 7.4.13 is published, the automated
jetbrains-cli-pin-bumpPR will move the pin to it and this pre-release pin can be dropped.kilo.cli.pinnedstaystrue(releasable state).Screenshots / Video
How to Test
Manual/local verification
HTTP 400 {"_tag":"BadRequest"}error.Reviewer test steps
HTTP 400 BadRequesterror.Blocked checks and substitute verification
./gradlew typecheckand the full./gradlew testsuite frompackages/kilo-jetbrains/— both pass (executed by the agent).User impact
On update, the plugin auto-downloads the pinned CLI (
v7.4.13) on first connect, verifies its checksum, caches it, and prunes older cached versions. No user action required.Checklist