Illuminated Cloud Announcements

2.4.2.4 Issue 2980 - IC now displays the project's .aerrc file contents, if present, in the Apex test run configuration editor so that it's obvious exactly what command-line options will be used when executing Apex tests via aer. It's still possible to configure additional aer command-line options on a per-run config basis in the run configuration editor as well. Issue 2924 - Added a new deployment Apex test level, RunDependentTests , that is conceptually similar to RunRelevantTests , but the set of tests to be executed is computed by IC before deployment — and then executed using the RunSpecifiedTests test level — instead of being computed by the Salesforce server. There are notable differences in how IC computes transitive dependents vs. how Salesforce computes them (at least at present): IC specifically computes dependent relationships with member-level granularity whereas Salesforce computes them with class-level granularity. This means that if an intermediate dep...

2.4.2.3 Issue 2885 - Added support for additional decomposed metadata types . As with the underlying feature, this support is beta . If you encounter issues with it, consider disabling optional decomposition and please report those issues to Salesforce or IC as appropriate. Issue 2936 - Added support for both types of edition values in project-scratch-def.json files. Values are still written in the documented form when scratch org definition files are written by IC. When Apex Execution Runtime (aer) is used for Apex code coverage, IC now uses the covered line information instead of computing its own set of executable lines. The tooltip for the Salesforce skills Update button in the Agentforce configuration tab now includes details about the nature of the recommended update, e.g., the installed and available version date/time stamps. Improved the offline symbol table generator's support for ExternalServiceRegistration classes which can sometimes yield HTTP 500/Internal Serve...

2.4.2.2 Issue 3011 - Prospective fix for an IDE freeze during initial dynamic file type determination. The Apex Unresolvable Reference code inspection now verifies property accessor visibility based on the reference context with write expressions being checked against the property setter and read expressions being checked against the property getter. This becomes particularly useful in Winter '27 where the Apex Symbol API includes property getter and setter visibility information for properties of system types. The Apex Annotation and Modifier Agreement code inspection now flags property accessors with higher visibility than their containing properties as errors with quick fixes to adjust the property or property accessor visibility to a valid value relative to the other.

2.4.2.1 Removed support for JetBrains 2025.2 IDEs. Please make sure that you're using 2025.3+ (ideally the latest-and-greatest which is currently 2026.2.2) for continued IC plugin updates. Issue 3019 - Fixed a problem with commas in ApexDoc @see description text being interpreted incorrectly as a comma-delimited list of targets. Issue 3020 - Fixed a potential deadlock calculating the server time offset during the first Deploy Modified Metadata action against a specific connection after starting the IDE. Added support for per-test code coverage in aer. This is accessed using the IDE's standard per-test coverage feature. Note that you must be using aer 1.4+, and you must explicitly enable the feature in Illuminated Cloud | Configure Application | Apex | Apex Execution Runtime (aer) | Enable coverage by test . Integrated broad improvements in the OST's Apex system types based on the upcoming Apex Symbol API . In this version, IC does not yet use that API - it will be ...

2.4.2.0 This is a quick hotfix for a regression introduced in 2.4.1.9 . I've primarily been working closely with Salesforce to validate the upcoming Apex Symbol API as a way to improve the fidelity and performance of IC's OST generation. Issue 3018 - Fixed a regression where Compare With Server on a single file would result in multiple diffs being shown including the selected file and the intermediate temporary directories. Note that support for 2025.2 JetBrains IDEs will be removed soon, likely in next week's build. Please make sure that you're using 2025.3+ for the best experience going forward.

2.4.1.9 Issue 2983 - When rerunning individual test classes or methods from the test results tool window, the test execution engine that produces those results, either Salesforce org or aer, is used to filter the available test execution actions. Note that the IDE's default test executor cannot be filtered and is always offered, but if selected within a short time after showing the context menu for a test class or method in the test results view, the test execution engine for that view will be used. Issue 3008 - If a metadata retrieval is requested for immediate population of project files (as opposed to retrieve-for-merge or compare-with-server) and its payload includes files that were not explicitly part of the original request, also exist locally in the project, and are different from their local counterparts, the user is now notified and retrieve-for-merge behavior is used to allow careful reconcilation of these unrequested changes. Issue 3012 - Improved the previously-stubb...

2.4.1.8 Issue 2957 - Fixed an issue where errors could occur when adding/removing Apex offline debugger server-side checkpoints. Issue 3002 - Fixed an issue with @NamespaceAccessible symbols from installed managed packages with the same namespace as the org not being properly rendered into the OST. Note that you must regenerate your OST to see the effect of this fix. Issue 3003 - Fixed an issue where file copy/paste-for-overwrite in the IDE could result in IC prompting to remove the corresponding metadata files from the subscription and org. This is because the IDE actually does remove the original files and create new replacement files. IC now ignores the file removal events in this specific scenario. Issue 3004 - By default large numeric values are returned by the SOQL and SOSL query APIs in scientific notation , and the SOQL Query and SOSL Query tool windows simply show the returned data. Now those tool windows include a configuration option, Convert scientific notation value...

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 ...