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
{{ message }}
Repository navigation
Commit 61d6d38
Browse filesBrowse the repository at this point in the historyBrowse files
jun
committed
feat(cursor): let the Codex Fast toggle reach Cursor's fast variant
Codex's Fast toggle is OpenAI's service_tier field, and Cursor has no such
field - its fast product is a different model variant
(claude-opus-5-thinking-high-fast) or a {id:fast} request parameter for Grok.
So a service_tier on a Cursor route was silently dropped, and no Cursor row
could advertise the toggle at all: FAST_WIRE_ADAPTERS is a closed set that
Cursor was not in.
Add a cursor-variant FastWire kind, declare it on the Cursor registry entry, and
have the request builder consume the tier DECISION (not the raw caller field, so
fastMode=false still suppresses a caller's request). A thinking umbrella pick
upgrades to thinkingFast rather than the regular-fast sibling, which is a
different product with a shorter ladder whose regular family is quarantined for
claude-opus-5.
Only the five bases that actually declare a fast variant advertise the tier, so
there is no dead toggle. That required one more fix: forwardCallerTier ignored
the wire's foreignCallerTiers declaration, so an unclassified cursor-variant
route projected 'unknown' support - enough for Codex to offer a toggle on
kimi-k3, which has no fast variant at all.
Telemetry recomputes the variant from the same pure inputs the builder uses.
Rebuilding the request there would be wrong twice over: tierLogForRunTurn runs
before runTurn, and createCursorRequest mints conversation ids.
Also widens the usage/log.ts wireKind allowlist, which silently returns null -
dropping the whole tier row - for a kind it does not recognise.
Refs devlog/_plan/260902_cursor_unified_identity/020_wp3_codex_fast_toggle.md
: `[opencodex] Cursor's transport limit allows ${kept.length} of ${kept.length+omitted.length} client tools this turn. Omitted and unavailable this turn: ${omittedSummary}.`;
181
181
}
182
182
183
+
/**
184
+
* True when this turn should take Cursor's fast variant.
185
+
*
186
+
* Reads the tier DECISION rather than the raw caller field so one authority owns precedence:
187
+
* `decideTier` has already applied config `fastMode`, the caller's `service_tier`, and the
188
+
* route's eligibility, so `fastMode: false` correctly suppresses a caller's Fast request.
189
+
* A `{kind:"set"}` decision on a Cursor route means canonical Fast survived that gate.
0 commit comments