Automatic Error Reports enabled in 2026.3 release

Starting with the 2026.3 release, JetBrains IDEs send error reports to JetBrains automatically by default. This FAQ explains what the IDE sends, how it removes sensitive data, and how you can control the feature.

General

What changes?

The IDE sends reports about exceptions and UI freezes to JetBrains automatically. These reports come from the IDE, its bundled plugins, and plugins that JetBrains owns. The IDE does not show these errors to you, and you do not need to send them manually.

Why does JetBrains do this?

Users do not report many errors manually. Automatic reports let JetBrains find and fix problems faster, also problems that users do not report.

Which products does this apply to?

It applies to JetBrains IDEs that JetBrains s.r.o. builds and distributes.

It does not apply to:

• Android Studio.
• IDEs from other vendors that use the IntelliJ Platform.
• An IDE that runs in headless mode, for example, a command-line inspection or a build on a CI server.

Which errors does the IDE send?

The IDE sends:

• Exceptions in the IDE platform.
• Exceptions in bundled plugins and in plugins from JetBrains.
• UI freeze reports (CPU snapshots, thread call stack dumps)
• Out Of Memory summary reports (not heap dumps, only short text summary with class instances histograms)

The IDE does not send exceptions from third-party plugins to JetBrains. A third-party plugin vendor can use the JetBrains Marketplace error reporter. In that case, the IDE sends the exceptions of that plugin to JetBrains Marketplace automatically, for the plugin vendor.

How do I know that the feature is on?

Each user gets a notification about it:

• An existing user sees the "Automatic error reporting is now on" notification one time.
• A new user sees "Error reports are sent to JetBrains automatically" on the Welcome screen.

To see the current state, open Settings | Appearance & Behavior | System Settings | Data Sharing. Look at the Send error reports to JetBrains automatically option.

Data and Privacy

What data does a report contain?

A report contains:

• The error message and the stack trace.
• The product name, the version, and the build number.
• The OS name and version, the CPU architecture, the number of CPU cores, and the Java runtime version.
• The anonymous exception reporter ID of the machine.
• The ID, the name, and the version of the plugin that caused the error.
• The ID of the last action that you used in the IDE.
• The IDs of installed non-bundled plugins that are published on JetBrains Marketplace.
• The update channel of the IDE.

A report does not contain your JetBrains Account e-mail or your license data.

How does the IDE remove sensitive data?

Before the IDE sends an exception, it masks sensitive data in the error message and in the stack trace. The IDE replaces each masked fragment with the <redacted> marker.

The IDE masks these types of data:

• File paths and file URLs.
• Web URLs and JDBC connection strings.
• E-mail addresses, phone numbers, and credit card numbers.
• IP addresses, MAC addresses, host names, and the name of your computer.
• Your OS user name, and user names in user=... or login=... fragments.
• Passwords, secrets, API keys, access tokens, and authorization headers.
• Known token formats, for example, GitHub, GitLab, Slack, AWS, and Google tokens, and JWTs.
• SQL statements.
• Values of environment variables.
• UUIDs.

The IDE keeps the stack frame lines, for example, at com.example.Foo.bar(Foo.kt:42). These lines contain only the names of IDE classes and methods.

Masking uses patterns and works on a best-effort basis. It cannot find all possible sensitive data. If you cannot accept this risk, turn off the feature. Refer to Control for Companies.

Does the IDE send my source code or my files?

No. In release builds, the IDE sends no attachments with an exception. Code fragments and arbitrary files are attachments, so the IDE does not send them.

For a UI freeze, the IDE sends only these attachments:

• The freeze report.
• The thread dumps of the IDE.
• The CPU snapshots of the freeze.

These files contain the state of IDE threads during the freeze. They do not contain the text of your files.

Do EAP builds behave differently?

Yes. EAP builds are for early testing, so the IDE sends all attachments of a report. The IDE masks the error message and the stack trace in EAP builds too.

Where does the IDE send the reports?

The IDE sends the reports over HTTPS to ea-report.jetbrains.com. Reports for third-party plugins go to exceptions.marketplace.jetbrains.com. The IDE uses the proxy settings that you set in the IDE.

What happens when the IDE has no network connection?

The IDE keeps the reports in memory and tries to send them again later. The time between attempts increases, up to two hours. The IDE does not save unsent reports to disk. When you close the IDE, it deletes them.

Does the IDE send the same error more than one time?

No. The IDE sends each exception one time per IDE session. The IDE sends each UI freeze separately.

How can I find the reports from my machine?

Open Help | About. The dialog shows the Exception reporter ID of your machine. The IDE also writes this ID to idea.log. Provide this ID to JetBrains support to help them find or remove your reports.

Control for Users

How do I turn off automatic error reports?

1. Open Settings | Appearance & Behavior | System Settings | Data Sharing.
2. Clear the Send error reports to JetBrains automatically option.

Does this setting apply to all my JetBrains IDEs?

Yes. The IDE saves this setting for your OS user account on the machine. All JetBrains IDEs of this user account on this machine use the same setting. The IDE keeps it in the consentOptions/accepted file in the JetBrains common data directory:

• Windows: %APPDATA%\JetBrains
• macOS: ~/Library/Application Support/JetBrains
• Linux: ~/.local/share/JetBrains

Can I still report an error manually?

Yes. Manual reporting continues to work as before. When automatic reports are off, the IDE shows UI freezes, and you can report them manually. For exceptions, refer to the next question.

I turned off the feature. Why do I not see the IDE errors?

In release builds, the IDE does not show exceptions from the IDE platform and bundled plugins. This is also true when automatic reports are off. The IDE writes these exceptions to idea.log.

To see these exceptions in the IDE again, add this VM option:

-Didea.fatal.error.notification=enabled

Control for Companies

You can control the feature for the IDEs that your company provisions. Add a VM option to the configuration of these IDEs. For example, add it to the .vmoptions file of the IDE, or set it in your provisioning tool.

We do not want to send any errors. What do we do?

Add this VM option:

-Dea.auto.report.allowed=false

The IDE does not send any reports automatically. The IDE does not show the option in the Data Sharing settings. Users can still report errors manually.

We do not want to send exceptions, but we agree to send UI freezes. What do we do?

Add this VM option:

-Dea.auto.report.forced=FREEZES

With this option:

• The IDE sends only UI freeze reports automatically.
• The IDE does not send exceptions automatically. Users see the exceptions in the IDE and can report them manually.
• Users cannot turn off the freeze reports. The IDE does not show the option in the Data Sharing settings.
• Users do not get the notification about automatic reports.

We want to work with JetBrains on errors and freezes that are important to us. What do we do?

Contact us.

JetBrains support can give you a tag for the reports from your company. Add the tag to your provisioned IDEs with this VM option:

-Dea.auto.report.forced.tag=<your-tag>

The IDE adds the tag to each automatic report. This helps JetBrains find and analyze the reports from your company.