[Bug]: Pi setup suggests installation without guiding reuse of an existing off-PATH runtime and profile

Abierto
  • ¿Algo no está bien?
#36,157 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@juliusmarminge ya está trabajando en esto.

Desde el 13/11/2026.

  • #36162 de @juliusmarminge — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
node.js, typescript
Área
frontend

Línea de trabajo

The report concerns the Pi provider card under apps/web, specifically the 'Not found' diagnostic shown when the default pi command is missing from PATH. Start by locating that message and the Binary path setting it should reference. Done means the failure text points to both installing Pi and setting Binary path, and mentions PI_CODING_AGENT_DIR for an existing profile. Pull request #36162 already targets this, so check it before starting.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Before submitting
  • I searched existing issues and did not find an exact duplicate.
  • I included the observed setup, executable verification, and related reports.
Area

apps/web

Steps to reproduce

Observed on an existing macOS installation:

  1. Have Pi Web installed in a user-level, isolated runtime, with its own Pi agent directory and existing custom-model configuration.
  2. Launch T3 Code desktop and enable Pi in Settings → Providers. Leave Binary path at its default, pi.
  3. The Pi executable is not on T3's PATH, although it exists inside the Pi Web runtime.
  4. Open the Pi provider card.
Actual behavior

The card shows:

Not found · Pi CLI (pi) is not installed or not on PATH. Install with npm install -g --ignore-scripts @earendil-works/pi-coding-agent.

The installation instruction is prominent, while this diagnostic does not point to Binary path or explain that an existing installation may use a separate agent directory.

In this case, Pi was already installed and its GUI service was running. The existing CLI answered:

node "$HOME/Library/Application Support/Pi Agent/runtime/node_modules/@earendil-works/pi-coding-agent/dist/bundle/cli.js" --version
# 1.5.0

There is also a runtime/node_modules/.bin/pi symlink. The existing profile is under $HOME/Library/Application Support/Pi Agent/agent, and already contains custom-model configuration.

The lookup failure itself is understandable: this private runtime is outside PATH. The problem is the recovery guidance. It encouraged a reinstall diagnosis even though the executable and configuration were already present.

Expected behavior

The default-command lookup failure should point directly to both supported recovery options:

  • Install Pi if it is absent.
  • Reuse an existing executable through Binary path.

For an existing installation, setup should also explain PI_CODING_AGENT_DIR so users can retain their models, authentication, and extensions rather than accidentally starting with a different profile. A file/directory picker or clear inline example would make this much easier.

This is a setup/diagnostic usability report, not a claim that T3 should automatically scan and execute arbitrary bundled dependencies. The provider documentation already describes manual configuration; the missing guidance is in the failure state where it is needed.

Impact

Minor bug or occasional failure. It makes a working installation look like it needs another installation and makes reuse of an existing model profile difficult to discover.

Version or commit

T3 Code (Beta) 0.1.9

Environment

macOS 27.0, arm64; Node.js 24.14.1; Pi Web @agegr/[email protected]; bundled @earendil-works/[email protected].

Workaround / verification limits

The existing CLI was verified directly. Configuring T3 with that executable and the original agent directory is the documented reuse route, but I have not yet completed an end-to-end T3 conversation with this installation.

Related: #35373 concerns a nonexistent custom Binary path; here the default lookup is used and the real executable exists elsewhere. #28714 concerns startup PATH capture, not discovery of a GUI-private runtime.

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
59 min
PR fusionados (30 d)
418

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.