Illuminated Cloud Announcements

2.4.1.1 Enabled support for the 2026.2 JetBrains IDEs that are now in a release candidate state. As always, if you see issues with a pre-release IDE build, please revert to the most recent released build and let me know about the issues you've seen so that I can address them. NOTE: I've pretty much completed the Bitbucket-to-GitHub migration for the public issue tracker and user guide/wiki. I'm planning to flip the switch early next week with all external references updated accordingly and the Bitbucket functionality switched to a read-only mode with links to the replacing features in GitHub. There will be a small IC2 release to accompany this change since some of the external references are in IC2 itself. 

2.4.0.1 As noted in the previous release notes, starting with 2026.1,  free  JetBrains IDEs now include  first-class language support  for  JavaScript, TypeScript, and CSS  (i.e., without an active JetBrains subscription). Also as stated previously, the main things that are notably missing are the JavaScript debugger and Jest support, but I've addressed those omissions in IC. A  demonstration  of these features is available  here . Note that the items described below are  only  available in  free JetBrains 2026.1+  IDEs. All  commercial  JetBrains IDEs already have their own versions of the same features, and they will not work with earlier free JetBrains IDEs because they build on the 2026.1+ IDEs' free JavaScript and TypeScript support. Users pairing IC with a free JetBrains IDE are  strongly encouraged  to use 2026.1+ going forward. With that preface out of the way, IC now includes  first-class ...

2.4.0.0 Issue 2939  - Fixed an issue that could occur when an error is reported for a source file by the API or CLI with a simplified path, e.g.,  classes/Foo.cls , where the local path is more complex, e.g.,  classes/subfolder/Foo.cls . Now if no matches are found using the reported path, IC looks for a unique source file with the same name and, if found, reports against it. Issue 2941  - As of  2026.1 , IntelliJ IDEA includes  first-class language support  for JavaScript, TypeScript, and CSS  for free  (i.e., without an Ultimate subscription). This includes not just basic language support features like intelligent code completion, reference navigation, source code formatting, etc., but also extensive refactorings, static code analysis including integration of ESLint and Stylelint, tight npm integration, and much more. The main things that are notably missing are the JavaScript debugger and Jest support, but I'm working on a very tight integ...

2.3.9.9 Enabled support for the 2026.1 JetBrains IDEs that are now in a  release candidate state . As always, if you see issues with a pre-release IDE build, please revert to the most recent released build and let me know about the issues you've seen so that I can address them. Issue 2929  - Made sure that the connection icon includes a lock overlay consistently for connections that require write confirmation. It was most noticeably missing in the connection status bar widget. Issue 2936  - Fixed a  StackOverflowError  that could occur when overriding dynamic file types. Fixed a few issues with placeholder  *.object-meta.xml  files being incorrectly treated as full custom object files during metadata deployment and retrieval. Improved CLI-based deployment result reporting where some information was being sent to  successes  and  failures  instead of  files  in the JSON result. Added support for contextually-correct code co...

2.3.8.7 Issue 2890  - Fixed issues with Illuminated Cloud in free 2025.3+ IDEs. As of 2025.3, JetBrains has removed IntelliJ IDEA and PyCharm Community Edition IDEs and replaced them with  unlicensed commercial editions  of those same IDEs. IC was enabling Community Edition-specific functionality in a very specific manner that does not work in these unlicensed commercial IDEs. That should be resolved with these fixes. The one notable downside is that some free IDE-specific functionality may be visible in licensed commercial IDEs even if it's completely inactive. Those features are generally labeled with "(free IDEs)" and can be safely ignored in licensed commercial IDEs. If you still see any remaining regressions or issues in free 2025.3+ IDEs relative to the previous Community Edition IDEs, please report them in the  public issue tracker  and I'll address them ASAP. Fixed an issue with the  PMD Salesforce  inspection against more recent PMD distributi...

2.3.8.6 Enabled support for the 2025.3 JetBrains IDEs that are now in a  release candidate  state. As always, if you see issues with a pre-release IDE build, please revert to the most recent released build and let me know about the issues you've seen so that I can address them. Issue 2878  - Prospective fix for a freeze observed in a user-provided thread dump where IC is frequently enumerating full LWC components including all attributes when only component header information is required. Issue 2882  - Added  editor  as an allowed attribute of the  TargetConfigProperty  element in LWC component  meta.xml  files. Issue 2883  - Fixed several issues with how  {label.*}  is processed in LWC HTML templates. Previously it was interpreted as a custom label reference, but that was incorrect. Now it's properly interpreted as a JS/TS controller reference. Also added support for braced expression variant completions and references vi...

2.3.6.8 Updated IC for JetBrains' 2025.2 releases now that they've entered a release candidate state. As noted previously, due to breaking plugin SDK changes in 2025.2, I've had to drop IC support for 2024.*, so please make sure that you're using 2025.1 or higher. Also, due to a wholesale change to one JavaScript API, some specific types of code completions are now only available in 2025.2, particularly those for the  config  parameter of the LWC  @wire  adapter. This change only affects those using IC with commercial JetBrains IDEs. Issue 2817  - Added support for the  LightningTypeBundle  metadata type. This is another pseudo-bundle metadata type that requires specialized handling. Note that deployment errors reported against files from these bundles do not specify a valid file, so IC currently follows the Salesforce CLI's precedent of attributing those errors to the bundle's  schema.json  file. Unfortunately this is rarely the actual file ...

