2.4.0.5 release notes

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 connections using the respective CLI command(s) when first needed and again, of course, when they become stale.

    Additionally the option Illuminated Cloud | Configure Application | GraphQL | Include connection information now defaults to disabled, though you can always enable that option if you'd like, understanding that it will result in the current CLI connection's access token being written to the project's graphql.config.yml file.

    IC should not be including CLI access tokens in idea.log unless debug logging is explicitly enabled by the user for the respective logging channels. It is, of course, recommended that such debug logging only be enabled as required for diagnostic purposes and disabled again when no longer needed.

  • Issue 2959 - Fixed an issue where Apex test failures that weren't directly attributable to an executed test class and/or method weren't being included in the test results when executed synchronously.

    While working on this, I fixed a number of other issues with failed test status attribution when the API's test results failed to include complete attribution information. This should result in much better diagnostics for Apex tests which fail due to transitive issues such as inconsistent server-side Apex compilation state, particularly with asynchronous test execution.

  • Issue 2960 - Improved error handling when an MCP servers JSON file fails to load/parse.
  • Issue 2962 - Implemented a set of prospective fixes/improvements for some freezes/slow-downs that users have reported. If you continue to see such problems, please let me know so that I can gather diagnostic information and address them.
  • Fixed an issue with a breaking API change in LSP4IJ. If you see issues with LSP4IJ, please make sure that you have the latest plugin version installed.
  • Fixed a potential IndexNotReadyException during deployment.
  • Fixed an issue with Agentforce for Developers inline completions due to a breaking API change.
  • Fixed a "Reentrant indexing" issue that could occur when building the Apex derived declarations indexes. Note that in the process of verifying these changes, I noticed that the IDE is sometimes showing duplicate line markers for inheritance relationships. I've logged a corresponding bug with JetBrains.
  • Added a few metadata types to metadata.xsd observed as missing/undefined in open source reference/test projects.
  • Added reference support for invocable variable targets in *.invocableactionextension-meta.xml files.
  • Implemented numerous new project wizard UX improvements and refinements.
  • Improved performance of Apex test/tested related class navigation.
  • Improved IC intention categorization in Settings | Editor | Intentions.
  • Another set of under-the-hood improvements and optimizations.

Other news

  • The next two major items on my plate are (still):
    • Salesforce Summer '26 updates to ensure they're ready for the final platform release in a bit under a month.
    • Moving the public issue tracker and IC user guide from Bitbucket to GitHub well before the August 20, 2026 deadline.