Jonas Helming, Maximilian Koegel and Philip Langer co-lead EclipseSource, specializing in consulting and engineering innovative, customized tools and IDEs, with a strong …
Eclipse Theia 1.76 Release: News and Noteworthy
October 8, 2026 | 11 min ReadWe are happy to announce the Eclipse Theia 1.76 release! The release contains in total 51 merged pull requests. You can now use your GitHub Copilot subscription with the current Copilot model lineup in Theia AI, both in the Theia IDE and in custom tools built on the platform. Other highlights include automatic model discovery, AI-generated commit messages, and an external API for AI sessions. In this article, we will highlight some selected improvements and provide an overview of the latest news around Theia.
Join us at TheiaCon 2026! Connect with the Theia community and learn how others build tools and IDEs with Theia. Visit the TheiaCon website to register to attend.
For those new to Eclipse Theia, it is a platform for building IDEs and tools for the web or desktop, based on web technologies. With Theia AI, the open-source, vendor-neutral AI harness platform that is part of Theia, you can also build AI-native tools and IDEs. For more details about Eclipse Theia, please refer to this article and visit the Theia website.
The Theia project also releases a product, the Theia IDE. The Eclipse Theia IDE is an AI-native, open IDE for cloud and desktop environments, aimed at end users. It is based on the Theia platform and lets you bring your own API key or subscription and connect any model. See What Is Eclipse Theia (AI)? for an overview. For more details, see the Theia IDE website.
If you are looking for a simple way to check out the new release, please download and install the Theia IDE, which is based on Theia 1.76.
Eclipse Theia 1.76: Selected features and improvements
In the following, we will highlight some selected improvements in the new release. As usual, we cannot mention all 51 merged pull requests, so we focus on changes visible to end users and relevant to adopters. The corresponding pull requests are linked under the respective heading when applicable.
Use Your GitHub Copilot Subscription in Theia AI
Your GitHub Copilot subscription now gives you access to the current Copilot model lineup in Theia AI. Theia’s agents can use the models available to your account through the official Copilot CLI. In the Theia IDE, you can choose these models to power your AI chats and coding tasks, including calls to Theia’s agent tools. Image attachments are supported too, for models that accept images.
For adopters building AI-powered tools, this means their users can bring an existing Copilot subscription to the application’s own agents. The @theia/ai-copilot provider connects those agents to Copilot models while retaining the prompts and tools defined by the Theia AI application. This capability is available to custom tools built on Theia AI, as well as to the Theia IDE.
The integration uses the official GitHub Copilot CLI, which must be installed on the backend host, for example with npm install -g @github/copilot. Theia does not bundle it. If it is not found automatically, set ai-features.copilot.executablePath. Then sign in through Theia’s Copilot sign-in dialog with an active subscription; users upgrading from the previous integration need to sign in again.
The provider remains experimental. Its credentials are kept separate from a normal Copilot CLI or GitHub CLI login, and only the tools supplied by the Theia request are available to the model.
Automatic Model Discovery and Favorites
Theia now asks Anthropic, Google and OpenAI which models they offer, rather than relying on curated lists shipped with each release. Discovery runs on startup, when an API key changes, and on demand. Each provider’s page in AI Configuration shows the discovery status, a refresh action, and its models ordered by release date. A cached snapshot supplies the list if a later discovery request fails.
For configuring the model per agent, model aliases remain the standard approach. An agent can use an alias instead of a specific model ID, keeping its configuration independent of individual model releases. Theia regularly updates the built-in alias defaults with new releases, and you can override their model mappings to suit your needs. See the Theia IDE AI user guide for configuration details.
The chat input keeps that growing catalogue manageable through favorites: it offers the newest model per provider plus the models you mark on the provider page. A “Manage models…” entry takes you there. Favorites only narrow the chat picker; agent configuration and model aliases still offer every discovered model.

