Illuminated Cloud Announcements

2.4.1.7 Issue 2998 - IC no longer bundles the Salesforce skills. Instead it uses the GitHub repo for Salesforce skills , checking the latest published version against the installed version and, if not yet installed locally or an update is available, cloning the repo into a temp directory and installing those. Note that there are significant differences between the original skills bundled with IC and the latest from that repo, so you might want to remove the existing skills before installing the new ones. Of course, if you've customized those skills and/or added your own, you should reconcile carefully to avoid losing anything. When a project is opened — including as part of IDE startup — IC checks for a plugin update. While the IDE already does this for all installed plugins, it only looks for updates that are compatible with the installed JetBrains IDE. Given that IC maintains compatibility with (roughly) one year's worth of JetBrains versions, currently 2025.2-2026.2, users ...

2.4.1.6 - Hotfix for 2.4.1.5 Issue 3001 - For some reason the compiler marked the catch block for UnexpectedErrorFault as invalid in IC's expired/invalid session handling logic, so I removed it. Sure enough, though, that exception still occurs, and now IC wasn't handling and recovering from it properly any longer. This is a targeted hotfix to restore that handling, albeit in a manner that the compiler no longer flags.

2.4.1.5 Issue 2995 - Fixed several issues with ApexDoc Markdown processing during parsing, conversion to HTML, and formatting. Note that the ApexDoc formatter option to add HTML paragraph break elements on blank lines is now automatically disabled if any of the ApexDoc Markdown-related formatter options are enabled. Paragraph breaks are, of course, added in Markdown with two consecutive blank lines, so it didn't make sense to have both options enabled simultaneously. Improved the background threading behavior changes introduced in the previous build to allow immediate cancelation of read-only API calls. This specifically improves the "hand-off" of progress indicators across background threads, and eliminates (or at least minimizes) unnecessary creation of background/worker threads from existing background/worker threads. Added XSD element definitions for FeatureParameter* and GenAiPromptTemplate metadata. Improved progress indicator feedback when refreshing the org met...

2.4.1.4 Issue 2979 - Implemented several performance improvements around the build options dialog and module subscription editor in projects with very large amounts of org metadata. Issue 2985 - Fixed several issues with metadata types that are either not reported properly by the Metadata API or have insufficient information about parent/child metadata type relationships. This addresses some specific issues, but I'm sure there are other metadata types — specifically those gated by feature flags — that are still unaddressed. I'll be happy to take care of those, but I'll need to know the specific metadata types and enabling feature flags. Issue 2990 - IC application-level settings now try to infer project-level context better when opened via system settings. Added support for the Agent Script Language Server for *.agent files. As usual, LSP4IJ is required, and you must also download the language server distribution and register it with IC. IC will, of course, help insta...

2.4.1.3 Issue 2987 - Fixed several issues with Flow diagrams in 2026.2. While diagrams now render properly, there are still a few remaining issues that seem attributable to the newer version of Mermaid used by the 2026.2+ version of the Mermaid plugin: Icons do not display properly, so they're not included in diagram nodes. The diagram look-and-feel options, e.g., Elk renderer and curve styles, don't seem to have any effect. Fixed several issues with copying Apex string literal contents to the system clipboard that were introduced with Apex multiline string support. A quick reminder that the public issue tracker , user guide , and discussions have been completely migrated from Bitbucket and Google Groups respectively into GitHub. The original public issue tracker and user guide will be removed by Atlassian on August 20, 2026 as part of its sunsetting of Bitbucket Cloud issues and wikis , and the original discussion groups are now read-only historical archives given that the o...

2.4.1.2 The migration of the public issue tracker and user guide from Bitbucket Cloud to Github is now complete. The original resources are now in a read-only mode and will no longer be available starting August 20, 2026. The new resources are: Issue tracker - All issues have been migrated with as much of the original content as possible. A few items of note: Some issue numbers have changed, so if you have external references to the originals, you may need to update those not just for Bitbucket vs GitHub, but also for the new issue numbers. The issue titles are (mostly) unchanged, so you should be able to locate the new one easily by title. I've updated all internal links between issues to accommodate for these changes. Unfortunately I wasn't able to attribute migrated issues to the GitHub user IDs corresponding to the original Bitbucket issue creator user IDs, but the original Bitbucket user IDs and creation date/time information are included in the migrated issues for histo...

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.1.0 Many improvements and fixes for Apex multiline strings and string templates: Generalized string template support so that it works properly for both simple strings and multiline strings. Added support for bidirectional navigation and highlighting of string template variable declarations and references. Note that highlighting of references when the caret is on a ${name} reference in a string literal is still not perfect. Unfortunately this seems to be due to some aggressive caching in the JetBrains IDE itself since the string literal is technically a single element, so I may not be able to improve it beyond its current state. Added support for renaming of string template variables via both the associated map key and any reference to that key. Changed multiline string literal syntax highlighting to match how the analogs are displayed in other first-class languages such as Java and JavaScript/TypeScript. Added indent guides to show the left border of indented multiline string cont...

2.4.0.9 Issue 2979 - Fixed an issue that could cause the derived invokable declaration index to fail indexing, resulting in constant "Analyzing" behavior. Added support for aer-based integration test execution with aer 1.2.0 +. Added support for Agent Script's subagent directive type including code completion, reference navigation, syntax highlighting, etc. Fixed an issue where class methods weren't being included in System.Label variant completions.