2.3.6.7 Issue 2725  - It's now possible to add a  tsconfig.overrides.json  file as a peer to the generated  tsconfig.json  and  tsconfig.compile.json  files under a project's  lwc  directories. When present, this file is automatically added to the generated files'  extends  lists to allow customization of TypeScript compiler behavior. While the order in which these files are processed should help prevent overriding options which are critical for IC's core TypeScript compilation functionality, if you make a change that does result in broken or incorrect compiler output, please revert that change and let me know so I can help further insulate against unintentional issues. Issue 2800  - Added support for inlining of Flow text templates at their point-of-use. Note that when these are rich text, the raw HTML is escaped and displayed inline. I'd also like to add support for inlining of other resource types such as choices, choice col...

2.3.6.4 Added support for multiple context files in the Agentforce for Developers  Dev Assistant  tool window. The  Use the selected editor  option is still used to add the file in the selected editor tab as a context file, and there is now an  Additional context files  expandable text field and companion  Add context file  button to add and manage other files from the project that should be included in the generated prompt for context. Note that the Agentforce API does limit the prompt size, so adding large numbers of context files and/or large context files may result in errors during prompt execution. Added support for  ESLint  integration in JetBrains  Community Edition  IDEs via LSP4IJ 0.14.3 (not yet released, but you can install a  nightly build  to play with it now) and Microsoft's  ESLint language server : If ESLint is integrated via LSP4IJ and the Salesforce Code Analyzer 5 integration is configured to ...

2.3.5.5 This is a small, tactical hotfix build for a few issues found in  2.3.5.4  and/or the JetBrains 2025.1 updates. Issue 2766  - Fixed an issue with the new HTTP Client Salesforce API invocation feature that could occur when some connection configurations are invalid and/or incomplete. Issue 2768  - Fixed an issue with the Agentforce for Developers Dev Assistant tool window in 2025.1 attributable to a breaking plugin SDK change that I have already  reported  to JetBrains. Issue 2769  - Note that there also seems to be an issue with the Agentforce for Developers inline autocompletion API at present that I have already  reported  to Salesforce.  

2.3.5.3 Unlocked compatibility with JetBrains' soon-to-be-released 2025.1 updates. While unlikely, it is still possible for breaking plugin SDK changes to be introduced in between the  current release candidate  and the final 2025.1 release, rendering this build of IC incompatible. If so, I will release another IC build in conjunction with the final 2025.1 release with the necessary fixes. My recommendation, as always, is to stay on the most recent  released  version of the IDE at all times, but this build of IC should allow it to be installed and used in 2025.1 barring unforeseen breaking plugin SDK changes in between RC1 and GA.  

2.3.3.6 Enabled compatibility with JetBrains' upcoming  2024.3  releases. As usual, I recommend that all users stay on a fully-supported JetBrains IDE release as there is always a slim chance of minor-but-breaking changes in JetBrains' final builds leading up to the 2024.3 release, but assuming that doesn't happen, 2024.3 should be good to go starting with this build. If any breaking changes are found in subsequent JetBrains builds, I will issue an IC2 hotfix ASAP. Issue 2669  - Fixed a potential performance issue with the Agentforce for Developers Dev Assistant when  Include referenced schema  is enabled and local custom object metadata files do not include  <label>...</label>  information. Fixed an issue that could occur when a suppression comment is found at the very beginning of an Apex source file. Also note that the lack of usual weekly releases over the past few weeks is due to the time required to get the next big feature ready. Bar...

2.3.2.2 Unlocked support for JetBrains' 2024.2 builds which are currently in an  EAP (Early Access Program)  state. Note that while IC2 can now be installed into these builds, I  strongly discourage  using them until an  official  build is released, likely at the end of July or beginning of August. Pre-release builds often include breaking changes to the plugin SDK. I'm unlocking support to avoid a catch-22 that can occur when JetBrains begins rolling out official builds of a new version without a compatible IC2 build already available in the plugin repository. I will update IC2 as necessary between now and the official 2024.2 release with any changes required for breaking plugin SDK changes. If you decide to brave these waters and run into issues, please feel free to  report them  in the  public issue tracker  so that I can address them, and then  revert  to the most recent  supported official build  of 2024.1. Issue...

  2.3.1.7 JetBrains has issued patch-level updates for all of their 2023.1+ IDEs to fix a  security issue . Please see the linked information for details, but the short version is that the security issue should only affect those using JeBrains' GitHub pull request integration. Nonetheless, I  strongly  encourage all users update to a JetBrains IDE version with this fix ASAP. More improvements to the recent dependencies-/dependents-based enhancements for Apex unit test execution and code coverage analysis: All transitive dependencies and dependents are now collected at the member-level instead of the file-level. Again, this means that the resulting set of dependencies/dependents should be as small and focused as possible short of performing runtime data flow analysis. When using the new "changed-only" features, this should ultimately mean less time spent waiting for unrelated unit tests to execute and a more focused view of impacted code coverage. Added many more meta...

