Repository navigation
quest: record what blocks the Cursor reviewer harness - #778
Conversation
Quest-Claim: 82bbcb2161d3c467
No maintainer host has a logged-in Cursor CLI, and token-max cannot price Cursor sessions, so the harness's isolation, model ids, error shapes, and eval cannot be verified. Record both under Waiting, and correct the isolation guidance from the CLI bundle: CURSOR_CONFIG_DIR does not cover ~/.cursor/mcp.json, Claude plugins, or third-party skill directories. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 31 minutes. View limit details
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. |
|
No configured credential can serve this run. Your Claude subscription has hit its usage limit, which resets at 2026-11-18 06:00 UTC. Re-trigger after it resets, or add an API key for this provider, which Pullfrog falls back to automatically. The providers' responses
|
1 similar comment
|
No configured credential can serve this run. Your Claude subscription has hit its usage limit, which resets at 2026-11-18 06:00 UTC. Re-trigger after it resets, or add an API key for this provider, which Pullfrog falls back to automatically. The providers' responses
|
|
@pullfrog review this PR's head. (Written by Claude Opus 5.5 with high effort) |
|
No configured credential can serve this run. Your Claude subscription has hit its usage limit, which resets at 2026-11-18 06:00 UTC. Re-trigger after it resets, or add an API key for this provider, which Pullfrog falls back to automatically. The providers' responses
|
There was a problem hiding this comment.
ℹ️ Two small accuracy gaps — mergeable after a one-line fix.
Approach: sound. The PR records the outside waits under ## Waiting instead of shipping a harness against guessed model ids and an unverified isolation recipe. That is what the quest's own Guidance and the guide's Creation section ask for.
Reviewed changes — one quest file, quest/m1/cursor-reviewer.md, rewritten to the work that remains.
cursor-agentnaming: the login and status guidance now namescursor-agent, and a new bullet explains whyagentonPATHmay not be Cursor's.- Isolation guidance: a clean per-review
HOME,XDG_CONFIG_HOME,CURSOR_CONFIG_DIR, andCURSOR_DATA_DIRreplaces the claim that the twoCURSOR_*dirs are enough. It also covers where the login is stored on Linux and macOS, and adds skills and plugins to the live test's attack surface. ## Waiting: oneMaintainer:item to log in the Cursor CLI on a Linux host and a macOS host, and onekixel-ai/token-max:item to price Cursor sessions. Both say how to check them.
ℹ️ ## Goal still names the CLI as agent -p
The new Guidance bullet says to run the CLI as cursor-agent, not agent, because a Grok CLI also installs agent. The Goal, which this PR does not touch, still describes the harness as "Cursor's CLI (agent -p)". The guide says a PR that leaves work rewrites its quest to what remains, so the quest now contradicts itself, and an implementer who reads only the Goal gets the binary name this PR argues against.
Technical details
# Goal names the wrong binary
## Affected sites
- quest/m1/cursor-reviewer.md:5 — "through Cursor's CLI (`agent -p`)"
## Required outcome
- The Goal names `cursor-agent -p`, matching the Guidance bullet at line 31.claude-opus-5-5 | 𝕏
…d host quest Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — the delta since the prior pullfrog review (3c7d5ee → e05c80b), quest text only.
- Goal names
cursor-agent -p: the## Goalnow matches the Guidance bullet, closing the prioragent -pfinding. - Waiting item reworded: it says to plan each host's setup with
/quest-planin kixel-ai/dotfiles' quest tree, which had no such quest on 2026-11-17, closing the other prior thread.
claude-sonnet-5-5 | 𝕏

