Illuminated Cloud Announcements

2.3.9.6 Issue 2922  (partial) - Implemented a few more fixes for  PsiInvalidElementAccessException  instances that I observed in my own work. I'll continue to try to track down the root cause of these invalid elements, but minimally I'm trying to be defensive against their presence and allow for recovery when possible. Issue 2925  - Corrected the data type of  ConnectApi.CdpQueryOutputV2.metadata . Note that the OST must be regenerated to see the effects of this change. Issue 2926  - Made IC's file type overriders — used for metadata files with a single extension but multiple MIME types, e.g., static resources, content assets, email templates, and documents — much more selective about files for which they try to determine a file type. All files must pass the following gates: Must be under a configured, deployable source root. Resource roots are  not  considered source roots for this check. Must be in an IC module/project. Additionally the file typ...

2.3.9.5 Issue 2918  - Added the  namespace  value from  sfdx-project.json  as a read-only field in the scratch org creation dialog when creating in the context of a source format project with a populated  namespace  value. Note that with this change, the  No Namespace  checkbox is only visible when a namespace is present in  sfdx-project.json , and enabling that option also hides the  Namespace  field (and vice-versa). Issue 2919  - Fixed an issue that could occur when renaming Apex classes/triggers via the file rather than the class/trigger name where non-Apex references to that name, e.g., in a  package.xml  file, would be incorrectly updated with the file name instead of the class/trigger name. Issue 2922  (partial) - Protected against a potential invalid element access exception when trying to find the module for a cache dependency. Unfortunately this is still a downstream behavior of the original invali...

2.3.9.4 Issue 2907  - Spring '26 / API v66.0 update Updated the SOAP client for API v66.0. Updated the API version used for primary communication with Salesforce APIs to 66.0. Added 66.0 as an available API version number for configured connections. Updated  metadata.xsd  based on the API v66.0 Metadata API SOAP WSDL. Updated the OST version number to prompt regeneration for system API changes in Spring '26. Updated the bundled  completions?type=apex  Tooling REST API response to be based on the API v66.0 REST endpoint. Updated Visualforce, Aura, and LWC components, functions, modules, etc., for Spring '26 changes. Note that I have not yet reconciled IC's own LWC TypeScript definitions with the latest from  @salesforce/lightning-types  but I do plan to do that shortly. If you're running into issues with some incompatibility between the two, please let me know about the specific instance(s) and I'll fast-track those. Updated the bundled SLDS CSS and SVG...

2.3.9.3 Issue 2895  - Implemented a number of editor enhancements for Agent Script: Added context-aware code completions and references for most internal relationships, e.g., variables, inputs, outputs, topics, utils, etc., and external relationships, e.g., Apex and Flow targets. Added references allow bidirectional navigation, i.e., go to declaration and find usages. Improved completion insert handlers for certain token types, e.g., adding a space after the colon when inserting a standard label, and also removing the unnecessary trailing space if the user types  Enter  immediately to specify label data in a sub-block. Added a new code inspection,  Agent Script unresolvable reference , that flags unresolvable references in  *.agent  files as errors. Added several missing Agent Script keywords and recategorized some tokens that were incorrectly categorized previously. Added support for structure view in  *.agent  files. Fixed issues with deployment...

2.3.9.2 Issue 2895  - Added support for Agent Script and AI authoring bundles. Note that this doesn't include a full parser/validator for the Agent Script language, but it does include the following: Explicit support for the  AiAuthoringBundle  metadata type including as a known bundle type. This also includes proper cross-correlation of  *.agent  files and peer  *.bundle-meta.xml  files for the tabbed editor UI, project view nesting rules, navigate-to-related-files functionality, etc. Fixes for several issues deploying and retrieving  AiAuthoringBundle  metadata. New  File | New | Agent Script  action for creating a valid  AiAuthoringBundle  directory with a file template-based  *.agent  file. Salesforce's TextMate bundle for Agent Script files associated with the  *.agent  file extension automatically. The JetBrains TextMate Bundles plugin must be installed and enabled for this to work properly. Simpl...

2.3.9.1 Issue 2888  - Added limit information to record lookup nodes in Flow diagrams when present in a Flow metadata file. Issue 2906  - Fixed an issue with Apex code completions in some compile-time field constants, specifically those of the form  Schema. SObjectTypeName .fields. fieldName . Issue 2909  - Fixed an issue with the signature of  lightning/uiRecordApi.notifyRecordUpdateAvailable() . Updated the bundled Salesforce rules for Cline and Kilo Code. They can be updated via  Illuminated Cloud | Configure Application | Agentforce | Agentforce Vibes  using the respective  Update  rules buttons. If you haven't customized these rules, it's safe to overwrite; otherwise you'll want to merge with your own versions carefully. Hopefully finally fixed the lingering long-running read action during population of  .illuminatedCloud/lwc/types , primarily noticed after indexing completes when first opening a project. Prospective fix for another...

2.3.9.0 Implemented several fixes and improvements for the Apex offline debugger: Issue 2899  - Fixed a potential  AbstractMethodError  during offline Apex debugging due to a breaking plugin SDK change. Issue 2900  - Added recovery for some instances of unbalanced stack frames found in Apex debug logs. This issue has been reported to Salesforce so that it can be fixed properly, but hopefully this recovery mechanism will allow logs with such issues to be used properly. Fixed a few issues with the  Step Out  action so that it should no longer execute the rest of the process when trying to step out of a single method. Improved  Smart Step Into  functionality, particularly how it determines which invokables should be offered for the current statement. Debugger variables are now sorted by last modified descending by default so that the most recently-changed variables appear at the top of the list. This is more in line with how JetBrains' debuggers for ...