Skip to content

Conversation

catrielmuller
Copy link
Contributor

@catrielmuller catrielmuller commented Sep 5, 2025

Context

This PR implements multi-file diff functionality for the JetBrains plugin, enabling support for displaying multiple file changes in a single view similar to VSCode's "vscode.changes" command. Additionally, it updates various file paths and references from "roo-cline" to "kilocode" branding.

Implementation

  • Adds multi-file diff command support with new MultiDiffCommands class
  • Updates branding from "roo-cline" to "kilocode" across multiple files
  • Removes unused utility files and example code

Screenshot

image

Copy link

changeset-bot bot commented Sep 5, 2025

🦋 Changeset detected

Latest commit: 5ada302

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
kilo-code Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR implements multi-file diff functionality for the JetBrains plugin, enabling support for displaying multiple file changes in a single view similar to VSCode's "vscode.changes" command. Additionally, it updates various file paths and references from "roo-cline" to "kilocode" branding.

  • Adds multi-file diff command support with new MultiDiffCommands class
  • Updates branding from "roo-cline" to "kilocode" across multiple files
  • Removes unused utility files and example code

Reviewed Changes

Copilot reviewed 11 out of 16 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
jetbrains/plugin/src/main/kotlin/ai/kilocode/jetbrains/editor/MultiDiffCommands.kt New file implementing multi-file diff functionality with vscode.changes command support
jetbrains/plugin/src/main/kotlin/ai/kilocode/jetbrains/editor/EditorCommands.kt Updated to register the new multi-diff commands
jetbrains/plugin/src/main/kotlin/ai/kilocode/jetbrains/util/FutureUtils.kt Removed unused utility file for coroutine-to-CompletableFuture conversion
jetbrains/plugin/src/main/kotlin/ai/kilocode/jetbrains/ipc/proxy/uri/UriTransformerExample.kt Removed example file for URI transformer usage
Multiple files Updated file paths and references from "roo-cline" to "kilocode" branding

@adamhill
Copy link
Contributor

adamhill commented Sep 5, 2025

Is there a specific reason we removed the shell integration scripts?

Don't we need them to enable Jetbrains terminal use? I just tested my zsh and Powershell in the JB Plugin and the LLM can manipulate JB shells (in the 3 I tested right quick - Rider, IntelliJ & WebStorm)

"execute ls -lt it in the Jetbrains terminal"

Copy link
Contributor

@hassoncs hassoncs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! It all looks sane to me. The isTestEnvironment seems a little weird to me... do you know what's going on there?

contentFactory.create(project, file)
}

"cline-diff" -> {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol @ cline still hanging around in this code

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah sorry, I was just commenting in general that "cline" is still in the repo- nothing to do with your code!

Comment on lines 233 to 245
private fun isTestEnvironment(): Boolean {
return try {
// Check if we're running under test
ApplicationManager.getApplication()?.isUnitTestMode == true ||
System.getProperty("idea.test.mode") == "true" ||
Thread.currentThread().stackTrace.any {
it.className.contains("test", ignoreCase = true) ||
it.className.contains("Test", ignoreCase = false)
}
} catch (e: Exception) {
false
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a standard for Jetbrains stuff or vibed? Seems a little sloppy tbh

Copy link
Contributor Author

@catrielmuller catrielmuller Sep 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks really sloppy, that was added for testing, i will remove it.

@hassoncs
Copy link
Contributor

hassoncs commented Sep 5, 2025

@adamhill, I was a little confused at first too, but then noticed the terminal stuff was just moved due to the rename:
CleanShot 2025-09-05 at 12 42 34

@catrielmuller catrielmuller merged commit 980a253 into main Sep 5, 2025
12 checks passed
@catrielmuller catrielmuller deleted the catrielmuller/jetbrains-terminal branch September 5, 2025 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants