How to Manage Extensions in Trae IDE: Install, Disable, Uninstall, and Fix Common Issues

Key Takeaways

• Trae IDE supports installing, disabling, and uninstalling editor extensions through its built-in Extensions panel. TRAE's current documentation refers to the IDE as TraeCode, although many users still search for it as Trae IDE.
• Open Extensions with Ctrl+Shift+X on Windows/Linux or Cmd+Shift+X on macOS.
• The safest installation path is Trae's built-in extension marketplace. If an extension is missing, Trae also supports importing compatible VS Code .vsix packages.
• A downloaded .vsix can be installed through Extensions → ··· → Install from VSIX, or in supported workflows by dragging the file into the Extensions panel.
• Trae can disable an extension globally or only for the current workspace, which is useful when an extension is needed for one project but causes conflicts elsewhere.
• VS Code compatibility is not guaranteed for every extension version. Extensions that depend on newer VS Code APIs may require an older release, while architecture-specific packages must match the operating system and CPU architecture.
• When debugging slow startup, crashes, language-server conflicts, or unusual editor behavior, temporarily disabling recently installed extensions is usually more useful than immediately uninstalling them.

What Are Extensions in Trae IDE?

Extensions add capabilities to Trae IDE beyond its built-in AI coding features. They can provide programming-language support, debuggers, formatters, linters, themes, Git integrations, database clients, remote-development tools, testing utilities, and other developer workflows.

Trae's current official documentation calls the editor TraeCode, while older documentation, community discussions, and search queries commonly use Trae IDE. The extension-management workflow remains familiar to developers coming from VS Code because Trae exposes an Extensions panel and supports compatible .vsix packages.

This compatibility is useful, but it should not be interpreted as a guarantee that every VS Code extension will behave exactly the same way in Trae. An extension may depend on editor APIs, bundled services, platform-specific binaries, authentication flows, or VS Code versions that do not match Trae's current extension host.

The practical rule is simple:

Use Trae's built-in marketplace first. Use a VSIX package when the extension is unavailable or when a specific compatible version is required.

How to Open the Extensions Panel in Trae IDE

The fastest method is the standard extensions shortcut:

• Windows/Linux: Ctrl+Shift+X
• macOS: Cmd+Shift+X

You can also click the Extensions icon in the left Activity Bar.

The Extensions view is the central place for:

• searching for extensions;
• viewing extension descriptions;
• checking installed extensions;
• installing new extensions;
• disabling extensions;
• uninstalling extensions;
• importing local .vsix packages.

Trae's documentation says an extension detail page can include information such as its description and changelog before installation.

That detail page should be reviewed before installing unfamiliar extensions, especially when they can execute commands, access project files, connect to remote services, or require account authentication.

How to Install an Extension from Trae's Marketplace

The built-in marketplace is the preferred installation method because it presents extensions that Trae can directly discover through its own extension interface.

Step 1: Open Extensions

Press:

Ctrl+Shift+X

On macOS:

Cmd+Shift+X

Alternatively, click the Extensions icon in the left sidebar.

Step 2: Search for the Extension

Enter the extension name in the search box.

Whenever several similarly named packages appear, verify:

• extension name;
• publisher;
• description;
• changelog;
• version;
• installation requirements.

Publisher verification is particularly important for high-value tools such as language servers, AI assistants, Git integrations, and remote-access extensions.

Step 3: Open the Extension Details

Select the extension to inspect its information before installation.

This is useful for detecting requirements such as:

• external runtimes;
• language SDKs;
• authentication;
• project configuration;
• operating-system limitations.

Step 4: Click Install

Click Install.

After installation, the extension should move into the installed-extension list.

Some extensions activate immediately. Others may require a window reload, IDE restart, sign-in, SDK installation, or opening a compatible project.

How to Install a VS Code Extension in Trae IDE

One of Trae's most useful extension-management features is the ability to install compatible extensions originating from the Visual Studio Marketplace when they are not available in Trae's built-in marketplace.

