<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title>Troubleshooting - 标签 - William</title>
    <link>https://williamlfang.github.io/tags/troubleshooting/</link>
    <description>Troubleshooting - 标签 | William</description>
    <generator>Hugo -- gohugo.io</generator><language>zh-CN</language><lastBuildDate>Fri, 06 Nov 2026 18:19:24 &#43;0800</lastBuildDate><atom:link href="https://williamlfang.github.io/tags/troubleshooting/" rel="self" type="application/rss+xml" /><item>
  <title>Codex startup: a shared model cache and a five-second timeout</title>
  <link>https://williamlfang.github.io/2026-11-06-codex-startup-model-cache/</link>
  <pubDate>Fri, 06 Nov 2026 18:19:24 &#43;0800</pubDate>
  <author>william</author>
  <guid>https://williamlfang.github.io/2026-11-06-codex-startup-model-cache/</guid>
  <description><![CDATA[<p>My Codex CLI sometimes paused for about five seconds when it started. Other
launches were almost immediate. After checking the
<a href="/2026-11-06-idc-v2raya-proxy-codex/">proxy setup</a>, I looked at
the startup logs. They showed <strong>a model-list request consuming five seconds</strong>
before timing out.</p>
<p>Three Codex versions were sharing the same model cache. A cache written by one
version could be rejected by another, which forced another network request.
I aligned the CLI with the shared server and changed the desktop launcher to
use the same CLI on its next launch. Five subsequent terminal checks reached
the model and prompt in a median of 0.80 seconds.</p>]]></description>
</item>
</channel>
</rss>
