Skip to main content

Troubleshooting

Beans are missing or autowiring looks wrong​

The bean model has not been loaded. Most inspection and navigation problems come down to this. Open the Explyt Spring tool window and link a run configuration — see Native Context Mode. Until you do, the plugin falls back to static analysis, which cannot resolve conditional, profile, factory, or library beans.

The project has not been compiled. Loading the bean model requires compiled classes. Run Build → Build Project and try again.

The model is stale. After changing bean definitions, use Refresh rather than re-linking. The floating refresh button in the editor is bound to Ctrl+Shift+O (Cmd+Shift+O on macOS).

Loading the bean model fails​

Your Spring Boot version is older than 2.4. Native context mode supports 2.4 and newer out of the box. For older projects, enable the explyt.spring.native.old registry key and try again.

The application fails to start. The lightweight load still executes your application's startup path far enough to build the context. If your app cannot start — a missing environment variable, an unreachable database during context initialization — the load fails too. Check that the run configuration you linked actually starts the application normally.

The javaagent is the problem. Turn off Use javaagent to resolve beans in Settings → Tools → Explyt Spring → Spring Boot to fall back to a custom main startup method.

To see what happened, enable the explyt.spring.process.log.all registry key, which logs the full Spring output of the resolve process.

If a run configuration is renamed, replaced, or updated from version control, the plugin may report that the configuration linked to the project no longer exists. Re-link it from the Explyt Spring tool window. Recent versions restore these links automatically.

Duplicate gutter icons in IntelliJ IDEA Ultimate​

Ultimate has its own Spring support, and both can contribute markers to the same code. From IntelliJ IDEA 2026.1 the plugin suppresses its own markers when Ultimate's Spring support is active. Otherwise, disable the bundled Spring plugin in Settings → Plugins. See Compatibility.

The Beans tab is missing from Search Everywhere​

The Beans tab only appears in Spring Boot projects. If your project is not detected as one, the tab is hidden by design.

.http files will not run​

No runner is configured. Set one up in Settings → Tools → Explyt Spring → Spring Boot — see .http and .rest files.

The settings row is not visible. The HTTP CLI path field only appears when the bundled Shell Script plugin is enabled. Check Settings → Plugins.

httpYac is not found. Confirm httpyac is on your PATH and that the executable path in settings is correct.

Swagger UI does not open or requests time out​

The Run gutter icon only appears on methods whose mapping is an absolute URL. A relative path describes an endpoint your application serves, not a request to send.

For slow endpoints, raise the proxy timeout with the explyt.openapi.ui.proxy.timeout registry key; the default is 10000 milliseconds.

MCP tools are not available to my agent​

They require IntelliJ IDEA 2025.2 or newer and the JetBrains MCP Server plugin. Confirm both, and that your AI client is connected to the IntelliJ IDEA MCP Server. See MCP tools.

Stale or incorrect analysis after a large change​

Right-click the project in the Project view and choose Explyt Spring Cache Invalidation to drop the plugin's cached model and rebuild it. Changing any plugin setting has the same effect.

Registry keys​

Some diagnostics and workarounds are exposed as registry keys. Open them with Help → Find Action, search for Registry, and locate the key by name.

Registry keys are advanced settings. Change them only when troubleshooting a specific problem, and revert afterwards.

KeyDefaultPurpose
explyt.spring.native.oldfalseSupport Spring Boot versions before 2.4.
explyt.spring.process.log.allfalseLog all Spring output during the bean resolve process.
explyt.spring.root.runConfigurationfalseUse the root class from the run configuration for bean search.
explyt.spring.agent.pathemptyCustom path to the agent JAR.
explyt.openapi.ui.proxy.timeout10000Timeout in milliseconds for proxied Swagger UI requests.
explyt.openapi.download.silent.modefalseDownload from Swagger without the Save As dialog.
explyt.http.cli.urlJetBrains CDN URLSource URL for the HTTP CLI download.

Still stuck​

See also: Compatibility · Install and setup · Native Context Mode