Skip to content

[Bug]: Timeouts in Codex on WSL2 for specific backlog commands #586

@sylvia-schmitt

Description

@sylvia-schmitt

Describe the bug
Asking Codex CLI to run command like the follwing will fail (timeout), while running them directly from the terminal or web UI will work

  • backlog.task_list
  • backlog.task_archive
  • backlog.task_list
  • ... and a lot more

But asking Codex CLI to run commands like the following will work

  • backlog.task_view
  • backlog.task_edit

Since the same backlog commands work when run directly in the terminal and via the Backlog web UI, I am unsure whether this is caused by Codex CLI tool execution, the WSL2 environment, or a local configuration issue. Guidance on how to diagnose or rule out configuration problems would be helpful.

To Reproduce

  1. Open Codex CLI in WSL2
  2. Ask for listing backlog board
    "show me the backlog board"
    • I’m assembling a compact board view from the current tasks and milestones, then I’ll format it by status so it’s easy to scan.
    • Calling backlog.task_list({"limit":100})
     └ Error: tool call error: tool call failed for `backlog/task_list`
           Caused by:
               timed out awaiting tools/call after 120s
    
  3. Asking Codex to show a specific task will work, like "show task 2"
• I’m opening TASK-2 now so you can see the full backlog entry and its current state.
• Called backlog.task_view({"id":"TASK-2"})
  └ File: /home/<path>/.backlog/tasks/task-2 - <title>
    Task TASK-2 - Derive candidate ...
    ==================================================

    Status: ✔ Done
    Created: 2026-03-20 10:21
    Updated: 2026-03-20 20:01
    Dependencies: TASK-1
    References: ...

    Description:
    --------------------------------------------------
    Follow-up task to TASK-1. ...

Expected behavior

  • Codex CLI should either return the requested backlog list successfully, or fail quickly with a clear and actionable error message instead of timing out.
  • Behavior should be consistent with direct terminal usage, where the same backlog commands complete successfully.

Environment

  • WSL2 with Codex CLI which is directly installed in WSL2.
  • codex-cli 0.117.0
  • node v24.14.0
  • backlog 1.42.0

Additional context
The VSCode IDE plugin as well as the Codex Desktop App are both installed, but configured to use the WSL2 backend.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions