Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

app-server rejects every turn with "invalid cwd" once the daemon's own working directory is deleted, even when the request cwd is absolute

Abierto Apto para principiantes
  • ¿Algo no está bien?
#51,152 1 comentario 0 reacciones 0 asignados Ver en GitHub

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
76/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust
Área
backend-api-design

Línea de trabajo

Empieza leyendo codex-rs/utils/absolute-path/src/lib.rs cerca de relative_to_current_dir; después, comprueba quién lo llama en codex-rs/app-server/src/request_processors.rs y los puntos de llamada de turn y resume mencionados en el issue. Se considera terminado cuando un cwd absoluto de la solicitud se resuelve aunque se haya eliminado el propio directorio de trabajo del daemon, mientras que las rutas relativas siguen resolviéndose respecto al directorio actual.

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

Descripción

app-server bug CLI

What happens

The shared app-server daemon starts with the working directory of the first codex invocation that spawns it. If that directory is later deleted (a removed git worktree, for example), every new turn/start on that daemon fails:

turn/start failed: invalid cwd: No such file or directory (os error 2) (code -32600)

This happens even though the turn's own cwd is an absolute path to a directory that exists. Every TUI attached to the daemon is affected until the daemon restarts. codex resume <thread> --no-daemon works around it for one session.

Why

resolve_request_cwd (codex-rs/app-server/src/request_processors.rs:629, rust-v0.160.0) resolves the request cwd with AbsolutePathBuf::relative_to_current_dir:

fn resolve_request_cwd(cwd: Option<PathBuf>) -> Result<Option<AbsolutePathBuf>, JSONRPCErrorError> {
    cwd.map(|cwd| {
        AbsolutePathBuf::relative_to_current_dir(path_utils::normalize_for_native_workdir(cwd))
            .map_err(|err| invalid_request(format!("invalid cwd: {err}")))
    })
    .transpose()
}

relative_to_current_dir (codex-rs/utils/absolute-path/src/lib.rs:87) calls std::env::current_dir()? unconditionally, before it looks at whether path is already absolute:

pub fn relative_to_current_dir<P: AsRef<Path>>(path: P) -> std::io::Result<Self> {
    Ok(Self::resolve_path_against_base(
        path,
        std::env::current_dir()?,
    ))
}

On Linux, getcwd fails with ENOENT when the process's cwd has been unlinked. So an absolute request path is rejected because of the daemon's own cwd, which the path does not depend on. The same call is used for turn/start (turn_processor.rs:621, :928) and thread resume (thread_processor.rs:3877).

Reproduce

  1. With no daemon running (codex app-server daemon stop), run mkdir /tmp/x && cd /tmp/x && codex. This starts the daemon with cwd /tmp/x. Exit the TUI.
  2. rm -rf /tmp/x
  3. cd ~/some/repo && codex, then send any prompt. The turn fails with invalid cwd.

Expected

An absolute request cwd resolves without consulting the process cwd. Only a relative request cwd needs current_dir(), and its error could say that the daemon's working directory no longer exists.

Possible fix: in relative_to_current_dir, return from_absolute_path(path) when path.is_absolute(), and call current_dir() only for relative input.

Related

The managed daemon and its updater both inherit the spawning terminal's cwd (codex app-server daemon start, and Daemon::stop leaves daemon-updater.pid running). So after stop + start, the next update recreates the daemon in the deleted directory again; only daemon bootstrap replaces both processes. Starting the managed daemon from a stable directory (for example $CODEX_HOME) regardless of the caller's cwd would remove the whole class.

Environment: codex-cli 0.160.0 (npm, linux-x64 musl), Ubuntu, managed app-server daemon (codex app-server --listen unix:// --managed-daemon).

Related report: #41559 (a session whose own cwd was removed). This issue is a different trigger: the request cwd exists and is absolute, and only the daemon process's cwd is gone.

Lenguaje dominante
Rust
Estrellas
127k
Forks
19.9k
Merge medio
1 min
PR fusionados (30 d)
994

Preparar el entorno

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 openai/codex

Todos los issues de openai/codex

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.