{
  "markdown": "<p align=\"center\">\n  <img src=\"src/assets/images/icon.png\" alt=\"Paths-LE Logo\" width=\"96\" height=\"96\"/>\n</p>\n<h1 align=\"center\">Paths-LE: Zero Hassle Path Extraction</h1>\n<p align=\"center\">\n  <b>Pull every file path out of the current file in one keystroke</b><br/>\n  <i>JavaScript, TypeScript, JSON, YAML, HTML, CSS, TOML, CSV and Environment files — and every other file, by text scan</i>\n</p>\n\n<p align=\"center\">\n  <a href=\"https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.paths-le\">\n    <img src=\"https://img.shields.io/badge/Install%20from-VS%20Code-blue?style=for-the-badge&logo=visualstudiocode\" alt=\"Install from VS Code Marketplace\" />\n  </a>\n  <a href=\"https://open-vsx.org/extension/OffensiveEdge/paths-le\">\n    <img src=\"https://img.shields.io/open-vsx/dt/OffensiveEdge/paths-le?style=for-the-badge&label=Open%20VSX&color=blue\" alt=\"Open VSX downloads\" />\n  </a>\n  <a href=\"https://www.npmjs.com/package/paths-le-mcp\">\n    <img src=\"https://img.shields.io/npm/v/paths-le-mcp?style=for-the-badge&label=MCP%20server&color=blue&logo=npm\" alt=\"paths-le-mcp on npm\" />\n  </a>\n  <a href=\"https://crates.io/crates/paths-le\">\n    <img src=\"https://img.shields.io/crates/v/paths-le?style=for-the-badge&label=Rust%20CLI&color=blue&logo=rust\" alt=\"paths-le on crates.io\" />\n  </a>\n  <a href=\"https://letools.dev/tools/paths-le\">\n    <img src=\"https://img.shields.io/badge/LE%20Tools-letools.dev-blue?style=for-the-badge\" alt=\"LE Tools\" />\n  </a>\n</p>\n\n---\n\n<p align=\"center\">\n  <img src=\"src/assets/images/demo.gif\" alt=\"Paths-LE Demo\" style=\"max-width: 100%; height: auto;\" />\n</p>\n\n> **Useful?** A star or rating is how other developers find it —\n> [★ GitHub](https://github.com/nolindnaidoo/paths-le) ·\n> [★ Open VSX](https://open-vsx.org/extension/OffensiveEdge/paths-le/reviews) ·\n> [★ Marketplace](https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.paths-le&ssr=false#review-details)\n\n## What it does\n\nOpen a file, press `Ctrl+Alt+P` (`Cmd+Alt+P` on Mac), and every file path in the document lands in a new editor — deduplicate and sort it from there. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).\n\n- **Import analysis** — extract local imports from JS/TS, including multi-line import statements; npm package names are filtered out\n- **Asset auditing** — every `src`, `href`, `srcset`, `url()`, and `@import` in HTML/CSS\n- **Config review** — path-like values from JSON/JSONC, YAML, TOML, CSV, and `.env` files\n- **Anything else** — Python, Go, Markdown, XML, a Dockerfile: no parser, so a text scan finds quoted filenames and any run carrying a path separator\n\n## Install\n\n| Where | What you get | Install |\n|---|---|---|\n| **VS Code** | The extraction, in your editor, on a keystroke | [Marketplace](https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.paths-le) |\n| **Cursor, VSCodium, Windsurf** | The same extension | [Open VSX](https://open-vsx.org/extension/OffensiveEdge/paths-le) |\n| **A terminal or a CI step** | The same run over a whole tree, with exit codes | `cargo install paths-le` · [crates.io](https://crates.io/crates/paths-le) |\n| **Any MCP agent, via Node** | `extract_paths` over stdio — the same tool this binary offers | `npx paths-le-mcp` · [npm](https://www.npmjs.com/package/paths-le-mcp) |\n| **Zed** | The MCP server as a context server | [add it by hand](https://zed.dev/docs/ai/mcp) *(no listing yet)* |\n\n## Use it from an AI agent\n\nThe same engine runs as an [MCP](https://modelcontextprotocol.io) server, so an agent can call it directly instead of you running a command.\n\n| Editor | How |\n|---|---|\n| **VS Code** 1.101+ | Nothing to install — the extension registers `extract_paths` with agent mode |\n| **Zed** | No listing yet — [add the MCP server by hand](https://zed.dev/docs/ai/mcp) |\n| **Claude Code** | `claude mcp add paths-le -- npx -y paths-le-mcp` |\n| **Cursor, Windsurf, anything else** | point it at `npx paths-le-mcp` |\n\n```\nextract_paths(content, format?, filename?, dedupe?, maxResults?)\n```\n\nReturns every path classified as file, relative, absolute or url, with its 1-based line and column. Paths are reported exactly as written — nothing is resolved against a workspace or touched on disk.\n\nThe server takes content and returns data — it reads no files and makes no network requests of its own. Published as [`paths-le-mcp`](https://www.npmjs.com/package/paths-le-mcp) on npm and as `io.github.nolindnaidoo/paths-le` in the [MCP registry](https://registry.modelcontextprotocol.io).\n\n<details>\n<summary><b>Configuring it by hand</b> — any host with an MCP config file</summary>\n\nMost hosts read a JSON config. Add one entry:\n\n```json\n{\n  \"mcpServers\": {\n    \"paths-le\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"paths-le-mcp\"]\n    }\n  }\n}\n```\n\n`-y` skips the install prompt on first run. Pin a version if you would rather not track releases — `paths-le-mcp@2.3.1`.\n\nPrefer not to go through `npx` on every launch? Install it once and point at the binary instead:\n\n```bash\nnpm install -g paths-le-mcp\n```\n\n```json\n{\n  \"mcpServers\": {\n    \"paths-le\": { \"command\": \"paths-le-mcp\" }\n  }\n}\n```\n\nIt speaks MCP over stdio and needs no environment variables, no API key and no configuration of its own. To check it before wiring it into anything:\n\n```bash\necho '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/list\"}' | npx -y paths-le-mcp\n```\n\nThat prints the tool list and exits — if you see `extract_paths`, the server works.\n\n</details>\n\n## The CLI\n\nThe same extraction runs from a terminal or an agent loop: a Rust CLI in\n[`crate/`](crate/) of this repository, sharing one corpus with the extension —\n[`crate/fixtures/`](crate/fixtures/) — so CI fails if the two ever read a\ndocument differently.\n\nIt also does the half an editor cannot: **resolve what it found against the\nfilesystem it is standing in.** Every path gets a verdict — exists, missing,\nescapes the audited tree, non-canonical, or a symlink with its target named.\n\n```bash\npaths-le .                    # audit a tree; JSON on stdout, summary on stderr\npaths-le --strict .           # count sloppily-written paths too\npaths-le --no-resolve src/    # just list what is written, touch nothing\npaths-le mcp                  # the same audit over MCP on stdio\n```\n\nThe exit code is the answer: **0 clear · 1 findings · 2 the question was\nmalformed** — so `paths-le --strict .` is a CI step as it stands.\n\n## Supported formats\n\n| Format | Language IDs | What gets extracted |\n|---|---|---|\n| JavaScript / TypeScript | `javascript`, `javascriptreact`, `typescript`, `typescriptreact` | `import`/`export … from`, side-effect imports, dynamic `import()`, `require()` — file paths only, package names excluded |\n| JSON / JSONC | `json`, `jsonc` | Path-like string values (comments and trailing commas supported) |\n| HTML | `html` | `src`, `href`, `srcset` (each entry), `action`, `poster`, and similar attributes |\n| CSS / SCSS / LESS | `css`, `scss`, `less` | `url()` and `@import` |\n| TOML | `toml` | Path-like values and keys |\n| CSV | `csv` | Path-like cells |\n| Environment | `dotenv`, `env` | Path-like variable values and names |\n| YAML | `yaml` | Path-like scalar values and keys, across every document in the file |\n| Everything else | any other language ID | A text scan: quoted tokens, and undelimited runs that carry a path separator |\n\nPositions are real source positions for JS/TS, JSON/JSONC, HTML, CSS and the text scan (exact line and column of the path); TOML and YAML positions are located in the source text and can be approximate for repeated identical values; CSV positions are row/cell coordinates. Version strings (`1.8.1`) and IP addresses are never treated as paths, and `data:`/`javascript:` URLs are excluded from HTML/CSS extraction. Known limitation: bare domains like `example.com` are indistinguishable from filenames and are extracted.\n\nThe text scan claims a bare `name.ext` only inside quotes. `os.path` in a Python file and `main.py` are the same shape, and no rule short of a dictionary separates them — but source quotes its filenames and does not quote its attribute access, so the quoting does. A YAML scalar holding a shell command (`run: node ./scripts/build.js`) is one token containing spaces, so no path is claimed from it, exactly as in JSON and TOML.\n\n## Commands\n\n| Command | Description |\n|---|---|\n| `Paths-LE: Extract Paths` (`Ctrl+Alt+P` / `Cmd+Alt+P`) | Extract all paths from the active document |\n| `Paths-LE: Deduplicate Paths` | Remove duplicate lines from the results |\n| `Paths-LE: Sort Paths` | Sort results alphabetically or by length |\n| `Paths-LE: Open Settings` | Open Paths-LE settings |\n| `Paths-LE: Help` | Built-in documentation |\n\n## Settings\n\n| Setting | Default | Description |\n|---|---|---|\n| `paths-le.openResultsSideBySide` | `true` | Open results beside the current editor |\n| `paths-le.postProcess.openInNewFile` | `true` | Open results in a new file (when not side-by-side) |\n| `paths-le.copyToClipboardEnabled` | `false` | Also copy results to the clipboard |\n| `paths-le.notificationsLevel` | `silent` | `all` = every notification, `important` = warnings + errors, `silent` = errors only |\n| `paths-le.safety.enabled` | `true` | Guardrails for very large files |\n| `paths-le.safety.fileSizeWarnBytes` | `1000000` | Refuse extraction above this file size |\n| `paths-le.safety.largeOutputLinesThreshold` | `50000` | Warn above this line count |\n| `paths-le.statusBar.enabled` | `true` | Show the status bar item |\n| `paths-le.telemetryEnabled` | `false` | Local-only event log (see Privacy) |\n| `paths-le.resolution.resolveSymlinks` | `false` | ⚠️ Resolve symlinks to canonical paths |\n| `paths-le.resolution.resolveWorkspaceRelative` | `false` | ⚠️ Resolve paths against workspace folders |\n\n## Languages\n\nTwelve languages besides English:\n\nGerman · Spanish · French · Indonesian · Italian · Japanese · Korean ·\nPortuguese (Brazil) · Russian · Ukrainian · Vietnamese · Chinese (Simplified)\n\nBoth halves are covered — the manifest (command titles, setting names and\ndescriptions) and everything shown while the extension runs (notifications,\nthe status bar, quick-picks and prompts). The extension follows VS Code's\ndisplay language, so it matches whatever the editor is already set to; no\nsetting of its own.\n\n## Privacy & security\n\n- **No network access.** The extension never sends data anywhere. The `telemetryEnabled` setting only writes events to a local Output Channel you can inspect (`Paths-LE Telemetry`).\n- **Canonical resolution is opt-in and warned.** Resolving symlinks/workspace-relative paths can put absolute filesystem paths into the results document; the extension warns before first use. Leave both `resolution.*` settings off unless you need them.\n- **The MCP server holds the same line.** It takes content as an argument and returns data: no filesystem access, no network calls, no telemetry. Your agent already has file-read tools, so duplicating them inside the server would add a path-traversal surface for no capability. `check:mcp-bundle` fails the build if the server ever imports something that could reach either.\n- Error notifications redact home directories and credential-shaped fragments.\n\n## Documentation\n\n| What | Where |\n|---|---|\n| What the tool is allowed to say — scope, output contract, refusals, non-goals | [`crate/SPEC.md`](crate/SPEC.md) |\n| How the extension is built and held together — architecture, invariants, toolchain, release | [AGENTS.md](AGENTS.md) |\n| How the CLI is built and held together | [`crate/AGENTS.md`](crate/AGENTS.md) |\n| What changed | [CHANGELOG.md](CHANGELOG.md) · [`crate/CHANGELOG.md`](crate/CHANGELOG.md) |\n| The tool's page, and the other fifteen | [letools.dev/tools/paths-le](https://letools.dev/tools/paths-le) |\n\n## Performance\n\n<!-- performance:start -->\n| Input | Size | Found | Time | Rate | Scan speed |\n| --- | --- | --- | --- | --- | --- |\n| TypeScript imports | 2.10 MB | 40,000 | 19.85 ms | 2,015,130/sec | 105.9 MB/s |\n| JSON config | 1.17 MB | 40,001 | 23.17 ms | 1,726,103/sec | 50.6 MB/s |\n| HTML document | 1.27 MB | 40,000 | 18.64 ms | 2,146,436/sec | 67.9 MB/s |\n| CSS stylesheet | 1.57 MB | 40,000 | 16.47 ms | 2,428,210/sec | 95.3 MB/s |\n| CSV data | 2.09 MB | 60,000 | 67.22 ms | 892,581/sec | 31.1 MB/s |\n\nMedian of 7 runs after warmup, on Apple M5 Pro, 24 GB RAM, Node 24.3.0. Inputs are generated\nby `scripts/benchmark.ts` rather than checked in, so the sizes above are\nexactly what was measured. Reproduce with `bun run benchmark`.\n\nThese are machine-specific and are not asserted in CI — a benchmark that gates\na build only tells you how busy the runner was.\n<!-- performance:end -->\n\n## Testing\n\n<!-- coverage:start -->\n| Metric | Coverage |\n| --- | --- |\n| Statements | 92.70% |\n| Branches | 87.04% |\n| Functions | 94.93% |\n| Lines | 93.67% |\n\n318 test cases across 22 files, plus an integration suite that runs\nin a real VS Code extension host and an end-to-end test that installs the\nbuilt `.vsix` into a clean profile.\n\nGenerated from a real run — `coverage/coverage-summary.json` and\n`coverage/test-results.json` — by `scripts/coverage-readme.js`; CI fails if\nthis section drifts. Reproduce with `bun run test:coverage`, and the case\ncount is the one vitest prints.\n<!-- coverage:end -->\n\n## More from the LE family\n\nSixteen single-purpose tools for the work in front of every model. Each ships\na Rust CLI and an MCP server. One page: **[letools.dev](https://letools.dev)**\n\n**Get it out**\n\n- **[String-LE](https://letools.dev/tools/string-le)** — Extract every string in a codebase, with its position, so a person can read them\n- **[Numbers-LE](https://letools.dev/tools/numbers-le)** — Extract every hardcoded number in a codebase, so a person can check them\n- **[Units-LE](https://letools.dev/tools/units-le)** — Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name\n- **[Dates-LE](https://letools.dev/tools/dates-le)** — Extract every date and timestamp, and the exact instant each one resolves to\n- **[IDs-LE](https://letools.dev/tools/ids-le)** — Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside\n- **[IPs-LE](https://letools.dev/tools/ips-le)** — Extract every IP address, CIDR block and MAC, normalized and classified by scope\n- **[URLs-LE](https://letools.dev/tools/urls-le)** — Extract every URL in a codebase, with its protocol and exact position\n- **[Paths-LE](https://letools.dev/tools/paths-le)** — Extract every file path in a codebase, and say whether it still points at anything\n- **[Colors-LE](https://letools.dev/tools/colors-le)** — Extract every color in a codebase, and say which ones are not in your palette\n\n**Check it**\n\n- **[Regex-LE](https://letools.dev/tools/regex-le)** — Find every regex in a codebase, and report which can be driven into catastrophic backtracking\n- **[Versions-LE](https://letools.dev/tools/versions-le)** — Find where one dependency is constrained differently across a repository's manifests\n- **[i18n-LE](https://letools.dev/tools/i18n-le)** — Identify the i18n library a project uses, then audit its catalogs by that library's rules\n- **[Scrape-LE](https://letools.dev/tools/scrape-le)** — Check whether a page is scrapeable before the scraper is written, and say when it cannot tell\n\n**Guard it**\n\n- **[Secrets-LE](https://letools.dev/tools/secrets-le)** — Find hardcoded credentials in a codebase, and never print one into the report\n- **[EnvSync-LE](https://letools.dev/tools/envsync-le)** — Compare the dotenv files in a tree, and say which keys are missing from which\n- **[Unicode-LE](https://letools.dev/tools/unicode-le)** — Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts\n\nEach stands on its own: no shared crate, no published core. Where two of them\nagree, it is because the same answer was right twice.\n\n**Contact** — [nolindnaidoo.com](https://nolindnaidoo.com) · [GitHub](https://github.com/nolindnaidoo) · [LinkedIn](https://www.linkedin.com/in/nolindnaidoo/)\n\n## Also by nolindnaidoo\n\n**Rust** — pixelcoords and pixelactions are one loop: pixelcoords answers\n*where*, pixelactions *acts* there. Their own tools, their own voice — not\npart of the LE family.\n\n- **[pixelcoords](https://github.com/nolindnaidoo/pixelcoords)** — Freeze your screen, mark regions, get pixel-exact coordinates and crops\n  [pixelcoords.dev](https://pixelcoords.dev) · [crates.io](https://crates.io/crates/pixelcoords) · [docs.rs](https://docs.rs/pixelcoords)\n- **[pixelactions](https://github.com/nolindnaidoo/pixelactions)** — Consume human-verified coordinates, perform the interaction, confirm it landed\n  [pixelactions.dev](https://pixelactions.dev) · [crates.io](https://crates.io/crates/pixelactions) · [docs.rs](https://docs.rs/pixelactions)\n\n## License\n\nMIT © [nolindnaidoo](https://github.com/nolindnaidoo)\n",
  "bytes": 16859,
  "sha": "a46a58706f972a44350b718e2834aa9d9e8e513695971d4f2cf8a2f0931892a5",
  "repo_slug": "nolindnaidoo/paths-le",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_nolindnaidoo_paths_le_512f830b/readme"
}