Windows: codex-cli 0.144.6 panics with chrono::offset::local::No such local time

Open
#34,127 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

Start by reproducing the startup crash outside VS Code with codex-cli 0.144.6 on Windows 11 using the reported Iran Standard Time timezone. Inspect the panic location in chrono-0.4.43/src/offset/local/mod.rs:193 and verify that the CLI no longer crashes at startup and that the VS Code extension can leave “Thinking...”.

Written by the indexing model from the issue text.

Description

app bug CLI windows-os
What version of the Codex App are you using (From “About Codex” dialog)?

0.144.6

What subscription do you have?

Free

What platform is your computer?

Microsoft Windows NT 10.0.22621.0 x64

What issue are you seeing?

Problem:
Running codex immediately crashes with:

Message: No such local time
Location: chrono-0.4.43/src/offset/local/mod.rs:193

The same panic occurs in the VS Code Codex extension, which stays on "Thinking..." because the embedded CLI crashes during startup.

Troubleshooting performed:

  • Verified Windows timezone and locale
  • Verified system date/time
  • Reinstalled Codex
  • Deleted ~/.codex
  • Reproduced outside VS Code
What steps can reproduce the bug?

Environment:

  • Windows 11 22H2 (22621.4317)
  • Node v22.16.0
  • npm 10.2.5
  • codex-cli 0.144.6
  • Installed via npm
  • Locale: en-US
  • Timezone: Iran Standard Time (UTC+03:30)
  • TZ environment variable not set
What is the expected behavior?

No response

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.