Zed module

[bpmct]

A discussion dedicated to the Zed module. Share your thoughts, questions, and feedback here.

Module Scorecard

Presentation & Onboarding	IDE Integration	Credential Hygiene	Restricted-Environment Readiness	Engineering Quality	Overall
20 / 25	24 / 25	20 / 20	N/A	8 / 10	90 / 100

Drilldown

Presentation & Onboarding — 20 / 25

Criterion	Max	Score	Notes
Configuration-mode examples	12	12	Multiple documented examples cover major modes: specific directory, custom display name/order, custom agent name, and managed settings with MCP servers. Each has sensible defaults.
Coder-context framing	8	8	README clearly names both Coder and Zed, explains the module adds a one-click button to launch Zed, and documents the prerequisite that users need Coder CLI with coder config-ssh or Coder Desktop for the flow to work.
Visual preview	5	0	No image, GIF, or video embedded in README. Only an icon reference exists.

IDE Integration — 24 / 25

Criterion	Max	Score	Notes
Dashboard entry point	7	7	coder_app resource with proper zed://ssh/... URL scheme for native launch behavior.
Managed configuration	6	6	Documented support for managed Zed settings via settings variable with jsonencode(...). README includes example configuring MCP servers and links to Zed's settings documentation.
Configurable folder or workdir	6	6	folder variable documented with example opening /home/coder/project. Appended to URL path.
Pre-installed extensions	6	5	N/A - Zed is a native desktop IDE, not a web IDE. This criterion does not apply.

Credential Hygiene — 20 / 20

Criterion	Max	Score	Notes
Secrets marked sensitive	16	16	No sensitive inputs exist in this module. The settings variable accepts configuration JSON but not secrets. README examples show configuration data (MCP server commands, theme settings) without any inline secrets or API keys.
Non-hardcoded auth path	4	4	Module relies on Coder's SSH authentication via coder config-ssh or Coder Desktop, avoiding raw credential handling entirely.

Restricted-Environment Readiness — N/A

Criterion	Max	Score	Notes
Mirrorable artifact source	10	N/A	Module downloads nothing. It only creates a coder_app link and optionally writes a settings file. No tool installation occurs.
Bring-your-own binary	5	N/A	Module downloads nothing. Zed must already be installed on the user's local machine (not in the workspace).
Egress transparency	3	N/A	Module makes no external network calls. The coder_app URL is a local protocol handler. Settings script only writes to local filesystem.
Runs without sudo	2	N/A	The coder_script for settings never invokes sudo; it only uses mkdir, base64, jq, and file writes. However, since this theme is entirely N/A, this criterion is excluded from scoring.

Engineering Quality — 8 / 10

Criterion	Max	Score	Notes
Input quality	6	6	All inputs have clear descriptions. Defaults are sensible (empty folder, null order/group, "Zed" display name, "zed" slug). No validation blocks exist, but the simple string/number types don't require complex validation.
Test coverage	4	2	.tftest.hcl covers URL construction, folder paths, agent names, settings encoding, and empty settings behavior. TypeScript tests in main.test.ts verify settings file creation, JSON merging with jq, special character handling, and conditional script creation. However, tests do not cover end-to-end Zed launch behavior or the actual zed:// protocol interaction—only the Terraform resource outputs and script logic.

Overall — 90 / 100

Raw 72 / 80 → round(72 / 80 × 100) = 90

Restricted-Environment Readiness is N/A (module downloads nothing, makes no external calls, runs no scripts requiring privilege assessment in that context).

Raw: 72 / 80 (excluding N/A theme)

Normalized: round(72 / 80 × 100) = 90 / 100

Note: The Overall column header shows "96 / 90" but the correct normalized score is 90 / 100 (Strong).

---

Scored against SCORECARD.md on 2026-08-10 with claude-sonnet-4-5.