Tool windows

Explyt Spring adds two tool windows: Explyt Spring for beans and contexts, and Explyt Endpoints for your API surface.

Explyt Spring

The Explyt Spring tool window is docked on the right. It is the entry point for Native Context Mode and shows the bean model once it has been loaded.

Toolbar actions

Action	What it does
Link Spring Boot Project From selected RunConfiguration	The + button inside the tool window. Associates a run configuration with the native bean model.
Link Explyt Spring Boot Project From RunConfiguration	The same operation from the main IDE toolbar, next to Build and Search Everywhere.
Detach All Spring Boot Projects	Drops the loaded model for every linked project.
Bean Analyzer	Opens the dependency analyzer for the current context.
Enable Spring Debug / Disable Spring Debug	Toggles the Spring debug mode described in Spring Debugger.
Refresh	Re-reads the bean model. This is the platform's standard external-project refresh.

Linking a run configuration compiles the project and loads all bean definition information into the tool window. The gutter marker that starts this describes it as "Load all bean definitions info to Explyt Spring Tool Window (Required compile)"; a compile is required because the plugin reads metadata from compiled classes.

To re-read the model after changing code, use Refresh rather than re-linking. A floating refresh button can appear in the editor for this, bound to Ctrl+Shift+O (Cmd+Shift+O on macOS). You can turn that button off in Settings.

The plugin README and some older articles call this step "Load Beans". There is no button with that label in the IDE — linking a run configuration is what triggers the load.

How beans are grouped

Once loaded, beans are organized into a tree with these nodes:

Project Beans · Library Beans · Components · Configurations · Auto Configurations · Controllers · Services · Repositories · Configuration Properties · Message Brokers · Aspects · Method beans · Profiles · Use for DI · Others

Double-click any bean to navigate to its declaration. The split between Project Beans and Library Beans matters: library beans come from your dependencies, and because Explyt reads the real context, they participate in autowiring checks like any other bean.

Explyt Endpoints

The Explyt Endpoints tool window collects your entire API surface in one navigable view:

• Spring MVC and WebFlux endpoints
• Router functions, including Kotlin coRouter
• Message broker listeners such as @KafkaListener and @RabbitListener, in IntelliJ IDEA 2025.2 and newer
• JAX-RS resources in Quarkus projects

Toolbar

Control	What it does
Search	Filters the tree by text.
HttpType	Filters by HTTP method.
EndpointType	Filters by endpoint kind, such as Spring MVC, WebFlux, or JAX-RS.
Refresh	Rebuilds the endpoint list.
Expand All / Collapse All	Expand or collapse the tree.

Click an endpoint to jump to the handler method. Endpoints with an absolute URL also carry a Explyt: Open in Swagger UI gutter action — see Swagger UI client.

Finding beans without the tool window

Press Shift twice to open Search Everywhere and switch to the Beans tab to jump to a bean by name. The tab appears only in Spring Boot projects.

See also: Native Context Mode · Quickstart · Spring Debugger