CLI /ide cannot read PhpStorm / JetBrains IDE context even when Codex ACP integration is running

What version of Codex CLI is running?

codex-cli 0.141.0

Also installed/running locally:

• Codex desktop bundled CLI: codex-cli 0.142.0-alpha.6 from /Applications/Codex.app/Contents/Resources/codex
• PhpStorm: PhpStorm 2026.1.3, build PS-261.25134.104
• macOS: 26.5.1, build 25F80, Darwin 25.5.0, Apple Silicon / arm64

What subscription do you have?

ChatGPT account auth is configured in Codex. PhpStorm is currently a trial install, but the JetBrains-side Codex/ACP integration appears to start successfully.

Which model were you using?

gpt-5.5

What platform is your computer?

macOS 26.5.1 (25F80), arm64.

What terminal emulator and version are you using, if applicable?

PhpStorm integrated terminal / local Codex CLI on macOS.

Codex doctor report

Relevant summary from codex doctor --json:

codexVersion: 0.141.0
auth.credentials: ok, ChatGPT auth configured
config.load: ok, config.toml parse ok
installation: ok, PATH has ~/.local/bin/codex and /Applications/Codex.app/Contents/Resources/codex
network.provider_reachability: ok
network.websocket_reachability: ok, HTTP 101 Switching Protocols
runtime.provenance: standalone on macos-aarch64, version 0.141.0
app_server.status: ok / idle, background server not running in ephemeral mode

The only failing doctor check in my captured run was terminal.env: TERM=dumb, because I ran doctor from a non-interactive diagnostic shell. That does not match the actual PhpStorm terminal environment where the issue is observed.

What issue are you seeing?

When using Codex CLI from a PhpStorm project and running /ide, Codex fails to enable IDE context:

IDE context could not be enabled. Codex could not read IDE context. Try /ide again.

Expected IDE context would include the active PhpStorm file, current selection, and/or open files.

This is confusing because the JetBrains-side Codex/ACP integration appears to be running. Local process inspection shows PhpStorm has started Codex ACP/app-server processes, including:

npm exec @agentclientprotocol/codex-acp@0.0.46 -acp
node .../node_modules/.bin/codex-acp -acp
node .../@openai/codex/bin/codex.js app-server
.../@openai/codex-darwin-arm64/.../bin/codex app-server

PhpStorm plugin directories present locally include:

ej
laravel-idea
ml-llm
vitejs

So this does not look like a simple case where no JetBrains-side integration is running. It looks like the CLI /ide command cannot consume JetBrains/ACP-provided editor context, or the error message does not explain that JetBrains context is unsupported for CLI /ide.

What steps can reproduce the bug?

1. On macOS, open a project in PhpStorm 2026.1.3.
2. Make sure the JetBrains Codex/AI/ACP integration is active enough to start its ACP processes.
3. Open a file in PhpStorm and select some code.
4. Open PhpStorm's integrated terminal in the same project.
5. Start Codex CLI with codex.
6. Run /ide.

What is the expected behavior?

One of these should happen:

1. /ide should read the active PhpStorm editor context through the running JetBrains/ACP integration and attach the active file/selection/open files to the next prompt.
2. Or, if JetBrains IDE context is not currently supported by CLI /ide, the command should return a clear unsupported-surface message, for example: JetBrains IDE context is not available to Codex CLI /ide; use the JetBrains Codex integration or attach files manually.

What is the actual behavior?

/ide fails with:

IDE context could not be enabled. Codex could not read IDE context. Try /ide again.

Retrying does not make the PhpStorm context available.

Additional information

Related public reports / discussions:

• #24514 reports /ide failing to read VS Code IDE context from Codex CLI.
• #22648 tracks JetBrains Codex extension feature parity gaps.
• Discussion #26608 says JetBrains/GoLand selection detection is not exposed to CLI /ide via config-only setup today.

The main request here is either support for consuming JetBrains ACP/editor context from CLI /ide, or clearer documentation/error handling that JetBrains IDE context is not a supported provider for CLI /ide today.