6 May 20263 min read

Explyt 5.10: Cross-Tool Skills and Quick Docs in Chat

Explyt TeamPublished 6 May 2026

Media

1 image

Explyt 5.10 makes the agent more integrated with your IDE workflow. It can now reuse Skills from dot directories used by other AI tools so that existing instructions can work across assistants, and show better hints for code and file links in chat, making it easier to view documentation or signatures without losing context.

Skills from All Vendors’ Dot Directories

Explyt now searches for Skills not only in .explyt/skills/*/SKILL.md, but also in .*/skills/*/SKILL.md inside other dot directories, such as .claude.

This makes it easier to reuse Skills and instructions that are already stored in the configuration folders of other AI tools. You no longer need to copy the same Skill into .explyt just to make it available to the agent.

Recognized configuration roots are highlighted in the project tree, so you can clearly see which directories Explyt has detected and where the Skills are coming from.

This is useful when a team uses different AI assistants and does not want to copy and paste Skills for each tool. A Skill maintained in one tool’s configuration folder can now be reused by Explyt as part of the same project setup.

Quick Documentation in Chat

Quick Documentation in Chat

We improved the hints for links to code and files in chat.

When the agent refers to a class, method, or file in its response, you can quickly view related documentation, a signature, or the file path without leaving the chat. This helps you understand the referenced code faster and reduces context switching while working through a conversation with the agent.

This is especially helpful in longer chats, where the agent may mention several files, methods, or classes, and you want to check what they are without interrupting your flow.

Reproduce, inspect and fix inside JetBrains IDEs, with the debugger, run configurations and IDE facts as evidence.

Newsletter

Get Explyt updates in your inbox

Release notes, engineering deep dives, and new articles like this one. No spam, unsubscribe anytime.

Comments

Loading comments...

Keep reading

All articles

Why choose Explyt?

Feature

Debugger

Yes

Ultimate only

No

No

No

No

SAST vulnerability scanner

Yes

No

No

No

No

No

IDE refactorings (Rename, Change Signature…)

Yes

No

No

No

No

No

Test coverage guarantees

Yes

Coverage gates

No

No

No

No

No

Semantic code model (types, find-usages)

Yes

Full code model

Yes

LSP

No

LSP

No

Reads dependency source

Yes

No

LSP

No

No

No

Auto-review of generated code

Yes

Via verify

/review

PR only

No

No

Context compression

Yes

No

Yes

No

No

Yes

Multi-IDE support

JB only

JB only

Yes

Yes

Yes

Yes

Pricing (all top models)

$15-200/mo

Credit-based

$20–200/mo

$20–60/mo

$10–39/mo

BYOK

What IDE-native AI feels like

What impressed me most is how well the agent understands the existing project. Its plans fit naturally into what is already built, even when I am working outside my usual tech stack.

Mariya Remenyuk
Mariya Remenyuk

Senior Analyst Developer · DXC Technology

LSP gives an agent coordinates; the full IDE gives it the project model. That native IDE context makes all the difference on real Java code.

Akiner Alkan
Akiner Alkan

Software Architect & AI Board Lead · Siemens

IDE-native stepping makes the difference on stateful Java applications.

Masaood
Masaood

Software Engineer

Webinar: Working with AI Tools at the User Level

Methodology, SDD + TDD, feedback loops, and subagents — a practical framework for getting predictable results from AI coding agents. For senior Java developers and team leads using JetBrains IDEs.

Explyt 5.20

Explyt 5.20: stop waiting in the chat — a background task panel and notifications outside the IDE

Frequently Asked Questions

Getting Started

IDE Integration & Workflow

How Explyt Compares

Models & BYOK

Pricing & Billing

Privacy & Security

Explyt 5.10: Cross-Tool Skills and Quick Docs in Chat