sync to main - #1
Conversation
|
Skipping CodeAnt AI review — this PR changes more than 100 files, which usually means a migration, codemod, or vendored drop. Line-level review on diffs this large produces duplicate findings on the same rewrite pattern and drowns out anything that actually matters. If you still want a review, comment |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 245 files
Note: This PR contains a large number of files. cubic only reviews up to 40 files per PR, so some files may not have been reviewed. cubic prioritizes the most important files to review.
On a pro plan you can use ultrareview for larger PRs.
Re-trigger cubic
|
Caution Review failedAn error occurred during the review process. Please try again later. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
1 issue found across 54 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="package.json">
<violation number="1" location="package.json:167">
P2: Root `package.json` bumped to 7.4.13 but `packages/kilo-jetbrains/package.json` is still at 7.4.11 while all other 24 workspace packages are at 7.4.13. This version drift means the JetBrains package is misaligned with the workspace release — likely an oversight in the release commit that left it behind.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
| "mammoth@1.12.0": "patches/mammoth@1.12.0.patch" | ||
| }, | ||
| "version": "7.3.54", | ||
| "version": "7.4.13", |
There was a problem hiding this comment.
P2: Root package.json bumped to 7.4.13 but packages/kilo-jetbrains/package.json is still at 7.4.11 while all other 24 workspace packages are at 7.4.13. This version drift means the JetBrains package is misaligned with the workspace release — likely an oversight in the release commit that left it behind.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 167:
<comment>Root `package.json` bumped to 7.4.13 but `packages/kilo-jetbrains/package.json` is still at 7.4.11 while all other 24 workspace packages are at 7.4.13. This version drift means the JetBrains package is misaligned with the workspace release — likely an oversight in the release commit that left it behind.</comment>
<file context>
@@ -164,6 +164,6 @@
"mammoth@1.12.0": "patches/mammoth@1.12.0.patch"
},
- "version": "7.4.11",
+ "version": "7.4.13",
"peerDependencies": {}
}
</file context>
There was a problem hiding this comment.
1 issue found across 43 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="packages/script/package.json">
<violation number="1">
P3: Version bump in `packages/script/package.json` modifies a shared upstream file without a `// kilocode_change` marker. Per AGENTS.md, changes to shared files (paths without `kilo` in the name) should mark each Kilo-specific line with `// kilocode_change`. The target branch has `"version": "7.3.54"`, so this PR introduces a Kilo-specific version divergence.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
There was a problem hiding this comment.
1 issue found across 65 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="packages/kilo-vscode/CHANGELOG.md">
<violation number="1" location="packages/kilo-vscode/CHANGELOG.md:30">
P3: The 7.4.16 release note advertises `@kilocode/kilo-ui` and `@kilocode/sdk` as 7.5.0, but the package manifests and lockfile for this release resolve both to 7.4.16. This makes the dependency metadata inaccurate; the entries should match the release artifacts.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
| - @kilocode/kilo-ui@7.5.0 | ||
| - @kilocode/sdk@7.5.0 |
There was a problem hiding this comment.
P3: The 7.4.16 release note advertises @kilocode/kilo-ui and @kilocode/sdk as 7.5.0, but the package manifests and lockfile for this release resolve both to 7.4.16. This makes the dependency metadata inaccurate; the entries should match the release artifacts.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At packages/kilo-vscode/CHANGELOG.md, line 30:
<comment>The 7.4.16 release note advertises `@kilocode/kilo-ui` and `@kilocode/sdk` as 7.5.0, but the package manifests and lockfile for this release resolve both to 7.4.16. This makes the dependency metadata inaccurate; the entries should match the release artifacts.</comment>
<file context>
@@ -1,5 +1,40 @@
+- [#12488](https://github.com/Kilo-Org/kilocode/pull/12488) [`c25f041`](https://github.com/Kilo-Org/kilocode/commit/c25f041eb3922defc4dadb9ad7b2f8c8edb74fbd) - Show the request ID when a model response ends without a finish reason.
+
+- Updated dependencies [[`b367105`](https://github.com/Kilo-Org/kilocode/commit/b367105c8d648c8e05b62c2d27a28a95a4772f61), [`c1f057a`](https://github.com/Kilo-Org/kilocode/commit/c1f057ad5a2021cd57e003cad7d45e5e6b0b4cba), [`2fcb137`](https://github.com/Kilo-Org/kilocode/commit/2fcb137ebcbf9101ca655804d0a61af2f222bbc5), [`f715e2f`](https://github.com/Kilo-Org/kilocode/commit/f715e2f5fa4db5abe5c734e1c360e8da3367f3e5), [`dcc0d64`](https://github.com/Kilo-Org/kilocode/commit/dcc0d64a3249bdd3aa27d564759253126ff9a5fe)]:
+ - @kilocode/kilo-ui@7.5.0
+ - @kilocode/sdk@7.5.0
+ - @kilocode/kilo-gateway@7.4.16
</file context>
| - @kilocode/kilo-ui@7.5.0 | |
| - @kilocode/sdk@7.5.0 | |
| - @kilocode/kilo-ui@7.4.16 | |
| - @kilocode/sdk@7.4.16 |
There was a problem hiding this comment.
1 issue found across 1 file (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="nix/hashes.json">
<violation number="1" location="nix/hashes.json:3">
P1: The `nix/hashes.json` nodeModules hashes are being changed to values that differ from `main` without a corresponding `flake.lock` update. Per repo conventions, hash changes must be backed by an upstream dependency update (e.g., `nix flake update`) and the commit message must reference the source of the new hashes. Without a lockfile change, these hashes won't match any real dependency state, breaking reproducible builds.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
| "aarch64-linux": "sha256-kpJ1SFCmBrhDwuJNJNoDU5NK6mDvEG4Yd41w9YJnsOs=", | ||
| "aarch64-darwin": "sha256-junSolEGOe+xUmPY4SAJGj+XKuytxvD0IWQWtLiaIEs=", | ||
| "x86_64-darwin": "sha256-p+3Jtb5CZexwx0UlhVeqeMr25R+jkjahFp9YTZYK0rE=" | ||
| "x86_64-linux": "sha256-sid/FCql4CmiAb1MNGMH33fwNs6esv9UNC819Yb03bQ=", |
There was a problem hiding this comment.
P1: The nix/hashes.json nodeModules hashes are being changed to values that differ from main without a corresponding flake.lock update. Per repo conventions, hash changes must be backed by an upstream dependency update (e.g., nix flake update) and the commit message must reference the source of the new hashes. Without a lockfile change, these hashes won't match any real dependency state, breaking reproducible builds.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At nix/hashes.json, line 3:
<comment>The `nix/hashes.json` nodeModules hashes are being changed to values that differ from `main` without a corresponding `flake.lock` update. Per repo conventions, hash changes must be backed by an upstream dependency update (e.g., `nix flake update`) and the commit message must reference the source of the new hashes. Without a lockfile change, these hashes won't match any real dependency state, breaking reproducible builds.</comment>
<file context>
@@ -1,8 +1,8 @@
- "aarch64-linux": "sha256-7S209ir2j9o9NXYmMUnEfo6m64cUIkexd8L95UeCMFE=",
- "aarch64-darwin": "sha256-bE1zw7EK+4rgUgw80t8hdc2yojAF2f8ihjorh6B7jJE=",
- "x86_64-darwin": "sha256-xukM9cEvZAKCXewun9xReGBKz09i63LACLN/eH54020="
+ "x86_64-linux": "sha256-sid/FCql4CmiAb1MNGMH33fwNs6esv9UNC819Yb03bQ=",
+ "aarch64-linux": "sha256-1H1873nLqmcKrumAjnjPPts5+EyJLBm1Z5VKsOYANeg=",
+ "aarch64-darwin": "sha256-i7D5RSPIVxXNY1gUnsYdFhVU2FxYEcjqYcQx6zZrJjg=",
</file context>
There was a problem hiding this comment.
All reported issues were addressed across 70 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
There was a problem hiding this comment.
All reported issues were addressed across 116 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
|
Caution CodeRabbit couldn't update its existing comment. The review summary may be out of date. Error details |
Co-authored-by: Christiaan Arnoldus <christiaan.arnoldus@outlook.com>
…ool-schema revert(agent-manager): restore provider-compatible tool schema
feat(jetbrains): agent manager beta
test(core): make project copy cleanup idempotent
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
…n-fast-typing fix(jetbrains): keep slash completion open while typing
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
…r-comments fix(agent-manager): stabilize PR review comments
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
feat(jetbrains): open sub-agent sessions in editor tabs
fix(cli): send max-step instruction as user message
…ti-project-session-loading # Conflicts: # packages/kilo-vscode/src/agent-manager/pr-status-bridge.ts # packages/kilo-vscode/tests/unit/am-pr-status-bridge.test.ts # packages/kilo-vscode/webview-ui/agent-manager/pr/PRPanel.tsx
…-sidebar # Conflicts: # packages/kilo-ui/src/components/message-part.tsx # packages/kilo-vscode/webview-ui/agent-manager/AgentManagerApp.tsx # packages/kilo-vscode/webview-ui/agent-manager/agent-manager.css # packages/kilo-vscode/webview-ui/agent-manager/side-panel-layout.ts
…ct-session-loading fix(agent-manager): scope multi-project session state
fix(model-selector): match colon-prefixed names
…-sidebar # Conflicts: # packages/kilo-vscode/webview-ui/agent-manager/AgentManagerApp.tsx
…ross-reloads fix(agent-manager): prevent PTYs escaping worktree cleanup
* fix(vscode): use minimum prompt input gutter * chore: update kilo-vscode visual regression baselines --------- Co-authored-by: kilo-maintainer[bot] <kilo-maintainer[bot]@users.noreply.github.com>
feat(agent-manager): preview edits in side panel
chore(jetbrains): bump CLI pin to v7.4.23
feat: add provider usage center
9 participants
Hey! Darko from Kilo here 👋
Saw you forked Kilo, really appreciate for building on top of us.
We are putting together a short Kilo Show segment on why people contribute to open source, and would love to include real perspectives from folks like you.
If you are open to it, would you be up for sharing a quick thought or two on what motivates you (or would motivate you) to contribute to open source?
Also opened a small PR to sync your fork with main in case that is useful.
Summary by cubic
Syncs this fork to upstream OpenCode v1.18.13 and refreshes our patches. Key behavior changes: VS Code edit/write/patch previews open in Agent Manager (not new tabs), background subagents are on by default, Ask/Plan remain read‑only unless allowed, and the legacy agent requirements feature is removed.
VS Code + Agent Manager (
kilo-code): in‑panel edit/patch previews with inline expansion and persistent diff view; stabilized inline diff scrolling and reachable permission‑prompt actions with large diffs; PR comment diff rendering; durable PTYs with cleanup on worktree deletion; focus‑aware terminal shortcuts and focused‑terminal context attachments; predictable scroll‑follow and stabilized session status dock; model selector search matches provider prefixes; restored session history on first worktree switch; background subagents surfaced in a header strip with notifications; document inspector for Markdown/text with inline review; removed multi‑project trust toggle; shared minimum prompt‑input gutter across panels; Enter/Tab executes the highlighted slash command in the command picker.JetBrains (
@kilocode/kilo-jetbrains): Advanced settings with Logging (stablekilo.logpath, rotation, legacy cleanup); show proposed file diffs in permission prompts; “why approved” footers on tool cards (toggle on by default); open sub‑agent task sessions in read‑only tabs; open/edit/delete workflows; keep slash‑command completion stable during fast typing and restore prompt focus after model/agent pickers; avoid IDE internal‑error popups and include HTTP details; preserve migration wizard across reconnects and restore worktree session; reuse session modal layout for migration; unblock public API release.CLI (
@kilocode/cli): fall back from unwritable state directories and verify writes; keep Ask/Plan read‑only under broad permission rules; prevent step‑limit provider errors by sending final summaries as user input; restore provider‑compatible Agent Manager tool schema and allow nullable tool fields; remove duplicate skill catalog; preserve prompt‑tool service env and clarify background process waits; scope interactive terminal and notebook state by directory.TUI: keep Kilo Gateway models visible and searchable by provider/name/id; keep selection stable when a model appears in multiple sections.
CI/CD and repo: rolling docs‑sync bot with triage/edit/learn, watermarking, redacted logs, and self‑tests; new JetBrains publish workflows (including bundled); Linux sandbox helper; Node 24 setup and skip Bun cache on Windows; tighter path filters (ignore
.kilo/plans/**), split JetBrains typecheck and path‑scoped gating; improved CodeQL/container guards; narrower i18n diffs (showen/de).Removals: agent requirements feature and legacy metadata; PR sidebar scroll button.
Required migration
kilo pr <number>no longer checks out a PR. Usekilo pr checkout <number>. Link/unlink withkilo pr link <url>/kilo pr unlink; check withkilo pr status.agent.ask.permissionoragent.plan.permissionto allow mutations in those modes.Written for commit ff74e2e. Summary will update on new commits.