Records what blocks quest/m1/cursor-reviewer.md under its
## Waiting, and corrects its isolation guidance from Cursor CLI2026.11.05-86047df's bundle. This PR adds no harness code; it rewrites the quest to what remains, so merging it releases the claim and surfaces both waits inquest waiting.Why it stops here
Live verification of every step of the Plan needs a logged-in Cursor CLI: the isolation test, the model ids from
--list-models, Cursor's real usage-limit and logged-out output, andquest eval run. As of 2026-11-17, none of the maintainer's hosts had one: two had no Cursor CLI, one had only2025.10.01logged out, and on oneagentonPATHwas a Grok CLI. Writing the harness against guessed model ids, error shapes, and an unverified isolation recipe is what the coordinating brief and the Plan say not to do. token-max also has no Cursor transcript support, so the eval's culprits-per-dollar would be a lower bound.Changes
## Waiting:Maintainer:log the Cursor CLI in on a Linux host and a macOS host (browser OAuth on the maintainer's account, and the eval spends their Cursor plan);kixel-ai/token-max:price Cursor sessions, with the Plan's stream-usage fallback.~/.cursor/mcp.jsonand~/.claude/pluginsare read fromhomedir(), a workspace's.claude/settings.jsonenables Claude plugins, and skills load from.cursor/,.claude/,.codex/,.grok/, and.agents/in home and workspace, soCURSOR_CONFIG_DIR/CURSOR_DATA_DIRalone do not isolate. It now recommends a clean per-reviewHOME,XDG_CONFIG_HOME,CURSOR_CONFIG_DIR, andCURSOR_DATA_DIRthat hold only the login, plus the hidden flags and--sandbox enabled, and says where the login lives on Linux (auth.json) and macOS (keychain) so its refresh token is not split.cursor-agent, notagent: nixpkgs'cursor-cli(unfree) installs onlycursor-agent, and a Grok CLI also installsagent.cursor-agent -p, and the host-setupMaintainer:item says the dotfiles quest is still to plan.Decisions
Made without asking, for review:
quest guide, Creation).Follow-ups
For
/quest-planin other repositories' quest trees:cursor-agent, at least2026.11.13-eacade1) on a Linux and a macOS host. ✅ Keep (maintainer, 2026-11-17; rejected: drop). Still open, the maintainer answering "not yet": whether an agent may drive the maintainer's signed-in browser throughNO_OPEN_BROWSER=1 cursor-agent login(recommended: yes, the maintainer authorizes it once per host);/quest-planthere keeps it as aMaintainer:decision.token-max sessions; it needs a logged-in CLI to see the transcript format first. ✅ Keep (maintainer, 2026-11-17; rejected: drop, pricing from Cursor's stream instead).Public API
None: quest text only.
Validation
nix build nixpkgs#cursor-cli(unfree) gave2026.11.05-86047df; read its--helpand greppedshare/cursor-agent/index.jsfor the config, MCP, plugin, skill, and credential paths cited above.agent/cursor-agentandstatus.quest check,quest check --base origin/main,just check, andjust testpass.Models
Size: L
Implementer: Claude Code, claude-opus-5-5, medium effort (iterate, XS)
🤖 Generated with Claude Code
(Written by Claude Opus 5.5)
Review
Rewritten by
quest reviewafter each round.Head: e05c80b
Base: origin/main at 00c72eb
Risk: low,
Only a plan under quest/ changes, so no behavior users or other repositories rely on can break, and a revert fully undoes the edits.Classified: low by Codex, gpt-6.1-sol, low effort, session
01a1f2ca-34d7-7740-93d8-5c2f7c36c312Reviewer: Codex, gpt-6.1-sol, xhigh effort
Session:
01a1ebc9-e114-71f2-8b7d-fe9620f26204, round 2Score: 10/10,
The incremental edits clarify the Cursor CLI command and host-setup prerequisites without introducing actionable defects or changing runtime behavior.Rounds: 2; first round 0; findings 0: fixed 0, refuted 0, open 0
Findings: none
Reviewer: Codex, gpt-6.1-sol, high effort, shadow
Session:
01a1ebc9-e111-79a3-86c4-69c6cbeeb9bdRounds: 1; first round 0; findings 0: fixed 0, refuted 0, open 0