For existing configurations, two settings change: the old curated-list preferences are removed in favor of ai-features.<provider>.modelOverrides, which lets you replace discovery with an explicit list. API keys from the backend environment now require one-time consent per provider before use, controlled by ai-features.<provider>.allowEnvironmentApiKey. A configured key in the preferences does not require that environment-key consent.
AI-Generated Commit Messages
The Source Control commit input gains two AI actions: generate a message from staged changes, or from all changes in the selected repository. The latter also includes untracked, non-ignored files, so a new file can inform the message before it has been staged.
Generation fills the commit input for you to review. It asks before replacing existing text, can be cancelled, and does not open a chat session. The buttons are available when AI is active and there are relevant changes. On first use, if the getGitChanges tool is set to Confirm or Disabled, a dialog asks permission to change it to Always Allow before running.
For adopters, @theia/ai-terminal introduces PredefinedShellTool for tools whose command is controlled by their implementation and whose arguments are typed. These tools use the normal tool-confirmation flow rather than the general shell-command allowlist. Applications that customize ScmCommitWidget need to extend the new AiAwareScmCommitWidget to retain the generation buttons.
Chat Search, Thinking Previews and Delegation
Find in chat: With focus in the response tree, Ctrl+F or Cmd+F opens a find bar with a match count, previous/next navigation, and case, whole-word and regular-expression options. Search covers the displayed conversation branch, including off-screen turns, and updates while responses stream. It searches user messages and rendered response text, including code, but excludes tool calls, reasoning, delegated sub-chats and Mermaid diagrams.
Sticky headers and live thinking previews: Response headers stay visible as you scroll, keeping the agent, model and status in view. While an agent is thinking, a spinner and a preview show the latest reasoning lines; the full reasoning remains collapsible afterwards. OpenAI Responses API reasoning summaries now appear as thinking content as well.

Resume delegated sessions: An orchestrating agent can now send follow-up work into a session it previously delegated, using the returned sessionId. The worker keeps its conversation context instead of starting from scratch. Questions from delegated agents also surface in the parent chat, fixing cases where a child session waited for input that the user could not see.
An External API for Tools and AI Sessions
Two new packages let external tools interact with a running Theia application. @theia/external-api supplies a contributable HTTP API, and @theia/ai-external-api adds its first use case: observing and controlling AI chat sessions across connected frontends.
One use case is integration with tools such as Eclipse Enclave, which runs AI coding agents, including Theia AI, in isolated containers. A companion dashboard could use this API to show which Theia sessions are running or waiting for input, send follow-up prompts, and open a session in the IDE when the user wants to inspect it. This gives external tools a way to coordinate agent work while keeping the conversation accessible in Theia.
Clients can list sessions, read conversations as plain text, create sessions, send prompts, and open or restore a session in the chat view. A server-sent event stream reports session changes. The API describes its typed routes in an OpenAPI 3.1 document at /api/openapi.json, which can be imported into API clients or used to generate clients.
The API is off by default. User preferences select whether it runs on the main backend port or a separate server; externalApi.token configures optional bearer-token protection. Configure that protection before making the API accessible to other hosts. Preference changes apply without a restart.
Adopters can contribute their own endpoints through ExternalApiContribution and ExternalApiRouter, with JSON Schema validation for request bodies and a shared response format.
Parallel Container Sessions and an Attach Screen
Theia 1.76 lets you run independent container sessions in separate IDE windows, each with its own session preferences. The launch options --attach-container and --session-preference now reach the window opened by a subsequent launch, even when the IDE is already running. Each window’s session preferences also carry through to its remote backend.
This allows tools such as Eclipse Enclave to open independent container sessions in separate IDE windows. CLI-driven attachment also gets a full-window progress screen with live status and retry/close actions on failure. Manual attachment is unchanged.
Electron adopters with custom preload scripts must adapt to the new CHANNEL_WC_METADATA response object. Applications assembling their extension modules manually must also include the new @theia/dev-container Electron main module. The migration guide covers these changes.
Guided AI Setup on the Welcome Page
The new “Get started with AI” walkthrough moves setup guidance from the chat welcome message to the Welcome page. It walks through activation, connecting a model, choosing a default agent, asking a first question, and tool confirmation and workspace trust. Steps reflect what the user has already completed, so an existing configuration does not need to be repeated. Progress survives a reload.
The chat retains short messages for states such as disabled AI or a missing model, linking into the walkthrough. For adopters, the new WalkthroughProvider contribution point lets build-time Theia extensions contribute walkthroughs alongside VS Code plugins. Walkthrough.pluginId is now optional, and the walkthrough registration APIs have changed.