The usual workflow is:

1. Find the required extension in the VS Code Marketplace.
2. Obtain the correct .vsix package.
3. Import that package into Trae.
4. Reload Trae if required.
5. Verify that the extension actually activates.

The final verification step matters. A VSIX can sometimes install successfully while still failing at runtime because of an unsupported editor API or incompatible native dependency.

How to Install a Local VSIX File

If a .vsix file is already available locally, Trae provides a direct import option.

Method 1: Install from the Extensions Menu

1. Open the Extensions panel.
2. Click the ··· menu near the top of the panel.
3. Choose Install from VSIX.
4. Select the .vsix file.
5. Wait for installation to finish.
6. Reload or restart Trae if requested.

This method is explicitly documented by Trae.

The same action can often be opened through the Command Palette by searching for:

Extensions: Install from VSIX...

Community extension documentation for Trae commonly uses this workflow as well.

Method 2: Drag the VSIX into the Extensions Panel

Trae's documentation also describes dragging a downloaded .vsix file into the Extensions panel so the editor can begin installation automatically.

This is convenient when several packages have already been downloaded manually.

Important: Download the Correct VSIX Architecture

Not every extension ships as one universal .vsix.

Some packages contain native binaries and publish separate builds for combinations such as:

• macOS Apple Silicon;
• macOS Intel;
• Windows x64;
• Windows ARM64;
• Linux x64;
• Linux ARM64.

Trae's official documentation specifically warns that architecture-specific extensions cannot always be handled through the generic VS Code Marketplace installation workflow. The correct platform-specific VSIX should be downloaded manually.

This matters because a mismatched package can produce a confusing failure mode: the extension appears installed but does not work correctly.

Before downloading a platform-specific package, confirm both:

Operating system + CPU architecture

For example:

macOS + Apple Silicon ARM64

is different from:

macOS + Intel x64

Why Some VS Code Extensions Do Not Work in Trae

Trae's support for VS Code extensions should be understood as compatibility, not perfect equivalence.

An extension can fail when it expects APIs introduced in a newer version of VS Code than the API surface currently supported by Trae.

Trae's official troubleshooting guidance recommends checking the extension's Version History and installing an earlier release when a newer version depends on unsupported VS Code APIs.

This is one of the most important troubleshooting techniques for Trae extensions.

Consider this situation:

Extension v5.2
Requires newer VS Code API
        ↓
Fails in current Trae build
        ↓
Extension v5.0
Uses older compatible API
        ↓
Works correctly

The newest version is therefore not always the best version for Trae.

How to Disable an Extension in Trae IDE

Disabling is usually preferable to uninstalling when diagnosing problems.

Open the Extensions panel and find the installed extension. Trae provides two important disable modes.

Disable Globally

A global disable prevents the extension from running across your projects.

Use this when:

• the extension is temporarily unnecessary;
• it causes general performance problems;
• it conflicts with another extension across multiple projects;
• you want to test whether it is responsible for an IDE issue.

Disable for the Current Workspace

Trae also supports Disable (Workspace).

This is often the better option when an extension is useful generally but problematic in one repository.

Examples include:

• multiple competing formatters;
• different Python environments;
• alternative linting configurations;
• project-specific TypeScript tooling;
• language servers that overlap with another project extension.

A workspace-level disable lets the rest of the editor configuration remain unchanged.

Disable vs Uninstall: Which Should You Use?

A useful decision rule is:

Disabling makes troubleshooting reversible. Uninstalling is better for permanently cleaning the environment.

How to Uninstall an Extension in Trae IDE

To remove an extension:

1. Open the Extensions panel.
2. Find the extension under the installed list.
3. Hover over it and select Uninstall, or open the extension detail page and click Uninstall.
4. Reload Trae if requested.

These are the uninstall paths documented by Trae.

Uninstalling is appropriate when an extension:

