Illuminated Cloud Announcements

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