Strings-LE

[Strings-LE Logo]

Strings-LE: Zero Hassle String Extraction

Pull every string value out of the current file in one keystroke
JSON/JSONC, YAML, CSV/TSV, TOML, INI, Environment files, and ten source languages

[Install from VS Code Marketplace] [Open VSX downloads] [string-le-mcp on npm] [strings-le on npm] [string-le on crates.io] [LE Tools]

[Strings-LE in VS Code]

Useful? A star or rating is how other developers find it — ★ GitHub · ★ Open VSX · ★ Marketplace

What it does

Open a file, run String-LE: Extract Strings, and every string value 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).

• i18n prep — flatten locale files (JSON/YAML) into a clean list of translatable values
• Config review — see every string value in a TOML/INI/.env file at a glance
• CSV mining — pull one column, several, or all of them; stream very large files

Install

Use it from an AI agent

The same engine runs as an MCP server, so an agent can call it directly instead of you running a command.

[An agent in Claude Code calling the string-le MCP server]

extract_strings(content, format?, filename?, dedupe?, multiline?, maxResults?)

Returns the values in document order, capped at 500 by default with meta.truncated. A format is optional — any unrecognised format falls back to quoted strings.

The server takes content and returns data — it reads no files and makes no network requests of its own. Published as string-le-mcp on npm and as io.github.nolindnaidoo/string-le in the MCP registry.

{  "mcpServers": {    "string-le": {      "command": "npx",      "args": ["-y", "string-le-mcp"]    }  }}

npm install -g string-le-mcp

{  "mcpServers": {    "string-le": { "command": "string-le-mcp" }  }}

echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | npx -y string-le-mcp

Supported formats

