Skip to content
| Marketplace
Sign in
Visual Studio Code>Visualization>loopfinderNew to Visual Studio Code? Get it now.
loopfinder

loopfinder

motimotinotch

|
3 installs
| (0) | Free
| Sponsor
Find the feedback loops in your workspace: trace your scripts with writes blocked, add the human/AI steps, and see every loop, including the ones you never declared.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

loopfinder for VS Code

日本語

Find the feedback loops in your workspace — including the ones you never meant to build.

The loopfinder CLI and viewer, inside the editor. No Node install needed: it runs on the editor's own runtime (Python is needed only to trace .py scripts).

Use

Run loopfinder: Get started from the Command Palette, or click loopfinder in the status bar once it is set up. It takes the folder to its next step:

  • Not set up yet: makes loopfinder/, then asks who should survey the workspace:
    • VS Code chat (agent mode) — opens the chat with the request filled in; you send it. Shown when the editor has a chat model.
    • Claude Code in a terminal — starts claude with the request in a new terminal. Shown when claude is on your PATH.
    • Another AI agent — copies the request for you to paste.
    • No AI — opens loopfinder/flows.json next to the guide, to write the flows yourself.
  • When the agent has written loopfinder/flows.json, loopfinder asks once: Build and show. Nothing runs before you click, because building runs the workspace's scripts. The question folds into the notification centre after a few seconds; until you build, the status bar reads loopfinder: Build the graph.
  • After that, the same command (or the status bar) shows the loops, or builds again if the flows changed.

The steps one by one, from the Command Palette:

  1. loopfinder: Set up this workspace — makes loopfinder/ (config.json, flows.json, AGENTS.md).
  2. Ask your AI agent (Claude Code, Codex, Cursor, Copilot, ...): "Read loopfinder/AGENTS.md and survey this workspace." (loopfinder: Copy the request for your AI agent puts it on the clipboard.) It writes loopfinder/flows.json.
  3. loopfinder: Build the graph — runs the traced scripts with writes blocked and draws the graph.
  4. loopfinder: Show the loops — opens the viewer. It redraws by itself after every build, from the palette or from loopfinder build in a terminal. Click a path in the side pane to open the file.

The viewer starts in the editor's display language. Picking a language with the button at the top of the viewer wins over it.

With three or more flows, the viewer's flow list starts with Overview (connections): every flow on one 3D graph, to see where flows meet. Drag to rotate, scroll to zoom, and pick a flow or a file to light it up.

Safety

Building really runs your scripts. Writes are recorded and dropped; network and subprocesses are blocked unless you turn on loopfinder.allowNetwork / loopfinder.allowSubprocess. It is a recorder, not a sandbox: do not trace code you would not run.

In a workspace you have not trusted, set up and build are off; you can still view a graph that is already built.

.loopfinder/ (the build output) lists your file paths. Keep it out of version control.

Support

Ko-fi · MIT License · bundles dagre and graphlib (MIT) and Lucide icons (ISC)

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft