“Open in PyCharm” does nothing after upgrading to PyCharm 2026.2 on macOS
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.803.61601 (build 6396)
What subscription do you have?
Plus
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
After upgrading PyCharm to 2026.2, clicking Open in PyCharm on a local file link no longer has any visible effect.
The Codex desktop log shows that Codex detects and invokes PyCharm, but the launcher exits with code 1:
[open-in-service] Failed to open file
errorMessage="/Applications/PyCharm.app/Contents/MacOS/pycharm exited with code 1
(--line 2028 --column 1 /Users/<user>/Documents/workspace/<project>/src/api/api.py)"
Running the same command directly returns:
unrecognized option: --line
Codex does not surface this error in the UI, so the action appears to do nothing. This worked before upgrading PyCharm.
What steps can reproduce the bug?
- Install or upgrade to PyCharm 2026.2 on macOS.
- Open a Codex task containing a clickable local file reference with a line number.
- Right-click the file reference.
- Select Open in PyCharm.
- Observe that PyCharm does not navigate to the file and Codex shows no error.
The command recorded in the Codex log is:
/Applications/PyCharm.app/Contents/MacOS/pycharm \
--line 2028 \
--column 1 \
/Users/<user>/Documents/workspace/<project>/src/api/api.py
The target file exists and the requested line is within the file. The command exits with code 1 and prints unrecognized option: --line.
What is the expected behavior?
PyCharm should open the referenced file and navigate to the specified line and column.
If launching the IDE fails, Codex should display an actionable error instead of silently doing nothing.
Additional information
Environment
- PyCharm:
2026.2.0.1 - PyCharm build:
PY-262.8665.369 - macOS:
26.5.1 - Architecture: Apple Silicon (
arm64)
Regression
The feature worked before upgrading PyCharm and stopped working immediately after upgrading to PyCharm 2026.2.
The same error occurs with PYCHARM_VM_OPTIONS unset:
env -u PYCHARM_VM_OPTIONS \
/Applications/PyCharm.app/Contents/MacOS/pycharm \
--line 2028 \
--column 1 \
/Users/<user>/Documents/workspace/<project>/src/api/api.py
Opening the file without line arguments works:
open -a "PyCharm" "/Users/<user>/Documents/workspace/<project>/src/api/api.py"
Codex currently invokes the internal macOS executable directly. PyCharm 2026.2 rejects the --line and --column arguments when invoked this way. The integration may need to use the supported macOS launcher mechanism (for example, open ... --args) or otherwise update its PyCharm 2026.2 handling.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Open in PyCharm action and reproduce the logged macOS launcher command with the reported PyCharm version. Trace how the command is built and how launcher failures are handled. Done means local file links open at the requested line and column, or a clear actionable error is shown when launching fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 66/100