• is no longer required;
• has been replaced by another tool;
• causes persistent compatibility problems;
• comes from an untrusted publisher;
• adds unnecessary background processes;
• duplicates features already provided by Trae.

How to Update Extensions Safely

Extension updates can introduce important bug fixes and security patches, but an update can also introduce a new VS Code API dependency that Trae does not yet support.

For this reason, the safest approach is not simply to assume that latest equals compatible.

For critical development environments:

1. Check whether the extension currently works reliably.
2. Review significant release notes before a major update.
3. Update the extension.
4. Reload Trae.
5. Verify its key commands and project integration.
6. If it stops working, inspect the extension's version history and consider an earlier release.

This approach is especially useful for:

• debuggers;
• remote development extensions;
• language servers;
• container tooling;
• AI coding extensions;
• extensions containing native binaries.

How to Check Whether an Extension Is Actually Working

Installation success and runtime success are different things.

After installation, verify at least one capability that the extension is supposed to provide.

For a language extension, check whether:

• syntax highlighting loads;
• diagnostics appear;
• autocomplete works;
• language-server commands are available.

For a formatter, check whether:

Format Document

appears in the Command Palette and produces the expected result.

For a debugger, confirm that its debug configuration or launch option is available.

For an extension with commands, open the Command Palette:

Ctrl+Shift+P

or on macOS:

Cmd+Shift+P

Then search for the extension's command prefix.

If installation succeeds but none of its commands appear, compatibility or activation should be investigated.

How to Troubleshoot an Extension That Will Not Install

Extension installation failures generally fall into several categories.

1. The Extension Is Missing from Trae's Marketplace

This does not necessarily mean it cannot run in Trae.

Try the VSIX route:

VS Code Marketplace
        ↓
Download compatible VSIX
        ↓
Trae Extensions panel
        ↓
Install from VSIX

Trae officially supports this path when an extension is unavailable in its own marketplace.

2. The Newest Version Is Incompatible

Symptoms can include:

• installation errors;
• extension activation failures;
• missing commands;
• unexplained warnings;
• the extension appearing installed but doing nothing.

Check Version History and try an older release. This is Trae's documented recommendation when an extension depends on newer VS Code APIs.

3. The Wrong Platform Package Was Installed

Verify whether the extension publishes architecture-specific packages.

For example, an Apple Silicon Mac should not receive an Intel-only or Windows VSIX build.

4. The Extension Needs Another Runtime

The extension may require software such as:

• Node.js;
• Python;
• Java;
• .NET;
• Docker;
• a language compiler;
• an external CLI.

Read the extension's requirements before assuming Trae itself is the problem.

5. Authentication Was Not Completed

Cloud-connected extensions may install correctly but remain inactive until authentication finishes.

Look for:

• sign-in notifications;
• browser authorization flows;
• account status in the Status Bar;
• extension-specific settings.

What to Do If the Trae Extension Marketplace Is Blank

A blank or endlessly loading marketplace is usually different from an individual extension incompatibility.

Trae community support has previously recommended checking Trae's internal proxy settings when the marketplace fails to load. A reported troubleshooting path was to open editor settings, search for Proxy, and verify that an unwanted HTTP proxy is not configured.

A sensible troubleshooting order is:

1. Confirm that normal internet access works.
2. Restart Trae.
3. Check editor proxy settings.
4. Disable VPN or proxy rules temporarily if they may be intercepting marketplace traffic.
5. Try a different network.
6. Confirm whether the problem affects every extension or only one package.
7. Check the current Trae release and changelog for marketplace-related fixes.

Do not immediately delete Trae's local extension directory unless there is a clear reason. That directory can contain installed extension data, so destructive cleanup should be treated as a last-resort recovery step with a backup first.

Troubleshooting Extensions That Make Trae Slow

Extensions can affect startup time, memory consumption, CPU usage, file watching, indexing, and editor responsiveness.

If Trae becomes noticeably slower after installing new extensions, use an isolation process.

