Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Add fish support for Unix command execution shell detection [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20259•Fetched 2026-04-30 06:30:59
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
explainanalyzeexplainanalyze
Participants
explainanalyzeexplainanalyzegithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

What problem are you seeing?

Codex does not appear to support fish as a Unix command execution shell. On macOS, my terminal and login environment use fish, but Codex command execution falls back to zsh. That means commands do not see the same shell-managed environment as my terminal.

This affects PATH setup, version managers, and session-based environment like 1Password/op auth state.

Thread ID: 019ddadd-5da7-7c92-8c75-c1563a6c8c4c

Feedback upload URL suggested by Codex:

https://github.com/openai/codex/issues/new?template=3-cli.yml&steps=Uploaded%20thread:%20019ddadd-5da7-7c92-8c75-c1563a6c8c4c

Expected behavior

If $SHELL or the passwd shell points to fish, Codex should either support fish command execution directly or provide an explicit config option for the default command shell.

Actual behavior

Codex detects supported Unix shells such as zsh/bash/sh, but fish is not treated as a supported shell for command execution, so the session uses a fallback shell.

Concrete ask

Add fish to the supported Unix shell detection and execution paths, likely using fish -c for non-login execution and the appropriate fish equivalent for places where Codex currently uses login-shell semantics.

Environment

  • Codex CLI: 0.125.0
  • Platform: macOS arm64
  • Login shell: fish (/opt/homebrew/bin/fish)
  • Observed command shell in Codex tool execution: zsh

extent analysis

TL;DR

The most likely fix is to add support for fish as a Unix command execution shell in Codex, allowing it to use the same shell-managed environment as the terminal.

Guidance

  • Verify that the $SHELL environment variable is set to the path of the fish executable (/opt/homebrew/bin/fish) to ensure Codex detects it as the default shell.
  • Check if there are any existing configuration options in Codex to specify the default command shell, which could be used as a temporary workaround.
  • To add support for fish, investigate using fish -c for non-login execution, as suggested in the issue.
  • Test the behavior with other shells (e.g., zsh, bash) to confirm the issue is specific to fish.

Example

No code snippet is provided, as the issue is related to shell support rather than a specific code problem.

Notes

The solution may require changes to the Codex codebase to add support for fish as a supported shell. The issue is specific to macOS and fish shell, so the fix may not apply to other platforms or shells.

Recommendation

Apply a workaround by setting the SHELL environment variable or using a different shell until fish support is added to Codex. This is because adding support for fish may require code changes, and using a workaround can provide a temporary solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

If $SHELL or the passwd shell points to fish, Codex should either support fish command execution directly or provide an explicit config option for the default command shell.

#API routing#API middleware#SSR setup#ISR setup#authentication setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Add fish support for Unix command execution shell detection [1 comments, 2 participants]