Static Extensions in Browser-Only Applications
Theia 1.75 added build-time plugin preparation. Version 1.76 adds the runtime support to use those prepared plugins in browser-only applications, including themes, grammars and web-worker extensions. Plugin resources are served through a read-only theia-plugin: URI scheme, and plugin state is kept in browser local storage.
This initial support focuses on extensions bundled with the application. The Extensions view is read-only; runtime installation from Open VSX and terminals are not yet supported. Some web extensions also still have bundling compatibility issues. Adopters should test the extensions they intend to ship.
Browser-only configuration now lives under file:///.theia; existing state at the filesystem root is not migrated automatically. PluginPaths also moves to @theia/plugin-ext/lib/main/common/paths/const, with a deprecated re-export at the old location.
Base Technology and Adopter Updates
VS Code API 1.139.0: Compatibility moves from 1.134.0 to 1.139.0, unblocking extensions that target the newer version. There were no public vscode.d.ts changes between those versions; localization metadata is updated too.
Legacy preview package removed: The deprecated @theia/preview source is now removed. Applications still depending on it should use the VS Code Markdown extension for Markdown previews.
Plugin telemetry follows consent: The plugin host now follows the telemetry consent provider and telemetry.telemetryLevel instead of hardcoding telemetry off. Error and usage collection are distinguished. Adopters implementing TelemetryConsentProvider must supply its new ready promise, and @theia/plugin-ext now depends on @theia/telemetry.
For the complete set of API changes, including decoration events and toolbar context matching, consult the release’s breaking changes and migration guide.
Additional Improvements
Settings and workbench: Selecting a Settings category filters the editor to that category and its descendants, with ancestor headings pinned above the content. Tree widgets no longer jump back to the focused node on unrelated updates after you have scrolled away. Hovers in secondary windows appear beside their target rather than in the main window.
AI providers: Custom Anthropic and OpenAI endpoints accept additional HTTP headers, useful for gateways that require routing or attribution information. Ollama tool-call completion is accepted instead of treated as an error, Gemini token reporting is corrected, and reasoning levels are adjusted to a level the selected model supports.
Chat reliability: User-interaction arguments are now validated so malformed choices cannot bypass the user’s decision. The input cursor stays visible on long wrapped lines, and streaming tool-call labels use top-level argument fields and handle escaped strings correctly.
Editors and search: The extension save APIs now support custom editors and notebooks, and notebook cell language changes reach the cell model. Syntax highlighting retains its tokenizer state after overlong lines. Packaged Electron applications resolve ripgrep from the unpacked archive location, restoring file and workspace search without a downstream workaround.
For a complete overview of all changes in this release, please refer to the 1.76 milestone. These 51 merged pull requests were the result of one month of development. Eclipse Theia follows a monthly release schedule, with the next release due next month. To be notified about future releases, follow us on LinkedIn or follow Theia on Twitter and subscribe to our mailing list.
If you are interested in building custom tools or IDEs based on Eclipse Theia, EclipseSource provides consulting and implementation services for Eclipse Theia, for AI-powered tools, as well as for web-based tools in general.
Furthermore, if you want to extend Theia, Theia AI or the Theia IDE with new features or strategically invest in the project, EclipseSource provides sponsored development for Theia, too. Finally, we provide consulting and support for hosting web-based tools in the cloud.
👉 Get in contact with us to discuss your use case!
👉 Subscribe to our YouTube channel
Stay Updated with Our Latest Articles
Want to ensure you get notifications for all our new blog posts? Follow us on LinkedIn and turn on notifications:
- Go to the EclipseSource LinkedIn page and click "Follow"
- Click the bell icon in the top right corner of our page
- Select "All posts" instead of the default setting