2.3.9.5 release notes

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 invalid element. I'm continuing to work with the reporting user to try to determine and fix the root cause.
• Integrated the Salesforce CLI's Agent Script syntax validator as an external annotator and bulk code inspection, Salesforce | Agent Script Validator. This should provide quite decent client-side static code analysis for *.agent files with the following restrictions/limitations:
  • Because the validator is an external Salesforce CLI command, only files that are completely saved to disk can be validated. As a result, the external annotator will not report results for unsaved files. As soon as the file is saved to disk, the validator is executed (if enabled), and results are displayed directly in the editor.
  • For the same reason, results may lag by a second or so while the validator is executed after opening or saving a *.agent file.
  • The validator is only executed for *.agent files under a configured source root that are not ignored via .forceignore.
  The enablement of this feature is controlled by the aforementioned Salesforce | Agent Script Validator inspection in the project's inspection profile. If you're not seeing results, make sure that is enabled; if you'd prefer not to see results, you can of course disable it.
• The IDE's copy keyboard shortcut — typically Ctrl+C on Windows/Linux and Cmd+C on Mac — now copies the details for the selected connection in IC's connection manager to the system clipboard as both HTML (the exact same information displayed in the connection tooltip) and plain text. I honestly added this mostly for myself to make it simpler to grab things like the org ID and instance name for a connection when working with Salesforce on issues observed in specific orgs, but hopefully it will prove useful for other IC users as well. In the process of doing this work, I also improved the connection detail information to be more complete and consistent across connection types.
• Implemented several improvements to Spring '26 complex template expression completions and references.
• Messages tool window tabs for external annotators such as Salesforce Code Analyzer and Agent Script Validator are no longer selected aggressively. They are still populated, but you must explicitly select them to see the respective command-line execution results. Other Messages tool window tabs for more critical operations such as metadata deployment and retrieval now take precedence and are automatically selected/focused as appropriate.
• Renamed the new project wizards to Illuminated Cloud (metadata format) and Illuminated Cloud (source format) for creating metadata format/traditional and source format/Salesforce DX projects respectively.
• Fixed an issue with opening local files in the default browser on Windows, e.g., after IcApexDoc generation, code coverage report export, and Mermaid diagram export.