LoopCLI

JetBrains & Fleet + LoopCLI

JetBrains IDEs and Fleet give you powerful project-aware tooling. Follow this guide to integrate LoopCLI with the IDE of your choice (IntelliJ IDEA, WebStorm, PyCharm, Fleet, etc.).

1. Install LoopCLI & ensure PATH access

  • macOS/Linux: add the LoopCLI binary to /usr/local/bin or export it in your shell profile.
  • Windows: add the installation folder (%USERPROFILE%\.loopcli) to your system PATH and restart the IDE.
  • Confirm inside the IDE terminal: loopcli version.

2. Create a Run Configuration

  1. Go to Run → Edit Configurations…
  2. Click +Shell Script (or External Tool in older IDEs).
  3. Set:
    • Name: LoopCLI Run Current
    • Script path: loopcli
    • Program arguments: loop run $FileNameWithoutExtension$
    • Working directory: $ProjectFileDir$
  4. Duplicate the configuration for deploys (loop deploy … --activate).

Now you can run loops with Ctrl+Shift+F10 (Windows/Linux) or ⌃⇧R (macOS).

3. Tool window shortcuts

  • Pin the built-in terminal to the bottom and run loopcli loop run --watch your-loop for live logs.
  • Add External Tools entries for connectors (Slack, Stripe, Supabase) so you can run setup commands without leaving the IDE.
  • Use Favorites to bookmark .loop.yml files you edit frequently.

4. Fleet-specific tips

Fleet auto-detects loopcli if it’s on PATH. Open the command palette (Cmd+Shift+P) and search for LoopCLI commands after creating run configurations—they sync across machines.

5. Snippets & templates

  • Create Live Templates (Settings → Editor → Live Templates) for HTTP steps, retries, and connector scaffolds. Example:
name: $NAME$
 type: http
 config:
   method: $METHOD$
   url: $URL$
  • Scope the template to YAML so it auto-inserts inside .loop.yml files.

6. Troubleshooting

Issue Fix
LoopCLI command fails in Run configuration Toggle “Shell path” to /bin/zsh or /bin/bash so the IDE loads your shell environment.
Secrets unavailable Use loopcli secret add from the terminal; map environment variables in the Run configuration if needed.
Fleet doesn’t see updated PATH Restart Fleet after modifying PATH; on Windows launch Fleet from a shell once to inherit PATH changes.

Next steps

  • Combine JetBrains automation with Starter Recipes to ship loops quickly.
  • Explore Account & Billing to manage team access when multiple developers run loops from the IDE.
  • Need another JetBrains-specific feature? Raise it in Discord; we track requests for the Fleet roadmap there.

Related Documentation

Continue learning with these related topics