2.3.0.9 Issue 1245  - Added missing Aura component attributes  lightning:accordionSection > label  and  aura:handler > includeFacets . Issue 1886  - Fixed an issue with Apex parser recovery in ternary expressions when there are syntax errors in the second (i.e., true branch) expression. Issue 1991  - Fixed an issue with the Apex lexer incorrectly tokenizing  /**/  as an unterminated documentation comment. Issue 1992  - Fixed an issue with Apex parser pinning and recovery when an inner interface is followed by a member variable without annotations or modifiers. Issue 2554  - Fixed an issue that would prevent the connection status bar widget from displaying when no Salesforce CLI is found by or registered with IC2. Issue 2555  - Added copy-to-clipboard support for SOQL query results in the tree view (in addition to existing copy support for the table view) as JSON, both plain text and syntax-highlighted HTML data flavors. Fixed ...

  2.3.0.5 Issue 2547 / 2024.1 updates  - This build includes changes to allow IC2 to be used with the 2024.1 JetBrains IDEs. Note that due to the removal of a bundled third-party library from the base JetBrains IDEs, it is no longer possible to export Flow diagrams in PNG format. Export to HTML is still supported. I looked at bundling the removed library with IC2, but it would have increased the IC2 distribution size by over 50%. I'll continue to investigate ways to provide other export capabilities with the ideal being proper resolution of the known issues with the Mermaid plugin's SVG export feature. Issue 2501  - Added support for  Flow.Interview  inner classes that reflect the project's local Flow metadata. The OST must be regenerated to see the effect of this change. Issue 2537  - Updated the  PMD Salesforce  code inspection to use  PMD 7 . Note that this  removes support for PMD 6  due to significant changes in the Java API be...

  2.2.9.1 JetBrains 2023.3 (pre-release) support  - At the time of this release, the JetBrains 2023.3 IDEs are still in a  pre-release  state (currently  Beta ). As usual, I have updated IC2 for each pre-release build to ensure compatibility and will continue to do so until the final release, but I'm also unlocking IC2 support for that version even before the final official release. This obviously carries some risk for  early adopters  as there could be breaking plugin SDK changes during the final beta and release candidate phases. If so, I will again update IC2 to accommodate for those breaking changes. While  not recommended , if you choose to move to 2023.3 while it's still in pre-release, you will receive a warning when the IDE is first started about this potentially fragile state. If you encounter issues unique to these 2023.3 pre-release builds, please file a bug in the  public issue tracker  to ensure that I'm aware of them, then ...

  2.2.7.7 Issue 2402  - Fixed an issue where environment variables—most notably those configured for the Salesforce CLI—would not be propagated to sub-processes created by IC2 on Mac. Many thanks to Kyle Blair for his help in characterizing this issue and verifying the ultimate fix! Issue 2405  - Fixed an issue where the  Tab  key wouldn't be processed properly in an empty file/editor. Issue 2406  - Provided a workaround for one of two regressions introduced in 2023.2 that would result in repeated prompting for TextMate Bundles configuration in Community Edition IDEs. These two issues, as reported to JetBrains, are: IDEA-327045  - This is the issue for which a workaround is included, so hopefully it should be resolved seamlessly for users going forward. IDEA-327051  - IC2 does not include a workaround for this issue, but JetBrains has reproduced it and should hopefully be implementing a proper fix shortly. In the interim, they provided a manual wo...

  2.2.7.6 Issue 2401  - Added support for the JetBrains 2023.2 IDE releases. This has been well-tested, but if you do find any new issues after updating to the official 2023.2 build of an underlying JetBrains IDE, please report them in the  IC2 public issue tracker  with as much diagnostic data as possible. NOTE:  During OST generation you may be seeing longer times when querying the Apex system/standard types, or you may even see that step fail one or more times and and then ultimately succeed upon retry. I am in active discussion with Salesforce about these issues. They have identified the root causes (there are evidently multiple contributing problems) and are investigating potential solutions. I will update IC2 as appropriate based on these solutions (if updates are even necessary) and will post progress in  Issue 2400  and also here as part of the standard release notes.

  2.2.6.0 JetBrains 2023.1 update  - Changes required for compatibility with JetBrains' 2023.1 IDE releases. Quality of life improvements Issue 2318  - Changed the way that IC2 determines whether or not a file is a source or SDK file so that it uses the IDE's native project file index. For the few who have experienced a deadlock on initial project startup, this should take care of it. For all users, this might result in a slight overall performance increase. Issue 2331  - The user is now prompted when closing Anonymous Apex and SOQL Query tool window tabs if the tab is unsaved and has contents or is saved and modified relative to the corresponding file. Issue 2333  - ApexDoc comments are no longer required to be on the line immediately preceding the documented declaration. There can now be any number of intermediate blank lines separating the comment and the declaration. Fixed a memory leak that would result in accumulated cached data as projects are closed acro...