Values are trimmed; empty values are dropped; keys are never extracted — one rule, shared by every extractor above. The fallback scan cannot see unquoted strings, which is why the parsed formats and the source languages get real readers; it reads a quoted run across lines when string-le.fallback.multiline is on (the MCP tool's multiline). Parse errors are silent unless string-le.showParseErrors is on.

Across a folder or a workspace

Extract reads the document you have open. A scan reads many files from disk and gives one report.

• The whole workspace: run String-LE: Extract Strings from Workspace from the command palette.
• One folder: right-click it in the Explorer and choose Extract Strings from Folder, or run String-LE: Extract Strings from Folder and pick one.

A project writes the same string in many places, so the report is the distinct strings, the most widely used first, with how often each is written and where. Every string is in the table. Most are written once, and such a one is placed in its row. A repeated one gets a section below that lists each place:

# String-LE workspace report
`my-project` · 4 file(s) read · 3 distinct string(s), 7 occurrence(s) in 3 file(s)
| String | Occurrences | Files | Where ||---|---|---|---|| `Save changes` | 4 | 3 | || `Cancel` | 2 | 2 | || `Press Enter` | 1 | 1 | `src/b.py` · **2:8** |
## `Save changes` (4)
- `i18n/en.json` · **2:11**- `src/a.ts` · **1:11**, **3:11**- `src/b.py` · **1:9**
## `Cancel` (2)
- `i18n/en.json` · **3:13**- `src/a.ts` · **2:11**
## Could not be read (1)
- `bad.json`: Invalid JSON: Expected value after colon in object property on line 1 column 6

Positions follow string-le.showPositions. With it off, each line is the file and how many times the string is in it: src/a.ts (2). The copy on the clipboard follows string-le.clipboardIncludesPositions, as it does for Extract.

A file its format reader could not parse is listed with the reason, never passed over. A string longer than 120 characters, or one with a line break, is shown as one cut line. Two strings are still compared whole.

What a scan reads. Files come from disk, so an unsaved edit is not seen. A file over the safety size, or one that is not UTF-8 text, is left unread. It stops at 5,000 files or 10,000 listed occurrences. The report ends with a line for each thing it left out, so a short report is never mistaken for a clean project.

What it skips, and how to change that. Three switches are on by default, and each can be turned off on its own in Settings:

Two lists adjust the result without turning a switch off. To skip more, add a pattern to scanExcludes. To read something a switch would skip, add it to scanAlwaysInclude:

{	// Also skip the test fixtures.	"string-le.workspace.scanExcludes": ["**/fixtures/**"],	// Read the vendored code, though the built-in list skips it.	"string-le.workspace.scanAlwaysInclude": ["**/vendor/**"]}

String-LE: Open Settings opens all of these in the Settings editor.

The settings that shape a scan are under Settings.

The CLI

The same extraction runs from a terminal or a shell pipeline: a Rust CLI in crate/, sharing one corpus with the extension — crate/fixtures/ — so the two can never read a document differently. Install it from npm with npm install -g strings-le (or run it with npx strings-le) or from crates.io with cargo install string-le. Both install the same command and are held to the same output byte for byte, apart from the words a parser uses to refuse a broken document.

string-le .                      # every string in the tree; JSON on stdout when pipedstring-le --values src/          # just the values, one per linestring-le --dedupe --values .    # each distinct string oncestring-le mcp                    # the same extraction over MCP on stdio
# the point of the whole thing:string-le --values --dedupe src/ | sort > after.txtdiff before.txt after.txt        # what changed in the copy this release

[string-le in a terminal]

Install it from npm (strings-le) or from crates.io (string-le). Both install the same string-le command.

[strings-le on npm] [string-le on crates.io]

npm install -g strings-le   # or run it once: npx strings-lecargo install string-le

The reader is not the author. The extension answers for the buffer you have open. Someone still has to read every user-visible string before a release — a QA lead, a compliance reviewer, a localisation owner — and they do not have the editor open, and several of them cannot be handed a checkout at all. The CLI puts the whole repository into one file they can read.

Source files are the main event there. A .ts or .py file is where the user-facing copy lives, so each language is read by its own literal syntax and anything still unrecognised falls through to quoted-string extraction rather than being refused.

Exit codes follow grep — 0 strings found, 1 none found, 2 the question was malformed — so finding nothing is an answer rather than an error.

Commands

No command is bound to a key by default. Give any of them one under Keyboard Shortcuts in the editor.

Settings

Languages

Twelve languages besides English:

German · Spanish · French · Indonesian · Italian · Japanese · Korean · Portuguese (Brazil) · Russian · Ukrainian · Vietnamese · Chinese (Simplified)

Both halves are covered — the manifest (command titles, setting names and descriptions) and everything shown while the extension runs (notifications, the status bar, quick-picks and prompts). The extension follows VS Code's display language, so it matches whatever the editor is already set to; no setting of its own.

Privacy & security

• No network access. The extension never sends data anywhere. The telemetryEnabled setting only writes events to a local Output Channel you can inspect (String-LE).
• 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.
• Error notifications redact home directories and credential-shaped fragments.
• One rating prompt, at most twice. On the 3rd successful use the extension asks once whether you would rate it, and once more on the 20th if you chose Later or dismissed it. Don't Ask Again ends it. Setting notificationsLevel to important or silent yourself turns it off. The counts are kept in VS Code's extension storage and nothing is sent anywhere; Rate opens the listing you installed from — the VS Code Marketplace or Open VSX — in your browser.

Documentation

Performance

Median of 7 runs after warmup, on Apple M5 Pro, 24 GB RAM, Node 24.3.0. Inputs are generated by scripts/benchmark.ts rather than checked in, so the sizes above are exactly what was measured. Reproduce with bun run benchmark.

These are machine-specific and are not asserted in CI — a benchmark that gates a build only tells you how busy the runner was.

Testing

533 test cases across 43 files, plus an integration suite that runs in a real VS Code extension host and an end-to-end test that installs the built .vsix into a clean profile.

Generated from a real run — coverage/coverage-summary.json and coverage/test-results.json — by scripts/coverage-readme.js, and bun run coverage:readme:check says whether it has drifted since. Reproduce with bun run test:coverage, and the case count is the one vitest prints.

More from the LE family

Sixteen single-purpose tools for the work in front of every model. Each ships a Rust CLI and an MCP server. One page: letools.dev

Get it out

• String-LE — Extract every string in a codebase, so a person can read them
• Numbers-LE — Extract every hardcoded number in a codebase, so a person can check them
• Units-LE — Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name
• Dates-LE — Extract every date and timestamp, and the exact instant each one resolves to
• IDs-LE — Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside
• IPs-LE — Extract every IP address, CIDR block and MAC, normalized and classified by scope
• URLs-LE — Extract every URL in a codebase, with its protocol and exact position
• Paths-LE — Extract every file path in a codebase, and say whether it still points at anything
• Colors-LE — Extract every color in a codebase, and say which ones are not in your palette

Check it

• Regex-LE — Find every regex in a codebase, and report which can be driven into catastrophic backtracking
• Versions-LE — Find where one dependency is constrained differently across a repository's manifests
• i18n-LE — Identify the i18n library a project uses, then audit its catalogs by that library's rules
• Scrape-LE — Check whether a page is scrapeable before the scraper is written, and say when it cannot tell

Guard it

• Secrets-LE — Find hardcoded credentials in a codebase, and never print one into the report
• EnvSync-LE — Compare the dotenv files in a tree, and say which keys are missing from which
• Unicode-LE — Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts

Each stands on its own: no shared crate, no published core. Where two of them agree, it is because the same answer was right twice.

Contact — nolindnaidoo.com · GitHub · LinkedIn

Also by nolindnaidoo

Rust — pixelcoords and pixelactions are one loop: pixelcoords answers where, pixelactions acts there. Their own tools, their own voice — not part of the LE family.

• pixelcoords — Freeze your screen, mark regions, get pixel-exact coordinates and crops pixelcoords.dev · crates.io · docs.rs
• pixelactions — Consume human-verified coordinates, perform the interaction, confirm it landed pixelactions.dev · crates.io · docs.rs

License

MIT © nolindnaidoo