Audited the AI documentation against the implementation
## Changes
- **tool-permissions**: `skill` tool patterns match the absolute
`SKILL.md` path, not the skill name (fixed the table, example pattern,
and added a clarifying note).
- **external-agents**: Gemini CLI receives Zed's Google AI key when no
env key is set; extension-provided agents are deprecated in favor of the
ACP registry.
- **inline-assistant**: alternatives run alongside the inline assistant
model (not just the default model); fixed a broken anchor and
`gpt-4-mini` → `gpt-5-mini` model id typos.
- **mcp**: corrected the extensions menu item name ("Install New
Servers…"), the remote server `url` example, and removed the nonexistent
`thinking` tool from the profile example.
- **agent-panel**: "New From Summary" lives in the New Thread menu;
corrected the `@`-mention type list (no "instruction files"; added Fetch
and Branch Diff).
- **use-api-access**: DeepSeek default `api_url` includes `/v1`.
- **skills**: folder name is a convention not a requirement; long
descriptions warn rather than fail (measured in bytes); hidden skills
are also `@`-mentionable; dropped the unenforced consecutive-hyphen
rule; reconciled the no-remote-registry note with GitHub import.
- **edit-prediction**: `alt-tab` and `alt-l` are bound across platforms;
predictions are throttled rather than fired on every keystroke.
- **getting-started, windows-and-projects, parallel-agents**: Panel
Layout lives in the title-bar user menu, with
`workspace::UseAgenticLayout`/`UseClassicLayout` action references.
Release Notes:
- N/A
---------
Co-authored-by: zed-zippy[bot] <234243425+zed-zippy[bot]@users.noreply.github.com>
3.8 KiB
title, description
| title | description |
|---|---|
| Windows & Projects | How Zed handles multiple projects in windows, including the threads sidebar and options for opening in new windows. |
Windows & Projects
Zed lets you work on multiple projects in a single window. Projects appear in the threads sidebar on the left, and you can switch between them while keeping your context intact.
Use Panel Layout > Agentic from the user menu in the title bar (or the {#action workspace::UseAgenticLayout} action) to keep the Threads Sidebar and Agent Panel together on the left. Use Panel Layout > Classic (or {#action workspace::UseClassicLayout}) to restore the editor-oriented layout.
How Projects Open
By default, when you open a folder in Zed, it opens as a new project in your current window's threads sidebar rather than creating a new window. This keeps related work together and preserves your agent threads and layout.
| Action | Result |
|---|---|
| File > Open | Opens in current window (threads sidebar) |
| File > Open Recent | Opens in current window (threads sidebar) |
| Drag folder to Zed | Opens in current window (threads sidebar) |
zed ~/project |
Opens in current window (threads sidebar) |
Working with Multiple Projects
When you have multiple projects open:
- Click a project header to collapse or expand its threads; Cmd+click (macOS) or Ctrl+click (Linux/Windows) to switch to that project
- Each project has its own file tree, git state, and search scope
- Agent threads are tied to their project context
- Your workspace layout (splits, tabs) is preserved per project
Think of projects in the threads sidebar like browser tabs, but for repositories.
Opening in a New Window
Sometimes you want a completely separate window. Here's how:
From Open Recent
When using File > Open Recent ({#kb projects::OpenRecent}):
- Enter or click opens in the current window (threads sidebar)
- Cmd+Enter or Cmd+click (macOS) / Ctrl+Enter or Ctrl+click (Linux/Windows) opens in a new window
From the CLI
Use the -n flag to force a new window:
zed -n ~/projects/other-project
Other CLI options for controlling window behavior:
| Flag | Behavior |
|---|---|
-n, --new |
Always open in a new window |
-a, --add |
Add to the current window's threads sidebar |
-r, --reuse |
Replace the current project in the existing window |
See CLI Reference for full details.
Via Settings
You can change the default CLI behavior with the cli_default_open_behavior setting:
{
"cli_default_open_behavior": "new_window"
}
Options:
existing_window(default): Open folders in the current window's threads sidebarnew_window: Open folders in a new window
This setting affects CLI and double-click behavior, not the File > Open menu.
Adding Folders to a Project
If you want to add a folder to your current project (not as a separate project in the threads sidebar), you have several options:
- File menu: File > Add Folder to Project
- Project panel: Right-click in the project panel and choose "Add Folders to Project"
- Open Recent: Select a recent project and click the "Add Folder to this Project" button
This adds the folder as an additional root in your current project's file tree, similar to VS Code's multi-root workspaces.
See Also
- Threads Sidebar: Managing threads across projects
- Getting Started: Essential commands and setup
- VS Code Migration: How Zed's project model differs from VS Code