Linuxbrew-installed tmux is missing from trusted helper lookup, disabling terminal pets

オープン 初心者向け
#62,005 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
72/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
linux, rust
領域
cli, tooling

調査の方向性

utils/path-utils/src/system_commands.rsを読み、特にsystem_directories()とinstallation_roots()を確認してから、system_executable("tmux")がパスを検証する方法を追ってください。信頼できるヘルパーの検索に関する既存のテストを確認し、Linuxの標準Homebrewプレフィックス配下にある実行ファイルのテストを追加してください。Linuxbrewのtmuxを検出でき、信頼できるヘルパーのポリシーが引き続き適用されていれば完了です。

索引モデルが issue の本文から書いたものです。

説明

bug CLI pets TUI
What version of Codex CLI is running?

codex-cli 0.169.0 (also the npm latest version when checked on November 17, 2026).

What subscription do you have?

Not included; this failure occurs during local terminal capability detection.

Which model were you using?

The identified failure is in local TUI startup/helper discovery, before a model response is needed.

What platform is your computer?

Ubuntu 26.04.1 LTS, x86_64.

Linux 7.0.0-43-generic x86_64 unknown
What terminal emulator and version are you using?

Ghostty 1.4.0, with tmux 3.8 installed through Homebrew on Linux.

Codex doctor report

Relevant excerpt from codex doctor --json, collected in a noninteractive diagnostic subprocess:

{
  "codexVersion": "0.169.0",
  "installation": {
    "current executable": "/home/linuxbrew/.linuxbrew/Caskroom/codex/0.169.0/bin/codex"
  },
  "terminal.env": {
    "terminal": "Ghostty",
    "tmux options": "not inspected (PATH helpers are not executed)"
  }
}
What issue are you seeing?

Terminal pets do not appear inside tmux even with fullscreen Codex, allow-passthrough all, and a selected pet (rocky). The tmux session reports Ghostty and RGB support.

The installed tmux is discoverable from the shell:

$ command -v tmux
/home/linuxbrew/.linuxbrew/bin/tmux
$ readlink -f /home/linuxbrew/.linuxbrew/bin/tmux
/home/linuxbrew/.linuxbrew/Cellar/tmux/3.8/bin/tmux

There is no tmux executable in the trusted search locations on this machine.

Live tmux state:

$ tmux display-message -p 'fullscreen=#{alternate_on} passthrough=#{allow-passthrough} terminal=#{client_termname} type=#{client_termtype}'
fullscreen=1 passthrough=all terminal=xterm-ghostty type=ghostty 1.4.0

#{client_termfeatures} also includes RGB.

What steps can reproduce the bug?
  1. On Linux, install tmux through Homebrew into /home/linuxbrew/.linuxbrew, without another tmux installation in the trusted system locations.
  2. Start tmux in Ghostty or Kitty.
  3. Set and apply set -g allow-passthrough all in tmux.
  4. Enable fullscreen_transcript = true under [tui] in Codex's configuration.
  5. Start Codex CLI 0.169.0 and select a terminal pet, for example /pets rocky.
  6. Observe that pets remain unavailable despite the supported terminal, fullscreen mode, and passthrough setting.
What is the expected behavior?

Codex should discover a tmux installation under the standard Linux Homebrew prefix and enable pets when the other capability checks pass. If that installation is intentionally unsupported, the diagnostic should explain the helper-discovery failure rather than only suggesting fullscreen/passthrough settings that are already enabled.

Additional information

Source inspection in the rust-v0.169.0 tag identifies the failing lookup:

  • tui/src/tui/tmux.rs calls system_executable("tmux") and returns default options when it cannot find the helper. That leaves kitty_image_base unset.
  • utils/path-utils/src/system_commands.rs deliberately ignores ambient PATH. Its system_directories() and installation_roots() include macOS Homebrew locations but omit /home/linuxbrew/.linuxbrew/bin and /home/linuxbrew/.linuxbrew.
  • The helper lookup canonicalizes executable paths before validating them, so a symlink in /usr/local/bin pointing to the Linuxbrew installation would still be rejected.
  • pets/image_protocol.rs only enables the tmux pet protocol when the fullscreen image base is available.

The trusted-helper policy was introduced in #42324. This report concerns coverage of the standard Linux Homebrew prefix while preserving that policy.

The cause above is based on source inspection and the installed executable paths. Installing/copying tmux into another location has not been tested as a workaround.

主要言語
Rust
スター
135k
フォーク
21.4k
平均マージ
1分
マージ済み PR(30日)
998

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

openai/codex のほかの issue

openai/codex の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。