Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
55 changes: 54 additions & 1 deletion .codex/config.toml
Original file line number Diff line number Diff line change
@@ -1,10 +1,26 @@
model = "gpt-5.2-codex"
sandbox_mode = "workspace-write"
[sandbox_workspace_write]
network_access = true
[features]
rmcp_client = true
web_search_request = true

[mcp_servers.aws-docs]
command = "uvx"
args = ["awslabs.aws-documentation-mcp-server@latest"]

[mcp_servers.aws-knowledge]
url = "https://knowledge-mcp.global.api.aws"

[mcp_servers.chrome-devtools]
command = "npx"
args = ["chrome-devtools-mcp@latest"]

[mcp_servers.next-devtools]
command = "npx"
args = ["-y", "next-devtools-mcp@latest"]

Comment on lines +16 to +23

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

cat -n .codex/config.toml

Repository: keito4/config

Length of output: 3094


🌐 Web query:

npx -y flag interactive prompt behavior documentation

💡 Result:

In npm v7+, npx is effectively npm exec, and it will prompt interactively before installing anything (e.g., “Need to install… Ok to proceed?”) to reduce mistakes like typosquatting. You can suppress that prompt with:

  • npx -y <pkg> … or npx --yes <pkg> … → automatically answers “yes” to the install prompt (non-interactive/CI-friendly). [1]
  • npx --no <pkg> … → automatically answers “no” (fails instead of prompting). [1]

Important CLI parsing detail:

  • When using the npx binary, all flags must come before positional args, so --yes must appear before the package name. [2]
    • Example: npx --yes create-next-app@latest (not npx create-next-app@latest --yes). [2]

Sources: npm npx docs (prompt + -y/--yes/--no) [1], npm npm exec docs (flag ordering / parsing behavior) [2].

[1] https://docs.npmjs.com/cli/v10/commands/npx/
[2] https://docs.npmjs.com/cli/v7/commands/npm-exec/


🌐 Web query:

chrome-devtools-mcp npm latest version

💡 Result:

The latest npm version of chrome-devtools-mcp is 0.2.7 (published ~16 hours ago on npm). [1]


🌐 Web query:

@playwright/mcp npm latest version

💡 Result:

The latest npm version of @playwright/mcp is 0.0.55 (dist-tag: latest) as of January 29, 2026. [1][2]


🌐 Web query:

next-devtools-mcp npm latest version

💡 Result:

The latest published version of next-devtools-mcp on npm is 0.3.10 (tagged/released Jan 8, 2026). [1][2]

Install: npm i next-devtools-mcp@0.3.10 [2]

Use latest via npx: npx -y next-devtools-mcp@latest [1]

Sources:
[1] https://github.com/vercel/next-devtools-mcp/tags
[2] https://www.jsdelivr.com/package/npm/next-devtools-mcp


Add -y flag to all npx calls and consider pinning MCP versions.

npx (npm v7+) prompts interactively before installing packages without -y, which will hang in non-interactive environments. Both chrome-devtools-mcp and @playwright/mcp are missing this flag. Additionally, pinning versions instead of @latest prevents nondeterministic installs (e.g., pin to chrome-devtools-mcp@0.2.7, @playwright/mcp@0.0.55).

Proposed fix
 [mcp_servers.chrome-devtools]
 command = "npx"
-args = ["chrome-devtools-mcp@latest"]
+args = ["-y", "chrome-devtools-mcp@0.2.7"]

 [mcp_servers.next-devtools]
 command = "npx"
-args = ["-y", "next-devtools-mcp@latest"]
+args = ["-y", "next-devtools-mcp@0.3.10"]

 [mcp_servers.playwright]
 command = "npx"
-args = ["@playwright/mcp@latest"]
+args = ["-y", "@playwright/mcp@0.0.55"]
🤖 Prompt for AI Agents
In @.codex/config.toml around lines 16 - 23, Update the npx invocations for
mcp_servers.chrome-devtools and mcp_servers.next-devtools to include the
non-interactive flag and pin explicit MCP versions: modify the args arrays for
the sections named mcp_servers.chrome-devtools and mcp_servers.next-devtools to
include "-y" (so npx runs non-interactively) and replace "@latest" with concrete
versions (e.g., chrome-devtools-mcp@0.2.7 and next-devtools-mcp or
`@playwright/mcp` pinned to a specific version such as `@0.0.55`) to ensure
deterministic installs.

[mcp_servers.playwright]
command = "npx"
args = ["@playwright/mcp@latest"]
Expand All @@ -15,7 +31,7 @@ args = ["o3-search-mcp"]
env = { OPENAI_API_KEY = "${OPENAI_API_KEY}", SEARCH_CONTEXT_SIZE = "medium", REASONING_EFFORT = "medium" }

[mcp_servers.supabase]
url = "https://mcp.supabase.com/mcp"
url = "https://mcp.supabase.com/mcp?project_ref=zjfngnetdzgofqmteqja"

[mcp_servers.supabase.http_headers]
Authorization = "Bearer ${SUPABASE_MCP_TOKEN}"
Expand All @@ -40,3 +56,40 @@ trust_level = "trusted"

[projects."/Users/keito4/develop/github.com/keito4/config"]
trust_level = "trusted"

[projects."/Users/keito4/develop/github.com/Elu-co-jp/platform-infra"]
trust_level = "trusted"

[projects."/Users/keito4/develop/github.com/Elu-co-jp/opt_ai_manager"]
trust_level = "trusted"

[projects."/workspaces/management_tools"]
trust_level = "trusted"

[projects."/workspaces/cloud_provisioning"]
trust_level = "trusted"

[projects."/Users/keito4/develop/github.com/Elu-co-jp/cloud_provisioning"]
trust_level = "trusted"

[projects."/workspaces/opt_ai_manager"]
trust_level = "trusted"

[projects."/workspaces/job_description"]
trust_level = "trusted"

[projects."/workspaces/pulse_survey"]
trust_level = "trusted"

[projects."/Users/keito4/develop/github.com/Elu-co-jp/job_description"]
trust_level = "trusted"

[projects."/workspaces/raycast-extensions"]
trust_level = "trusted"
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved

[notice]
hide_gpt5_1_migration_prompt = true
"hide_gpt-5.1-codex-max_migration_prompt" = true

[notice.model_migrations]
"gpt-5.1-codex-max" = "gpt-5.2-codex"