Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current workspace.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.
日本語の概要は準備中です。原文の説明を表示しています。
Drives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA traces. Use for any interactive browser task; not for a plain search or an unblocked static fetch.
日本語の概要は準備中です。原文の説明を表示しています。
QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real ~/.codex. The first-party method drives the real `codex app-server` against an isolated CODEX_HOME plus a LOCAL mock model (no real API call), and proves a plugin hook fired by asserting hook/started + hook/completed notifications. Also: isolated install verification, per-component hook probes, a tmux TUI smoke, and runtime log observation (RUST_LOG / logs SQLite / /debug-config). Ships tested helper scripts each with a --self-test. Use whenever someone changes anything under packages/omo-codex or wants to QA, smoke-test, verify, or debug the Codex plugin, its hooks/components, the installer/config.toml, the app-server flow, or the Codex TUI. Triggers: codex qa, qa codex, codex-qa, test codex plugin, verify codex hook, codex app-server, lazycodex qa, isolated CODEX_HOME, prove codex hook fired, codex tui test.
日本語の概要は準備中です。原文の説明を表示しています。
Finds, reads, and reconstructs coding-agent sessions across Codex, Claude, OpenCode, OMO/Senpi, and other local agent logs. Use when asked to find or search past sessions, transcripts, or subagent runs, or to recover what an earlier session did.
日本語の概要は準備中です。原文の説明を表示しています。
Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
日本語の概要は準備中です。原文の説明を表示しています。
Stores a DAG definition once and re-runs it by name, instead of pasting the definition into every run. Use when the user wants to save a DAG, run a saved one, or schedule the same multi-agent graph repeatedly.
日本語の概要は準備中です。原文の説明を表示しています。