Troubleshooting Pieces for JetBrains
Here are links to support resources, documentation, and our Discord channel for troubleshooting related to the Pieces for JetBrains Plugin.
You can also find some specific troubleshooting steps for JCEF-related issues below.
Pieces Copilot: Enabling JCEF Runtime and Downgrade
The Pieces Copilot relies on the JCEF (Java Chromium Embedded Framework) runtime to function properly within JetBrains IDEs.
However, not all JetBrains IDEs, including certain versions of Android Studio, come pre-configured with a JCEF-compatible runtime, which can cause compatibility issues.
Switching to a JCEF-Enabled Runtime
You’ll need to switch your Java runtime to JCEF-enabled runtime inside your global IDE settings.
This operation will require restarting your IDE, so make sure to save your work before doing so.
Follow these steps to switch your runtime:
Open Action Search
Open the Action Search Dialog using ⌘+shift+a
(macOS) or ctrl+shift+a
(Windows/Linux)
Search for Boot Runtime
Search for Choose Boot Java Runtime for the IDE…
Choose Latest JCEF Runtime
Select the latest version from the available JCEF-enabled runtimes
Restart IDE
Android Studio Hedgehog Compatibility Issues
If you’re using Android Studio Hedgehog (2023.1.1), switching to a JCEF runtime may still result in GPU process errors, which can cause performance instability.
This is a known issue with this release, affecting Pieces Copilot and other plugins relying on JCEF (such as the Flutter inspector).
Recommended Workaround for Hedgehog Users
If you encounter GPU-related errors after switching to a JCEF runtime, consider downgrading to Android Studio Giraffe (2022.3.1 Patch 4). This version offers better compatibility until a permanent fix is released for Hedgehog.
To downgrade Android Studio, follow these steps:
-
Uninstall Hedgehog (2023.1.1) from your device
-
Download Giraffe (2022.3.1 Patch 4) from the Android Studio archives, which you can find here
-
Reinstall Android Studio using the Giraffe version and switch the runtime to JCEF-enabled using the instructions above
Unable to Find the Pieces JetBrains Plugin in the JetBrains Marketplace
If you can't find the Pieces for Developers JetBrains Plugin in the JetBrains Marketplace, you can navigate directly to it using this link.
Updating
The Pieces for JetBrains Plugin will automatically update when a new version is available.
You can also manually update the plugin by going to your Plugins window using ⌘+shift+x
(macOS) or ctrl+shift+x
(Windows/Linux).
Next, locate the Pieces for JetBrains Plugin (titled ‘Pieces’) and click the update button.
Check PiecesOS Status
Check to make sure PiecesOS is running. PiecesOS must be running for the Pieces for JetBrains Plugin to work.
Restart JetBrains After Updates
If you’ve recently installed or updated PiecesOS or the Pieces for JetBrains Plugin, restart the IDE.
Reloading the Pieces Copilot Chat Window
You may find that you need to restart or refresh the Pieces Copilot chat, especially if you’re using a cloud LLM and disconnect from WiFi.
These scenarios can occasionally cause the LLM to ‘hang’—which is to appear as if generating a response, but eventually timing out or entering into an infinite response loop, or experience other issues.
To do so, click the small Reload Copilot
symbol above the Pieces Copilot chat, once open.