From 4e64be1237795840188659f295900e65bcfdee34 Mon Sep 17 00:00:00 2001
From: KyleBarton <kjbarton4@gmail.com>
Date: Fri, 22 May 2026 20:19:54 -0700
Subject: [PATCH] Update docs with note on how extensions work

---
 docs/src/dev-containers.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/docs/src/dev-containers.md b/docs/src/dev-containers.md
index 6a6a030bb91..eb35980080c 100644
--- a/docs/src/dev-containers.md
+++ b/docs/src/dev-containers.md
@@ -41,6 +41,26 @@ If you modify `.devcontainer/devcontainer.json`, Zed does not currently rebuild
 Once connected, Zed operates inside the container environment for tasks, terminals, and language servers.
 Files are linked from your workspace into the container according to the dev container specification.
 
+## Extensions
+You can specify extensions in the .devcontainer/devcontainer.json under the "customizations" field like so:
+```json
+{
+  ...
+  "customizations": {
+    "zed": {
+      "extensions": ["vue", "ruby"],
+    },
+    "vscode": {
+      ...
+    },
+    "codespaces": {
+      ...
+    },
+  }
+}```
+
+Note that extensions load for the Zed session, so these extensions will exist on your local Zed as well.
+
 ## Known Limitations
 
 > **Note:** This feature is still in development.