Zed 1.0

Summary

• A smarter search experience that keeps results in a persistent, dockable panel with quick‑close (Esc) and multi‑file preview, eliminating the “new tab every time” pain point.
• Integrated “don’t warn again” button for each search result to auto‑apply ignore‑case or regex settings.

Details

Notes

• HN users repeatedly lamented that “search opens a new tab, which I hate” and wanted a quick‑glance UI.
• Solving this would directly address the “search UI is awkward” and “no sidebar option” complaints, likely sparking enthusiastic discussion among power users.

Summary

• GUI tool to toggle or mute specific LSP diagnostics per project, with a one‑click “silence this warning forever” that auto‑generates the appropriate .zed config.
• Visual indicator of which language server is active and its current warning set.

Details

Notes

• “turn off all AI features” checkbox exists, yet many still struggle with “missing features” and “warnings I can’t turn off”; a UI for LSP fine‑tuning would be a major usability boost.
• Would be heavily discussed on HN as a concrete improvement to Zed’s “defaults that work for everyone” criticism.

Summary

• A curated theme marketplace with high‑contrast, large‑icon, and dyslexia‑friendly palettes, plus a simple UI to customize accent colors without editing JSON manually.
• Automatic detection of system‑wide contrast settings and optional font‑size sliders.

Details | Key | Value |

|-----|-------| | Target Audience | Color‑blind or visually impaired developers; also power users who want quick visual customization. | | Core Feature | One‑click theme switcher with live preview; “export as JSON” for sharing custom themes. | | Tech Stack | Rust backend, React UI embedded in Zed’s settings pane, theming engine based on Monokai. | | Difficulty | Low | | Monetization | Revenue-ready: Theme pack sales ($3 each) or subscription for premium palettes ($4/mo). |

Notes

• Multiple comments highlighted “theme is bland”, “grey on grey”, and “accessibility issue”.
• A market‑ready solution would attract praise from the accessibility community and generate discussion about monetization models.

Summary - Redesign of the agent sidebar to be a dockable, persistent panel that can be split, pinned, or hidden without affecting the main editing view.

• Ability to view agent conversation history in a separate pane and switch contexts without reselecting agents.

Details | Key | Value |

|-----|-------| | Target Audience | Users experimenting with multi‑agent workflows (e.g., Claude Code, custom agents) who find the current “window titlebar controls branch” confusing. | | Core Feature | Dockable side panel with tab‑based agent selection, persistent session storage, and shortcut to toggle visibility (Ctrl+Alt+A). | | Tech Stack | Rust UI components, Electron‑style docking library (e.g., dockview), JSON‑backed session metadata. | | Difficulty | High | | Monetization | Revenue-ready: Enterprise licensing for team‑wide usage ($15/user/mo). |

Notes

• “agent first layout which I cannot undo” and “unclear which is source of truth” are recurring pain points. - A polished UI would likely be lauded in HN threads as the missing piece for serious AI‑augmented development.

--- ## Remote Dev Container Manager

Summary

• Plugin that automatically provisions, mounts, and monitors SSH‑based dev containers, with UI to switch between multiple remote environments, auto‑forward ports, and persist container state across sessions. ### Details
  | Key | Value | |-----|-------| | Target Audience | Teams using remote dev boxes or “online live reloading apps” who currently wrestle with manual SSH setup and port forwarding. | | Core Feature | One‑click “Create Remote Workspace”, integrated terminal tab, auto‑detect .devcontainer configs, visual status dashboard. | | Tech Stack | Rust networking (tokio), Tauri for UI, Docker Engine API over SSH, secure credential vault. | | Difficulty | Medium | | Monetization | Revenue-ready: Team plan with admin controls ($8/user/mo). |

Notes

• Several comments emphasized “remote dev containers are critical” and “SSH remote editing is a must”.
• Solving this would convert many VS Code‑remote users to Zed and generate buzz across HN’s remote‑work community.

Summary

• A sandboxed Rust/Wasm API that lets third‑party developers add new docked panels or floating windows (e.g., Markdown preview, code‑transformation canvas) without breaking the core editor.

Details | Key | Value |

|-----|-------| | Target Audience | Plugin developers who want richer UI than the current limited extension API permits. | | Core Feature | Declarative panel definition JSON, live‑preview callbacks, secure IPC with editor core. | | Tech Stack | Rust (wasm), wasmtime, bindings exposed via existing extension host. | | Difficulty | High | | Monetization | Hobby (open source), optional paid support contracts for enterprise adopters. |

Notes

• “Extensions can’t add new UI, so you are stuck fitting to the recipe Zed team provides” is a frequent gripe.
• Providing a sanctioned way to embed custom UI would unlock discussing topics like “Markdown WYSIWYG experience” and spark ecosystem growth discussions on HN.