fix(cursor): prevent cross-account Max Mode capability leakage - #401
fix(cursor): prevent cross-account Max Mode capability leakage#401luvs01 wants to merge 10 commits into
Conversation
release: promote dev into main for v2.32.1
# Conflicts: # package.json
[WRONG BRANCH] merge dev into main for the v2.33.0 release
Promotes the dev integration line onto main. The resulting tree is byte-identical to origin/dev, including package.json at 2.34.0. The package.json conflict is resolved to dev's side, NOT to main's stale 2.33.0. Earlier promotions (lidge-jun#2553, lidge-jun#2507) kept the target's version so the release bump would land on its own "release: vX.Y.Z" commit. That is no longer legal: this very delta adds tests/release-version-line.test.ts, which fails when the in-tree version sits behind the highest release tag. With v2.34.0-preview.20260827 now published, 2.33.0 orders behind it, so a promotion carrying the stale line turns CI red on every shard that runs the suite. The consequence for the release step is that scripts/release.ts skips the bump (release.ts:568, currentVersion === version), so v2.34.0 gets tagged on this merge commit rather than on a separate release commit. The workflow creates the tag itself after publishing and validates expected-sha against the checked-out commit, so the tag still names exactly the audited tree.
[WRONG BRANCH] promote dev onto main for v2.34.0
[WRONG BRANCH] promote dev onto main for v2.35.0
[WRONG BRANCH] promote dev onto main for v2.36.0
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ Deterministic PR hygiene checks passed. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
github-actions
Bot
changed the title
✅ READY
Hygiene✅ Deterministic PR hygiene checks passed. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c0c47c363a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const ultraRequested = parsed.ultra || reasoning?.toLowerCase() === "ultra"; | ||
| const evidence = liveMaxModeIds ?? liveCursorMaxModeBases; | ||
| const maxModeArmed = capability.maxModeVerified === true || evidence.has(parsed.baseId); | ||
| const maxModeArmed = capability.maxModeVerified === true || liveMaxModeIds?.has(parsed.baseId) === true; |
There was a problem hiding this comment.
For an account whose GetUsableModels response marks an otherwise-unverified model as Max-Mode capable, Ultra requests now silently omit the maxMode wire flag. This resolver's new argument is never supplied by production code: src/adapters/cursor/request-builder.ts:215 still calls it with only two arguments, while this commit also discards liveResult.maxModeModels in provider-fetch.ts, so only the statically verified kimi-k3 can use Max Mode. Preserve the evidence in a provider/credential-scoped store, pass the selected route's set into request construction, and add a focused discovery-to-request regression test.
AGENTS.md reference: AGENTS.md:L336-L339
Useful? React with 👍 / 👎.
luvs01
changed the title
2 participants
Motivation
GetUsableModelsmax-mode evidence into a process-global singleton, letting one provider/account's results affect requests routed to other providers or accounts.Description
liveCursorMaxModeBasessingleton and itsrecordLiveCursorMaxModeModelsmutation from the catalog code.src/codex/catalog/provider-fetch.tsso provider fetch remains account-scoped and only caches the discovered roster.resolveCursorSelection; otherwise, only staticmaxModeVerifiedcapability can arm Max Mode (src/adapters/cursor/catalog.ts).tests/cursor-umbrella-rows.test.ts).Testing
bun test tests/cursor-umbrella-rows.test.ts tests/cursor-catalog.test.ts tests/cursor-ultra-mode.test.ts, all tests in those files passed.bun run test, which completed with tests passing in this environment (no new failures observed).bun run typecheckpassed andbun run privacy:scanpassed.bun run test:changedcould not run because this checkout has nodev/origin/dev/upstream/devcomparison ref; this is an environment limitation, not a code failure.Codex Task