## Description Add `#!/bin/sh` to zed_settings coder_script <!-- Briefly describe what this PR does and why --> ## Type of Change - [ ] New module - [ ] New template - [X] Bug fix - [ ] Feature/enhancement - [ ] Documentation - [ ] Other ## Module Information <!-- Delete this section if not applicable --> **Path:** `registry/coder/modules/zed` **New version:** `v1.1.1` **Breaking change:** [ ] Yes [X] No ## Testing & Validation - [X] Tests pass (`bun test`) - [X] Code formatted (`bun fmt`) - [X] Changes tested locally ## Related Issues https://github.com/coder/registry/issues/482 <!-- Link related issues or write "None" if not applicable -->
2.3 KiB
2.3 KiB
| display_name | description | icon | verified | tags | |||
|---|---|---|---|---|---|---|---|
| Zed | Add a one-click button to launch Zed | ../../../../.icons/zed.svg | true |
|
Zed
Add a button to open any workspace with a single click in Zed.
Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Important
Zed needs you to either have Coder CLI installed with
coder config-sshrun or Coder Desktop
module "zed" {
count = data.coder_workspace.me.start_count
source = "registry.coder.com/coder/zed/coder"
version = "1.1.1"
agent_id = coder_agent.example.id
}
Examples
Open in a specific directory
module "zed" {
count = data.coder_workspace.me.start_count
source = "registry.coder.com/coder/zed/coder"
version = "1.1.1"
agent_id = coder_agent.example.id
folder = "/home/coder/project"
}
Custom display name and order
module "zed" {
count = data.coder_workspace.me.start_count
source = "registry.coder.com/coder/zed/coder"
version = "1.1.1"
agent_id = coder_agent.example.id
display_name = "Zed Editor"
order = 1
}
With custom agent name
module "zed" {
count = data.coder_workspace.me.start_count
source = "registry.coder.com/coder/zed/coder"
version = "1.1.1"
agent_id = coder_agent.example.id
agent_name = coder_agent.example.name
}
Configure Zed settings including MCP servers
Zed stores settings at ~/.config/zed/settings.json by default. If XDG_CONFIG_HOME is set on Linux, settings will be at $XDG_CONFIG_HOME/zed/settings.json.
You can declaratively set/merge settings with the settings input. Provide a JSON string (e.g., via jsonencode(...)). For example, to configure MCP servers:
module "zed" {
count = data.coder_workspace.me.start_count
source = "registry.coder.com/coder/zed/coder"
version = "1.1.1"
agent_id = coder_agent.example.id
settings = jsonencode({
context_servers = {
your-mcp-server = {
source = "custom"
command = "some-command"
args = ["arg-1", "arg-2"]
env = {}
}
}
})
}
See Zed’s settings files documentation: https://zed.dev/docs/configuring-zed#settings-files