Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Call lsp MCP tools through the tool interface; lsp.*/mcp__lsp__* are tool-call names, not shell commands.
lsp.status: list configured, installed, missing, disabled, and active language servers.lsp.diagnostics: check one file or directory for LSP diagnostics. Prefer severity: "error" after edits.lsp.goto_definition: locate a symbol definition from file, line, and character.lsp.find_references: find usages of a symbol across the workspace.lsp.symbols: inspect document symbols or search workspace symbols.lsp.prepare_rename: check whether a rename is valid at a position.lsp.rename: apply a language-server workspace edit for a rename.Project config lives at .codex/lsp-client.json; user config lives at ~/.codex/lsp-client.json.
{
"lsp": {
"typescript": {
"command": ["typescript-language-server", "--stdio"],
"extensions": [".ts", ".tsx", ".js", ".jsx"]
}
}
}
Use lsp.status first when diagnostics report a missing language server.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Removes AI-generated code smells from a SINGLE file while preserving functionality. For multiple files, call in PARALLEL per file.
The English summary is being prepared. Showing the original description.
Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
The English summary is being prepared. Showing the original description.
MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async misbehavior, unexplained timing, reverse engineering. Runs a hypothesis-driven loop: form ≥3 hypotheses, investigate in parallel, after 2 failed rounds spawn Oracles from orthogonal angles, confirm root cause, lock with a failing test, fix minimally, QA by actually USING the system, scrub artifacts. The actual HOW lives in `references/` — READ THEM. Triggers: 'debug this', 'why is X not working', 'hanging', 'attach a debugger', 'reverse engineer', 'pwndbg', 'gdb', 'lldb', 'node inspect', 'tsx debug', 'pdb', 'dlv', 'delve', 'rust-gdb', 'set a breakpoint', 'context window exploded', 'why is the response empty', 'attach the debugger', 'debug it', 'why is this happening', 'trace this bug', 'reproduce and fix', 'silent failure', 'HTTP 200 but empty', 'why did it stop', 'inspect the binary', 'reverse engineering', 'playwright'.
The English summary is being prepared. Showing the original description.
Designer-turned-developer who crafts stunning UI/UX even without design mockups
The English summary is being prepared. Showing the original description.
(builtin) Initialize hierarchical AGENTS.md knowledge base
The English summary is being prepared. Showing the original description.
Strategic planning consultant that produces decision-complete work plans through Socratic interview, codebase exploration, Metis gap analysis, and optional Momus high-accuracy review. MUST USE when the task has 5+ steps, scope is ambiguous, multiple modules are involved, or the user asks for a plan. Triggers: plan this, create a work plan, interview me, start planning, prometheustic, plan mode, help me plan this, break this down.
The English summary is being prepared. Showing the original description.