Zed.dev + LoopCLI

Zed’s ultra-fast editor is perfect for teams who want LoopCLI at their fingertips. This guide covers command palette hooks, integrated terminal workflows, and collaboration tips.

1. Make the CLI available to Zed

• On macOS: copy the LoopCLI binary to /usr/local/bin or add $HOME/.local/bin to your shell PATH.
• On Linux: ln -s ~/.loopcli/loopcli /usr/local/bin/loopcli.
• Verify inside Zed’s terminal (⌘J / Ctrl+J): loopcli version.

2. Add command palette shortcuts

Create .zed/tasks.json with custom commands:

{
  "tasks": [
    {
      "name": "LoopCLI: Run Current Loop",
      "command": "loopcli loop run ${buffer_basename}" ,
      "dir": "${workspace_root}"
    },
    {
      "name": "LoopCLI: Deploy Current Loop",
      "command": "loopcli loop deploy ${buffer_basename} --activate",
      "dir": "${workspace_root}"
    }
  ]
}

Use Cmd+Shift+P (macOS) / Ctrl+Shift+P (Windows/Linux) → “Tasks: Run Task” to trigger them.

3. Live logs & split terminals

• Pin a split terminal to run loopcli loop run --watch my-loop. Zed’s low-latency terminal keeps logs in sync with your edits.
• Use Cmd+Shift+D to duplicate terminals so one pane runs tests while another monitors deploys.

4. Team snippets & AI collaboration

• Share LoopCLI snippets via .zed/snippets.json—include common HTTP steps, connectors, and schedule examples.
• When using Zed’s built-in AI, paste the LoopCLI YAML schema or link the Starter Recipes page so completions stay valid.

5. Recommended automations

6. Troubleshooting

Next steps

• Wire Zed with Connectors to call external APIs from your loops.
• Review Authentication to secure secrets used in terminal tasks.
• Share scripting wishes in Discord; we publish Zed automation recipes monthly.