Linuxbrew-installed tmux is missing from trusted helper lookup, disabling terminal pets
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 72/100
Línea de trabajo
Lee utils/path-utils/src/system_commands.rs, especialmente system_directories() e installation_roots(), y luego sigue cómo system_executable("tmux") valida las rutas. Revisa las pruebas existentes para la búsqueda de herramientas auxiliares de confianza y añade cobertura para ejecutables bajo el prefijo estándar de Homebrew en Linux. El trabajo estará terminado cuando se pueda encontrar Linuxbrew tmux y se siga aplicando la política de herramientas auxiliares de confianza.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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?
- On Linux, install tmux through Homebrew into
/home/linuxbrew/.linuxbrew, without another tmux installation in the trusted system locations. - Start tmux in Ghostty or Kitty.
- Set and apply
set -g allow-passthrough allin tmux. - Enable
fullscreen_transcript = trueunder[tui]in Codex's configuration. - Start Codex CLI 0.169.0 and select a terminal pet, for example
/pets rocky. - 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.rscallssystem_executable("tmux")and returns default options when it cannot find the helper. That leaveskitty_image_baseunset.utils/path-utils/src/system_commands.rsdeliberately ignores ambientPATH. Itssystem_directories()andinstallation_roots()include macOS Homebrew locations but omit/home/linuxbrew/.linuxbrew/binand/home/linuxbrew/.linuxbrew.- The helper lookup canonicalizes executable paths before validating them, so a symlink in
/usr/local/binpointing to the Linuxbrew installation would still be rejected. pets/image_protocol.rsonly 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.
- Lenguaje dominante
- Rust
- Estrellas
- 135k
- Forks
- 21.4k
- Merge medio
- 1 min
- PR fusionados (30 d)
- 998
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de openai/codex
-
CLI config custom-model enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
app documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
openai/codex#61678 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
app auth bug windows-os
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
app bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
Los mantenedores suelen responder en 1 día
-
ImageGen generate-batch aborts valid JSONL jobs containing a Unicode line separator in poster textAbiertobug imagen skills
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
openai/codex#61442 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de openai/codex
Issues similares
-
bug ui
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
userFRM/egui-charts#3363 ·
Los mantenedores suelen responder en 1 día
-
ada documentation mobile report
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
physicsdolphin/nv-uefi-unlocker#254 · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
kindraywind/rustnarok-client#1382 ·
Los mantenedores suelen responder en 1 día
-
area:accessibility bug good first issue help wanted priority:p3-low size:small
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
NecturaLabs/Canopy#209 ·
-
marketing
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día