Explyt AI actions
AI-assisted conversions that automate routine Spring work inside the IDE: generating entities from a database schema, DTOs from entities, OpenAPI from controllers, and .http requests from cURL. The assistant proposes the result in chat and may ask clarifying questions, so you review before anything lands in your project.
Requirements. Two plugins must be installed: Explyt Spring and the Explyt AI assistant plugin, available from explyt.ai or the JetBrains Marketplace. Works with OpenAI-compatible providers and local models; output quality depends on the model you choose.
These actions are distinct from the MCP tools. MCP tools expose your Spring project's structure to external AI agents. The actions on this page are AI-driven commands you invoke yourself from the editor.
How to invoke them
From the right-click menu. In the editor or the Project view, right-click a file and choose Explyt Spring AI Actions, then pick a conversion. You can select several files at once for the DTO and entity conversions.
From the gutter. An AI assistant icon appears next to annotated class declarations, offering the actions relevant to that class.
Data and JPA
| Action | What it does | Where |
|---|---|---|
| Convert Liquibase/Flyway File to Entity | Generates JPA entity classes from a Liquibase, Flyway, or plain SQL schema file. | Right-click a migration or SQL file |
| Convert Entity to Db Script | The reverse direction. Detects the application's database and migration tool and generates a matching migration script. | Right-click an entity, or the gutter on an entity class |
| Convert Entity to DTO | Generates DTO classes from JPA entities. The model can exclude fields or add validation annotations on request. | Right-click an entity, or the gutter on an entity class |
| Convert DTO to Entity | The reverse direction — JPA entities from DTO classes. | Right-click a DTO |
Looking for
equalsandhashCodeon an entity? That generator is not AI-driven and does not need the AI plugin — it ships in Explyt Spring under Code → Generate. See Code generation.
Web and API
| Action | What it does | Where |
|---|---|---|
| Convert Spring Controller to OpenAPI File | Analyzes a controller's endpoints, parameters, and DTO models, then generates an OpenAPI specification. | Right-click a controller, or the gutter on a controller class |
| Convert OpenAPI File to Spring Controller | The reverse direction — scaffolds Spring REST controllers from an OpenAPI spec, which is useful when integrating a third-party service. | Right-click an OpenAPI file |
HTTP requests
| Action | What it does |
|---|---|
| Convert Curl to Http | Converts a cURL command into an RFC 7230 request and appends it to an HTTP file. |
| Convert Postman Collection to Http | Converts an entire Postman collection into RFC 7230 requests. |
Run the resulting files with the built-in runner — see .http and .rest files.
Configuration formats
| Action | What it does |
|---|---|
| Convert Properties to YAML | Converts a Spring .properties file to YAML, preserving comments. |
| Convert YAML to Properties | The reverse direction. |
Spring Initializr generates
application.properties. If your team standardises on YAML, this converts it in one step. A non-AI version of the same conversion is available in the editor popup menu without the AI plugin — see Code generation.
Further reading
- Neural networks in Spring development: eliminating routine, not intelligence (in Russian)
- Explyt AI platform and integrated agents (in Russian)
See also: MCP tools · Code generation