# Attaching Cursor to running container doesn't show "Extension install" Pop-Up and doesn't keep installed extensions after reboot

**URL:** <https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732>\
**Category:** Bug Reports\
**Tags:** devcontainers, extensions, wsl\
**Created:** [March 24, 2026, 8:52am UTC](https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732 "2026-03-24T08:52:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Grevil](https://avatars.discourse-cdn.com/v4/letter/g/7c8e57/32.png) [@Grevil](https://forum.cursor.com/u/Grevil)\
**Post date:** [March 24, 2026, 8:52am UTC](https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732/1 "2026-03-24T08:52:54Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

There are two bugs related to this issue:

#### First bug

When attaching cursor to a running container for the first time (using Anysphere Dev Containers), it used to directly check the “.vscode/extensions.json” and ask you, if you would like to batch install the extensions via a pop-up.

A few releases ago this is not the case anymore, so after you attach cursor to the running container, you always have to go to the “Extensions” Tab and manually type in `@recommended` to show all recommended extensions and then install them manually one by one.

#### Second Bug

When using Microsoft’s Dev Containers extension, you have to only install the extensions only once, when you attach vscode to a container for the first time. Even if you restart the PC (or WSL) and then reattach to the same container, Microsoft’s Dev Containers extension, will know, which extensions you installed the last time you attached to this container and will reinstall them automatically.

When using the Anysphere Dev Containers extension, you always have to manually install the extensions after reboot. Which gets quite annoying.

Also you always have to manually reindex the project code, if it exceeds a certain size in the cursor settings, even if you already reindexed it once, it doesn’t keep on reindexing automatically.

### Steps to Reproduce

#### First Bug

- Have a container running with a VSCode extensions.json in `/var/www/html/.vscode/extensions.json`
- Attach Cursor to `/var/www/html` using the Anysphere Dev Containers extension
- See no install pop-up

#### Second Bug

- Have a container running with a VSCode extensions.json in `/var/www/html/.vscode/extensions.json`
- Attach Cursor on `/var/www/html` using the Anysphere Dev Containers extension
- Install all extensions manually
- Restart WSL / computer
- Reattach to the same container on ` /var/www/html`
- The extensions are not automatically installed and need to be installed manually again.

### Expected Behavior

#### First Bug

- The install Popup should appear

#### Second Bug

- The extensions should be automatically installed on reattaching Cursor

### Operating System

Windows 10/11

### Version Information

Version: 2.6.21 (user setup)  
VSCode Version: 1.105.1  
Commit: fea2f546c979a0a4ad1deab23552a43568807590  
Date: 2026-03-21T22:09:10.098Z  
Build Type: Stable  
Release Track: Default  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
OS: Windows\_NT x64 10.0.26200

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [March 24, 2026, 9:07am UTC](https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732/3 "2026-03-24T09:07:33Z")

</div>

Hey, thanks for the detailed report.

A couple of quick questions so we can narrow this down:

Bug 1 no recommended extensions popup: When you attach to the container, are you using only `.vscode/extensions.json` for recommendations, or do you also have a `.devcontainer/devcontainer.json` with extensions listed in `customizations.vscode.extensions`? Extensions in `.vscode/extensions.json` are treated as recommended and used to show a prompt, but if you want auto-install, listing them in `devcontainer.json` under `customizations.vscode.extensions` is usually more reliable:

```json
{
    "customizations": {
        "vscode": {
            "extensions": [
                "ext1.name",
                "ext2.name"
            ]
        }
    }
}

```

Related thread with staff response: [Extensions listed in `devcontainer.json` not installed into Remote Extension Host](https://forum.cursor.com/t/extensions-listed-in-devcontainer-json-not-installed-into-remote-extension-host/122375)

Bug 2 extensions lost after reboot: This sounds like a real gap in the Anysphere Dev Containers extension vs Microsoft’s one. I’ll flag this to the team. Can you confirm if you’re doing a pure Attach to Running Container flow, or using a devcontainer.json based flow?

Re-indexing: Is this related to the large project file limit in settings? After reboot, does the index disappear completely, or does it show as partially indexed?

Do you remember roughly which version the popup was still working in? That would help us track down when the regression started.

---

<div class="post-metadata">

**Author:** ![Grevil](https://avatars.discourse-cdn.com/v4/letter/g/7c8e57/32.png) [@Grevil](https://forum.cursor.com/u/Grevil)\
**Post date:** [March 25, 2026, 1:47pm UTC](https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732/4 "2026-03-25T13:47:08Z")

</div>

Hey, thanks for the fast reply!

Unfortunately, the .devcontainer.json isn’t properly used when attaching to a running container, where the container itself contains the .devcontainer.json. There is this old issue, where this is talked about:

> <https://github.com/microsoft/vscode-remote-release/issues/5278>
>
> Hi and thank you all very much for your hard work on vscode and vscode-remote! I…t's simply brilliant.
> 
> \### Context
> We're using tools like https://github.com/drud/ddev or https://lando.dev/ to build and run smart development docker containers.
> We're using VSCode Remote to attach to these running containers using the wonderful UI via F1 + Remote-Containers: Attach to Running Container ...
> There we select the container we'd like to attach to and run it.
> 
> \### Problem
> This works, but for developers like you and us the process isn't really perfect. It's clicky here, clicky there for a task where you'd expect to write a shell script and GO :)
> 
> I've read many similar issues, most are about how to start devcontainers / k8 or ssh remote connections.
> Anyway it seems such CLI parameters aren't yet officially documented?
> 
> For our use-case (attaching to a running docker container by name from CLI / shell script) I couldn't find a viable solution. That's why I've written this feature request to document the CLI options and provide a clever way to \*\*start vscode from CLI / shell script attached to a running container by container name / id\*\*.
> 
> \### Proposed solution
> 1. \*\*Document the CLI parameters officially with examples how to start vscode from CLI in remote\*\* (devcontainer, attached to running container, k8, ssh, ...?)
> 2. \*\*Allow to attach to a running container from CLI by container name\*\* (or document how to do that if that should be possible already)
> 
> Once again, thank you very much for your hard work on this wonderful project!

This is an age old task for us, where we tried several methods to auto install extensions, but never really succeeded. All documented here:

> <https://github.com/webksde/ddev-vscode-devcontainer-drupal-template/issues/74>
>
> It is currently not possible to use a custom settings/extensions for the attache…d container, current workaround uses a workspace in the project directory with custom workspace settings/extensions, but inside a workspace it is only possible to recommend these extensions not force install them. Furthermore it seems like some workspace settings get overwritten by my "normal" VSCode settings which should not happen.
> 
> Everything documented here:
> https://github.com/microsoft/vscode-remote-release/issues/5944
> 
> and here:
> https://github.com/webksde/ddev-vscode-devcontainer-drupal9-template/issues/28

I introduced a `cursor` command, which auto attaches cursor to the running ddev web container, similiar to our VSCODe "`code`command in the same folder here: [ddev-vscode-devcontainer-drupal-template/.ddev/commands/host/cursor.sh at main · webksde/ddev-vscode-devcontainer-drupal-template · GitHub](https://github.com/webksde/ddev-vscode-devcontainer-drupal-template/blob/main/.ddev/commands/host/cursor.sh)

But it won’t auto install any extensions, because of the reasons listed above in the issues. As a workaround we added the `.vscode/extensions.json`, so when we attach via command, we get the little prompt to install the recommended extensions. And in the case of VSCode the install prompt appeared and the extensions kept being installed even after reattaching after reboot. But for Cursor the install prompt doesn’t show up nor are the extensions still installed after reboot.

Regarding the re-indexing after reboot: It shows, that the index is gone completely, but once pressing “compute index” it seems to find an existing index and only updates it:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/c/7/c7e1666fd9d1f63f34791695e7742f814108e3f4.png)

but this is also really annoying to reindex everytime after reboot.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [March 25, 2026, 4:39pm UTC](https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732/5 "2026-03-25T16:39:35Z")

</div>

Hey, thanks for the detailed follow-up and the GitHub issue links. That context is really helpful.

Here’s what I’m tracking:

1. Recommended extensions popup regression  
`.vscode/extensions.json` used to trigger the install prompt when attaching to a running container, but it doesn’t anymore. Got it that `devcontainer.json` won’t work for Attach to Running Container flows.

2. Extensions not persisted after WSL or PC reboot  
Microsoft Dev Containers keeps installed extensions across reboots, but Cursor doesn’t. That’s a real gap.

3. Index lost after reboot  
From your screenshot, it finds the existing index and updates it, but not auto-resuming indexing on reattach is definitely inconvenient.

I’ve flagged all three issues with the team. No ETA yet, but your report, especially the GitHub issue links showing the attach-to-running-container limitations, helps us prioritize.

One question: do you remember roughly which Cursor version still had the recommended extensions popup working? That would help narrow down when the regression started.

Let me know if anything else comes up.

---

<div class="post-metadata">

**Author:** ![Grevil](https://avatars.discourse-cdn.com/v4/letter/g/7c8e57/32.png) [@Grevil](https://forum.cursor.com/u/Grevil)\
**Post date:** [March 27, 2026, 11:04am UTC](https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732/8 "2026-03-27T11:04:45Z")

</div>

> [@deanrie](#):
>
> do you remember roughly which Cursor version still had the recommended extensions popup working?

Sorry I don’t unfortunately. It’s like this for a couple of months now (maybe 2?) I always update Cursor, once an update ships.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 6, 2026, 2:40pm UTC](https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732/9 "2026-04-06T14:40:24Z")

</div>

No problem if you don’t remember the exact version. Having a rough 2-month window is enough to narrow down the regression search.

All three issues have been shared with the team. There’s no timeline yet, but I’ll post here if there are any updates. Let me know if you run into anything else.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [May 13, 2026, 4:05pm UTC](https://forum.cursor.com/t/attaching-cursor-to-running-container-doesnt-show-extension-install-pop-up-and-doesnt-keep-installed-extensions-after-reboot/155732/20 "2026-05-13T16:05:12Z")

</div>

Closed on May 13, 2026, 4:05pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
