Enhancements
Manage Device Authentication tokens directly from the Dashboard
Previously, Device Authentication tokens could only be managed through the command palette inside an active workspace. A new Device Auth Tokens tab is now available on the User Preferences page, allowing users to connect to GitHub using the device authorization flow (RFC 8628), view stored tokens, delete them, or reconnect without needing an active workspace session.
To support this feature, the che-server OAuth API now exposes the clientId in the OAuthAuthenticatorDescriptor, enabling the Dashboard to initiate the device flow directly. See Connecting to GitHub using device authorization in the Eclipse Che documentation.
Faster Dashboard loading with gzip pre-compression for static assets
The Dashboard now serves gzip-compressed static assets (JS, CSS, HTML, JSON, SVG), reducing network transfer size by approximately 65-75%. The total first-load payload drops from ~5-8 MB to ~1.5-2.5 MB, significantly improving load times on slower or shared cluster connections. Compression is handled at build time using compression-webpack-plugin, and @fastify/static serves pre-compressed files automatically when the browser supports gzip.
Updated Bitbucket OAuth documentation to match the new Bitbucket UI
Bitbucket Cloud updated their terminology from "OAuth consumer" to "OAuth client." The Eclipse Che documentation has been updated to reflect this change, aligning procedure steps and terminology with the current Bitbucket UI. See Configuring OAuth 2.0 for the Bitbucket Cloud in the Eclipse Che documentation.
Simplify configuring cluster roles for Che users
To reduce complexity in user permission management, the Che Operator now reconciles cluster roles for users directly, instead of delegating to che-server via the che ConfigMap. This removes the need for the legacy che-server-based workflow that was designed for the pre-DevWorkspace engine.
Bug fixes
Automatic podman login now works correctly in workspaces
Automatic podman login failed to write credentials inside workspace containers, causing private image pulls to fail with "unauthorized" errors despite having registry credentials configured in User Preferences. The root cause was that the exec WebSocket handler prematurely closed connections — it terminated after the first non-empty message and had a 3-second timer that killed the exec process before podman login could finish writing credentials. The fix lets the exec process run to natural completion.
Workspace reuse now correctly evaluates the devfilePath parameter
When using Factory Links with a devfilePath query parameter to create workspaces from different devfiles within the same repository, Dev Spaces incorrectly reopened an existing workspace based solely on the base Git URL. The workspace reuse check now includes the devfilePath value in its comparison, so distinct devfiles in the same repo correctly create separate workspaces.
AI tool CLI images updated to latest versions
The bundled AI tool container images shipped outdated CLI versions. Notably, OpenCode v1.2.27 defaulted to the no-longer-available GPT 5.3 model, causing "Model not found" errors on first launch. The CLI versions have been bumped to OpenCode v1.18.14, Claude Code v2.1.246, and Gemini CLI v0.57.0.
Improved accessibility in the Container Registry modal
Several interactive elements in the Container Registry modal used generic aria-labels that lacked sufficient context for screen reader users. Labels have been updated to be more descriptive — for example, aria-label="show" is now aria-label="Show password" and aria-label="Close" is now aria-label="Close Container Registry form" — meeting WCAG 2.2 criterion 2.4.4 (Link Purpose in Context).