Step 1: Identify Recent Changes

Start with extensions installed or updated immediately before the slowdown.

Step 2: Disable One Extension

Do not uninstall everything at once.

Disable one likely extension and restart or reload the editor.

Step 3: Reproduce the Problem

Open the same repository and repeat the action that was slow.

Step 4: Continue Narrowing the Cause

If performance improves, re-enable the extension to verify the relationship.

If nothing changes, test the next likely candidate.

This controlled approach is more reliable than randomly changing multiple settings simultaneously.

How to Diagnose Extension Conflicts

Two extensions can both work individually while conflicting when enabled together.

Common examples include:

• two formatters claiming the same file type;
• multiple Python language servers;
• overlapping TypeScript tooling;
• two Git UI extensions modifying similar workflows;
• different remote-development tools;
• competing AI completion extensions;
• multiple linting systems reporting duplicate diagnostics.

The simplest diagnostic method is binary isolation:

Problem exists
     ↓
Disable Extension A
     ↓
Problem gone?
   /       \
 Yes       No
  ↓         ↓
Test A     Re-enable A
against B  and test B

Workspace-level disabling is particularly valuable here because different repositories may require different toolchains.

Manage Formatters Carefully

Formatter conflicts are among the most common extension-management problems in VS Code-compatible editors.

For example, a web project might have:

• Prettier;
• ESLint formatting;
• a framework-specific formatter;
• a language-specific formatter.

Installing all of them does not guarantee that Trae knows which one should handle a file.

After adding a formatter, verify:

• which extension is configured as the default formatter;
• whether format-on-save is enabled;
• whether ESLint is fixing files separately;
• whether project configuration overrides user configuration.

If formatting happens twice or produces unstable diffs, disable unnecessary formatters for that workspace.

Be Careful with Extensions That Duplicate Trae's AI Features

Trae already provides AI-native coding capabilities. Additional AI extensions may still be useful, but installing several simultaneously can create overlapping features.

Possible symptoms include:

• multiple inline suggestions;
• competing autocomplete UI;
• duplicate chat panels;
• conflicting keyboard shortcuts;
• additional background indexing;
• multiple services reading the same repository;
• increased memory or network usage.

Before installing another AI coding extension, determine exactly which missing capability it adds.

A focused extension stack is usually easier to maintain than installing every available AI assistant.

Security Best Practices for Trae Extensions

Extensions execute inside a development environment that may contain source code, environment variables, Git credentials, deployment configuration, and proprietary project data.

Treat an extension as software, not merely as a visual editor add-on.

Before installing an unfamiliar package, evaluate:

• Publisher: Is the publisher expected and trustworthy?
• Repository: Is the source code public when it should be?
• Maintenance: Is the project still maintained?
• Permissions and behavior: Does it execute binaries or connect to external services?
• Authentication: Where are credentials stored?
• Network access: Does the extension upload code or metadata?
• Dependencies: Does it download additional software?

This is especially important when manually sideloading .vsix packages because the user is intentionally bypassing the normal marketplace discovery path.

Built-In Extensions vs Agent Plugins: Do Not Confuse Them

Current TraeCode documentation also describes a Plugin Marketplace for agent capabilities. This is different from traditional editor extensions.

Traditional editor extensions primarily enhance the IDE itself, such as:

• language support;
• themes;
• formatters;
• debuggers;
• editor commands.

Trae's newer agent plugins can connect external tools, services, MCP servers, and skills to the AI agent. The official documentation places these under Settings → Plugin Marketplace.

A useful distinction is:

When a guide says to install an extension, do not assume it means the newer Trae agent plugin system.

Importing from VS Code or Cursor

Trae's onboarding flow supports importing existing configuration from VS Code or Cursor.

This can make migration easier, but configuration import should not be treated as proof that every extension will remain compatible.

After migrating:

1. Open a representative project.
2. Review installed extensions.
3. Remove extensions that duplicate Trae features.
4. Test language servers.
5. Test formatters and linters.
6. Verify debugger integrations.
7. Confirm remote or container tooling if used.
8. Check keyboard shortcuts for conflicts.

Migration is most reliable when the extension environment is audited instead of simply copying years of accumulated editor configuration.

Recommended Extension Management Strategy

A clean Trae setup can follow four principles.

Prefer Fewer, High-Value Extensions

Install extensions because a workflow requires them, not simply because they are popular.

Prefer the Built-In Marketplace First

This reduces unnecessary compatibility uncertainty.

Use VSIX for Missing or Version-Specific Packages

VSIX installation is valuable when:

• the extension is not in Trae's marketplace;
• a particular historical version is required;
• a platform-specific package is necessary;
• an offline installation is needed.

Disable Before Uninstalling During Troubleshooting

This keeps testing reversible and makes extension-conflict diagnosis faster.

A Practical Extension Troubleshooting Checklist

When an extension does not behave correctly, check these items in order:

• Is the extension actually installed?
• Is it enabled globally?
• Is it disabled for this workspace?
• Does it require a window reload?
• Does it require authentication?
• Does it need an external runtime or CLI?
• Is the VSIX built for the correct CPU architecture?
• Does the current extension version require a newer VS Code API?
• Would an older extension version work?
• Is another extension providing the same feature?
• Does the problem disappear when competing extensions are disabled?
• Is Trae's marketplace or network connection itself failing?

Following this order helps separate installation problems from compatibility, configuration, and network problems.

FAQ

Where Is the Extension Manager in Trae IDE?

Click the Extensions icon in the left Activity Bar or use Ctrl+Shift+X on Windows/Linux and Cmd+Shift+X on macOS.

Can Trae IDE Install VS Code Extensions?

Yes. Trae's official documentation says extensions unavailable in Trae's own marketplace can be imported from the VS Code ecosystem through compatible .vsix packages.

How Do You Install a VSIX in Trae?

Open the Extensions panel, click ···, choose Install from VSIX, and select the downloaded .vsix file. Trae also documents dragging a VSIX directly into the Extensions panel.

Why Does a VS Code Extension Install but Not Work in Trae?

The extension may depend on APIs from a newer VS Code version or contain binaries for a different platform architecture. Trae recommends trying an earlier extension release when newer APIs cause incompatibility.

Can an Extension Be Disabled for Only One Project?

Yes. Trae supports both global disabling and Disable (Workspace) for the current workspace.

Should an Extension Be Disabled or Uninstalled?

Disable it when troubleshooting or when it may be needed later. Uninstall it when it is permanently unnecessary, incompatible, or untrusted.

Are Trae Plugins the Same as Extensions?

No. Traditional extensions modify editor functionality, while Trae's newer Plugin Marketplace adds capabilities that agents can invoke, including connections to external tools and services.

Is Trae IDE Now Called TraeCode?

Current TRAE documentation uses the name TraeCode for its professional AI coding IDE, while many users and older references still call the product Trae IDE.

Conclusion

Managing extensions in Trae IDE is straightforward once the three installation paths are understood: Trae's marketplace, compatible VS Code extensions through VSIX packages, and locally stored VSIX files.

The most important difference from ordinary VS Code extension management is compatibility awareness. An extension can install successfully but still depend on an unsupported editor API or the wrong native architecture. When that happens, checking the extension's version history and platform build is usually more productive than repeatedly reinstalling the latest version.

For a stable development environment, keep the extension stack intentional. Install only tools that add a clear capability, use workspace-level disabling for project-specific conflicts, and disable suspicious extensions before uninstalling them during diagnosis.

Developers moving from VS Code or Cursor can take advantage of Trae's familiar extension model, but a clean migration should include an extension audit rather than blindly reproducing an old editor setup. That approach keeps Trae faster, reduces conflicts, and makes its built-in AI features easier to use alongside traditional development tooling.