Skip to content

Java Extension Support in the Agents Window #315572

@benibenj

Description

@benibenj

Refs:

Complexity: 5

Create Issue


Java Extension Support in the Agents Window

The goal of this test plan is to identify popular Java extensions that work well in the agents window so we can expand the extension allow list over time.

We’d like testers to try commonly used extensions for Java development and evaluate how well they function in real workflows, especially when working across multiple projects at the same time in the agents window. The focus should be on finding extensions that provide a smooth and useful experience and are good candidates to allowlist in the agents window.

At the moment, most of these extensions are not yet allowlisted by default (they will not be enabled even if you have them installed), so you’ll need to enable them manually through settings.

To test extensions:

  1. Install the extension in your default profile.
  2. Add it to the following setting:
"extensions.supportAgentsWindow": {
    "extension.id": true
}
  1. Open the agents window and try using the extensions during normal Java development workflows.
  2. Verify whether the extensions behave as expected and whether the experience feels smooth and useful in practice.

We’d especially appreciate testing of popular extensions related to:

  • Java language support
  • IntelliSense/autocomplete
  • Maven and Gradle integrations
  • Linting and formatting
  • Code navigation and refactoring
  • Spring and enterprise Java tooling
  • Testing frameworks and tooling
  • Dependency management and project management tooling

Please let us know:

  • Which extensions you tested
  • Which extensions you believe should be enabled automatically when the user has them installed

Keep in mind that the agents window currently does not support extension contributions such as:

  • Custom views
  • Status bar items
  • Debuggers

Extensions that rely heavily on those contribution points may not work well in the agents window and may not be good candidates for enablement.

You can review an extension’s contribution points in VS Code on the extension page under the Features tab.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions