LSP support would improve cross-file project understanding

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.623.141536 • Released Jul 6, 2026

What subscription do you have?

Pro

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Codex works file-by-file and shell-by-shell. It has no integration with Language Server Protocol (LSP) servers, so it cannot query symbol definitions, find all references, resolve types, or ask a language server for project-wide understanding.

This causes Codex to propose changes that look correct in the current file but break callers in other files, miss existing utilities and re-implement them, or guess signatures instead of reading them from the project.

What steps can reproduce the bug?

Feedback ID: 019f3f0f-2314-7ff3-bb80-cf92eb22e6e3

What is the expected behavior?

Codex should be able to start/connect to language servers (e.g., typescript-language-server, rust-analyzer, pyright) and expose LSP queries as tools it can invoke, similar to read_file and shell.

Examples:

• definition for the symbol under the cursor
• references across the project
• hover for inferred types
• rename / workspace edits

This would let Codex plan multi-file changes against the real project graph instead of guessing from text.

Additional information

This is a feature request framed as a bug report because the issue template requires it. The underlying ask is for LSP integration. LSP gives a uniform interface across languages instead of Codex having to bundle per-language static analyzers.