Skip to main content

Quickstart

In a few minutes you will install Explyt in your JetBrains IDE, ask the agent its first question, and make your first change with a verified result.

Before you start

  • One of the supported IDEs: IntelliJ IDEA Community, IntelliJ IDEA Ultimate, Android Studio, PyCharm, GoLand, Rider, WebStorm, or PhpStorm.
  • An open project with code you understand.
  • Internet access to the plugin repository and the Explyt service.

Step 1. Add the Explyt plugin repository

  1. Open Settings (Preferences), switch to the Plugins tab, and click the settings icon.
  2. Enable Update Plugin Automatically and open Manage Plugin Repositories.
  3. Click "+" and paste the URL: https://repository.explyt.dev/

Step 2. Install the Explyt plugin

  1. Switch to the Marketplace tab.

  2. Enter Explyt.

    ⚠️ If the Explyt plugin does not appear in the search results, check that the URL https://repository.explyt.dev/ has no extra whitespace and that your IDE version is 2025.1 or newer.

  3. Click Install.

  4. Click Restart IDE and confirm the action.

If the Explyt window does not open automatically, choose View | Tool Windows | Explyt or click the Explyt button on the right-hand tool window bar. If the window still does not appear, go to installation troubleshooting.

Step 3. Choose a plan on first launch

After the restart, Explyt asks you to choose a plan: Personal, Community, or Enterprise.

  • Personal — work with the models available under an Explyt subscription.
  • Community — work with your own API key.
  • Enterprise — connect to a corporate platform using the key issued by your organization.

Complete the initial setup. A detailed comparison is available in the plans reference. Subscription and payment terms for Personal are described on the Plans and balance page.

Step 4. Ask the agent your first question

Start with a question that does not change the project. Switch the agent to Ask mode: it reads code and answers, but does not edit files or run commands, so you do not need to add "don't change anything" to your prompt.

Choosing Ask mode in Explyt

For your first question, choose Ask mode: it explores the project without changing files.

  1. Open a small file whose purpose you understand: a class, a function, or a component.

  2. Select the code and switch to the Explyt chat. The selection is added to the input field as an attachment. You can also attach a file explicitly with @file or #file.

    Selected code is added to the Explyt message as an attachment.

  3. Send the prompt:

    Explain what this code is responsible for: where the input data comes from,
    what result it returns, and which neighboring symbols I should read to verify
    the explanation. For every conclusion, name the file and the symbol.

Verify the answer against the project: open the named symbols using IDE navigation and compare the input data and the result with the signatures. A good answer relies on files and symbols that actually exist.

Step 5. Make your first change

Now give the agent a small edit. General mode is active by default: it can change files and run IDE tools, so changes to the project are a normal part of the work. You see every edit before you keep it in the project.

  1. Pick a simple, well-understood task, such as adding a documentation comment to a method or extracting a value into a constant.

  2. Attach the file you need and send the prompt:

    Add a short documentation comment to this method: its purpose, parameters,
    and return value. Do not change anything else.
  3. Review the edits in the Agent Changes panel: open each changed file, accept the edits you want, and reject the rest.

    In Agent Changes you can review every changed file and reject unwanted edits.

  4. If you want to limit what the agent may change, set an Edit Scope before sending the prompt, and shield files containing secrets with .readignore.

  5. Run the narrowest check that confirms this edit: a test for the changed method, a documentation check, or a run configuration for the affected component. For a method comment, a syntax check or a module build is enough. Expected result: the check completes without new errors and the behavior of the project does not change.

A change is accepted deliberately when you have reviewed the diff, kept only the edits you need, and got the expected result from the check.

Something not working?

What's next