From 5d7fa30bc9790c7988521314181ed6b57247d7a2 Mon Sep 17 00:00:00 2001 From: B Lacroix Date: Fri, 19 Jun 2026 14:32:36 +0200 Subject: [PATCH] Document Zed cli_default_open_behavior for one window per worktree When the "Open in" target is Zed, Supacode opens each worktree in its own window. This requires Zed's `cli_default_open_behavior` to be `new_window` (default is `existing_window`, which collapses worktrees into one window). Add a short hint under repository settings explaining the setting and how to reach it (`zed://settings/cli_default_open_behavior`). --- content/docs/worktree/repository-settings.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/docs/worktree/repository-settings.mdx b/content/docs/worktree/repository-settings.mdx index 1e7e61c..e18ad92 100644 --- a/content/docs/worktree/repository-settings.mdx +++ b/content/docs/worktree/repository-settings.mdx @@ -19,6 +19,16 @@ From the repository settings UI, you can change: Supacode also persists the selected "Open in" target for each repository. +### Opening worktrees in Zed + +When the "Open in" target is **Zed**, Supacode opens each worktree as its own Zed window, and focuses the existing window when that worktree is already open. + +This relies on Zed's `cli_default_open_behavior` setting being `new_window`. Zed's default is `existing_window`, which makes every worktree collapse into a single shared window. Set it from Zed via `zed://settings/cli_default_open_behavior`, or add to your Zed `settings.json`: + +```json +"cli_default_open_behavior": "new_window" +``` + ## On-disk file If a repository contains a `supacode.json` file at its root, Supacode reads and writes repository settings there.