2.4.0.8 Issue 2974 - Summer '26 / API v67.0 update Updated the SOAP client for API v67.0. Updated the API version used for primary communication with Salesforce APIs to 67.0. Added 67.0 as an available API version number for configured connections. Updated metadata.xsd based on the API v67.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in Summer '26. Updated the bundled completions?type=apex Tooling REST API response to be based on the API v67.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Summer '26 changes. Updated the bundled SLDS CSS and SVG icons to 2.30.4. Updated for new org features, standard value set names, metadata XML file type extensions, etc. Updated all integrated API documentation. Usages of SOQL WITH SECURITY_ENFORCED in Apex source files with API version 67.0+ are now flagged as errors with a quick-fix to use WITH USER_MODE instead. Apex classes with...

2.4.0.7 Minor bug fix release before next week's Summer '26 updates: Issue 2968 (redux) - Improved fix for an NPE when copy/pasting files to the IDE project. Issue 2972 - Addressed an potentially significant IDE memory growth issue introduced accidentally in the last few builds where IC's server metadata index could be included once per-file in what should otherwise be a very slim file-to-metadata cache. Several other minor fixes. Also, if you are having issues with validation and code completion in Salesforce metadata XML files in 2026.1, it appears to be a regression in the base JetBrains IDE, and I've logged a bug in their public issue tracker that clearly shows the correct behavior in 2025.3 and earlier and incorrect behavior in 2026.1.

2.4.0.6 Issue 2964 - Fixed an issue where AbstractFileType files were being processed incorrectly during indexing. Issue 2965 - Fixed an issue where compiled LWC TypeScript *.js files weren't being properly added to deployment payloads. Issue 2966 - Increased the LWC TypeScript compilation timeout from 30 seconds to 5 minutes. If you still see TypeScript compilation timeouts, please let me know so that I can either raise it further or make it configurable. Issue 2968 - Prospective fix for an NPE when copy/pasting files to the IDE project. I say "prospective" because I've not been able to reproduce it, but the nature of the NPE is clear from the stack trace, and I've updated that logic to be defensive and use the original, non-null parameter value when necessary. Implemented a number of quality-of-life fixes and improvements: With the changes to IC in 2.4.0.5 to accommodate for how CLI-based connection access tokens are made available to clients, it was nece...

2.4.0.5 Salesforce CLI issue 3560 - IMPORTANT: The Salesforce CLI is in the process of implementing a set of security mitigation changes, some of them with breaking behavior . Starting with this build, IC accommodates for the changes around how connection access tokens are made available via CLI commands. For pre-2.136.8 CLI versions, IC will use continue to the org list and org display commands to get CLI-based connection access tokens; for 2.136.8+ CLI versions, IC will use the org auth show-access-token command. IC automatically determines the installed CLI version and, for efficiency, caches that value aggressively, though it should be resilient to CLI upgrades/downgrades while running. In support of Salesforce's goal of not having access tokens stored in-the-clear in the file system, IC no longer caches them persistently across IDE sessions. They are still cached aggressively in-memory, but if/when the IDE is restarted, IC will need to fetch access tokens for CLI-based ...

2.4.0.4 Issue 2951 - Added first-class support for UI Bundles and Salesforce Multi-Framework . Note that this feature requires native IDE JavaScript/TypeScript/CSS/React support, so you'll need to pair Illuminated Cloud with either a commercial JetBrains IDE or a free 2026.1+ JetBrains IDE. A demonstration video is available here. As part of this work, the Illuminated Cloud application-level settings tab LWC has been renamed UI Frameworks and now includes options for configuration of both Lightning Web Components and UI Bundles behavior. The new/changed options are: LWC Enable LWC local development - LWC local development support has existed for some time, but it wasn't possible to disable it. Now it can be disabled if desired, but it is enabled by default . Disable deploy-on-save of LWC source files when the local development server is running - This option was moved from the Deployment tab (previously called Validation and Deployment ) to be closer to its related setti...

2.4.0.3 Issue 2919  (redux) and  Issue 2955  - Improved handling of references to  *-meta.xml  files when those files are renamed, particularly in other XML files such as  package.xml  and permission sets/profiles. Issue 2949  - Prospective fix for an issue where loaded scratch org definition files in the create scratch org dialog could be based on stale cached information. Issue 2952  - Improved Apex offline debugger source position determination when stub/synthetic declarations are involved, e.g., default no-arg constructors. Issue 2956  - Fixed an issue where Apex coverage would not be displayed properly after unit test execution. Extended IC's assisted installation/configuration support for agentic AI tools to include more agentic AI JetBrains plugins and more/more recent Salesforce-specific support components. A demonstration video is available  here . In  Illuminated Cloud | Configure Application | Agentforce , the  ...

2.4.0.2 Issue 2950  - Updated the  *scratch-org-def.json  JSON schema for the latest-and-greatest settings types. Added support for aer-based profiling of executed unit tests via the  Profile " Run Configuration Name " with aer  Apex unit test executor. After aer test execution, the resulting profiling snapshot is automatically opened in the  Perfetto trace viewer  for review. Note that aer is a different Apex runtime than the Salesforce server and will have different performance characteristics, though the resulting profiling data should hopefully be directionally useful. It can, of course, also be used to understand aer-based test execution hotspots and bottlenecks. To profile org-based execution, use the Salesforce server Apex unit test profiling executor and IC's Log Analyzer. Added another aer unit test execution configuration option to add the  --skip-errors  option always when aer is executed. This option is  enabled by default ...

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.9.8 Hotfix for a few issues introduced in  2.3.9.7 : Issue 2933  - Fixed an NPE that could occur when running the Apex Offline Debugger for a full Apex unit test class. Issue 2934  - Fixed all known issues with aer-based unit test execution/debugging/coverage in projects with a namespace.