Proposal: Expose LSP/Language Service capabilities (e.g., rename) via a tsc subcommand

[trim21]

🔍 Search Terms

lsp rename refactor

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

As AI coding agents evolve, structured program manipulation becomes increasingly vital. While tsc currently excels at type-checking and emitting JavaScript, programmatic refactoring (such as symbol renaming) is only exposed through the Language Service API in Node.js or via standard LSP integration over IPC.

To better support CLI-driven agent workflows, we should consider exposing core Language Service features through dedicated tsc subcommands (e.g., tsc rename ).

Prior Art / Motivation:
Other language toolchains already offer similar CLI interfaces for headless program transformation. For instance, Go provides native subcommand/tooling support via gopls (e.g., gopls rename ...), allowing external CLI tools and AI agents to execute deterministic, workspace-wide symbol renames without needing to boot a full LSP client or write custom Node.js wrappers around typescript.createLanguageService.

Exposing this in tsc would provide:

A standardized, zero-dependency CLI interface for AI agents to perform refactoring safely.

Deterministic AST/type-aware renaming out of the box for automated workflows.

Reduced friction for CLI tool developers who currently have to mock or bridge LSP protocols.

📃 Motivating Example

 $ gopls rename --help
rename selected identifier

Usage:
  gopls [flags] rename [rename-flags] <position> <name>

Example:

        $ # 1-based location (:line:column or :#position) of the thing to change
        $ gopls rename helper/helper.go:8:6 Foo
        $ gopls rename helper/helper.go:#53 Foo

rename-flags:
  -d,-diff
        display diffs instead of edited file content
  -l,-list
        display names of edited files
  -preserve
        with -write, make copies of original files
  -w,-write
        write edited content to source files

💻 Use Cases

1. agent vibe coding

[RyanCavanaugh]

There are already MCP adapters for LSP. Evidence that this would be better-exercised than the status quo would be a first step.

[trim21]

There are already MCP adapters for LSP. Evidence that this would be better-exercised than the status quo would be a first step.

Yeah I know it's possible to do this with LSP protocol, but the LSP protocol doesn't guarantee that rename actions would cover the full project. for example, when indexing, the rename would return partial reference that is not a very type-safe operator, which is also the behavoir of current tsserver

[trim21]

there is another direction on this, we have some kind of option that require full indexing on lsp requests so it fit the agent scenario