feat: AI Selector Widget

[olexii4]

What does this PR do?

Adds an AI Selector widget to the Create Workspace page and integrates AI tool management across the dashboard, allowing users to pick an AI tool (e.g. Gemini CLI, Claude Code, OpenCode), save their API key, and have the tool automatically injected into workspaces.

Type Definitions

Two separate types model the AI feature:

• AiProviderDefinition — provider metadata (id, name, publisher, description, icon, docs URL). Icons and descriptions live on the provider, not on individual tools.
• AiToolDefinition — injection details (providerId as FK to provider, tag, binary, pattern, injectorImage, envVarName). The providerId follows vendor/product convention (e.g. anthropic/claude, google/gemini).

Create Workspace — AI Provider Selector

• Accordion-based UI ("Use a Default AI Provider" / "Choose an AI Provider") rendered on the Create Workspace page between Editor Selector and Import form.
• Link to "Manage API keys in User Preferences" for quick navigation.

User Preferences — AI Providers Keys

• New "AI Providers Keys" tab in User Preferences with a table listing configured API keys per tool.
• Add/Edit modal with provider dropdown and masked API key input;
• Delete confirmation modal.

Workspace Details — Overview Tab

• AiToolFormGroup section displaying the currently injected AI tool (or "None").
• Edit mode opens a radio-button modal listing all available tools with descriptions from the provider definition.
• Info modal explaining the injection mechanism and listing available tools with provider descriptions.

Workspaces List — AI Provider Column

• New "AI Provider" column in the Workspaces List table.

AI Tool Injection into DevWorkspace

• addAiToolToWorkspace() creates an init container from the tool's injectorImage, a shared injected-tools volume, and DevWorkspace lifecycle commands:
  • preStart: apply command runs the injector init container.
  • postStart: exec command symlinks the binary into PATH and optionally runs setupCommand.
• Two injection patterns: init (single binary copy) and bundle (full runtime directory with symlink).

Screenshot/screencast of this PR

What issues does this PR fix or reference?

fixes eclipse-che/che#23796

Is it tested? How?

Setting up the AI Tool Registry

The dashboard reads AI tool definitions from a Kubernetes ConfigMap at runtime. To enable the AI widgets you need to create this ConfigMap:

# Clone the AI tool images repository
git clone https://github.com/olexii4/che-ai-tool-images.git
cd che-ai-tool-images

# Set your Che namespace
NS="${CHE_NAMESPACE:-eclipse-che}"

# Create the AI tool registry ConfigMap
oc create configmap ai-tool-registry \
  --from-file=registry.json=registry.json \
  -n "$NS" \
  --dry-run=client -o yaml | \
  oc label --local -f - \
    app.kubernetes.io/component=ai-tool-registry \
    app.kubernetes.io/part-of=che.eclipse.org \
    -o yaml | \
  oc apply -f -

When no ConfigMap is found, the dashboard returns an empty registry and all AI-related UI elements are hidden automatically. To remove all AI tools:

oc delete configmap ai-tool-registry -n "${CHE_NAMESPACE:-eclipse-che}"

Manual testing steps

1. Deploy Eclipse Che with the dashboard image from this PR.
2. Create Workspace page: verify the AI Provider Selector accordion renders below the Editor Selector. Expand "Choose an AI Provider" — cards should show provider icons, names, and descriptions sorted alphabetically, navigable with arrow keys. Selecting a card and creating a workspace should inject the tool's init container, shared volume, and lifecycle commands into the DevWorkspace spec.
3. Default provider message: if the admin configures defaultAiProvider in the CheCluster CR, the "Use a Default AI Provider" panel should display the resolved provider name (e.g. "The default AI provider "Gemini" configured by your administrator will be used.").
4. User Preferences → AI Providers Keys tab: add an API key for a tool — verify the secret is created in the user namespace with correct labels (che.eclipse.org/ai-provider-id, controller.devfile.io/mount-to-devworkspace, controller.devfile.io/watch-secret) and annotation (controller.devfile.io/mount-as: env). Update and delete the key. Verify the "Key configured" badge updates on the Create Workspace gallery cards.
5. Workspaces List: verify the "AI Provider" column shows the injected tool icon and name for workspaces that have an AI tool, and "-" for those without.
6. Workspace Details → Overview tab: verify the AI Tool section shows the current tool or "None". Click the info icon — verify the modal shows tools with provider descriptions. Click edit, select a different tool, save — verify the DevWorkspace spec is updated. When no tools are configured, verify the empty-state message is shown.
7. Workspace runtime: start a workspace with an injected tool (e.g. Gemini CLI). Open a terminal in the editor container and verify the tool binary is available in PATH (e.g. which gemini). Verify the API key env var is set (e.g. echo $GEMINI_API_KEY).
8. Empty registry: delete the ai-tool-registry ConfigMap and verify that the AI Provider Selector on the Create Workspace page, the AI Provider(s) column in the Workspaces List, and the AI Providers Keys tab in User Preferences are all hidden.
9. AI tool injection (Gemini CLI): on the Create Workspace page, select "Gemini CLI" as the AI Provider. Create a new workspace from any sample (e.g. Go). Wait for the workspace to start and the IDE to load. Open a terminal in the IDE and run gemini — verify the Gemini CLI starts (or prints its help/version output), confirming the AI tool binary was injected into PATH.
10. AI tool injection (Claude Code): repeat step 9 but select "Claude Code" as the AI Provider. In the terminal, run claude — verify the Claude Code CLI is available.
11. Multiple AI tools: on the Create Workspace page, expand "Choose an AI Provider" and select multiple providers (e.g. both Gemini CLI and Claude Code). Create a workspace, open a terminal, and verify both gemini and claude commands are available. Check the Workspaces List — the "AI Provider(s)" column should show icons for both tools.

Release Notes

Docs PR

eclipse-che/che-docs#3062

[che-bot]

Click here to review and test in web IDE:

[github-actions]

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1505 (linux/amd64, linux/arm64)

kubectl patch command

kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1505", name: che-dashboard}]}}]"

[github-actions]

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1505 (linux/amd64, linux/arm64)

kubectl patch command

kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1505", name: che-dashboard}]}}]"

[github-actions]

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1505 (linux/amd64, linux/arm64)

kubectl patch command

kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1505", name: che-dashboard}]}}]"

[github-actions]

Docker image build succeeded: quay.io/eclipse/che-dashboard:pr-1505 (linux/amd64, linux/arm64)

kubectl patch command

kubectl patch -n eclipse-che "checluster/eclipse-che" --type=json -p="[{"op": "replace", "path": "/spec/components/dashboard/deployment", "value": {containers: [{image: "quay.io/eclipse/che-dashboard:pr-1505", name: che-dashboard}]}}]"

[ibuziuk]

@olexii4 let's add the Tech preview label to the widget, similar to what we have on devfile samples:

[dmytro-ndp]

I have a few questions:

1. there are also codex CLI and Copilot CLI available in the Market. Should we support them as well?
2. do you need AI CLI owner agreements to place their tile in the User Dashboard?
3. will there be team wide API keys supported which covers several accounts?