You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove broken background spec fetch; use synchronous timeout
The previous 3-second-timeout-with-background-continuation design was
broken: the background thread was a daemon, so when the 3s join timeout
expired and the CLI raised, the process exited and killed the thread
before it could cache the spec. Users on slow networks would hit the
timeout on every invocation with no path forward.
Replace with a straight synchronous fetch that relies on the HTTP
client's own timeout. First call on a cold cache may take a few seconds;
every subsequent call within the TTL is served from disk. Update README
and docstring to match.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- **Read-only today.** Only `GET` endpoints are exposed in this beta.
665
665
- **Spec-driven.** Adding a new endpoint to the API surfaces it automatically the next time the cache is refreshed.
666
-
- **No bundled spec.** The first `cycode platform` invocation after install (or after the 24h cache expires) will perform a network fetch with a 3-second timeout; if it times out, it continues fetching in the background so the next run is fast.
666
+
- **No bundled spec.** The first `cycode platform` invocation after install (or after the 24h cache expires) performs a network fetch. On slow connections this first call may take a few seconds; subsequent calls are near-instant until the cache expires.
667
667
- **Override the cache TTL** with `CYCODE_SPEC_CACHE_TTL=<seconds>`.
0 commit comments