{"schemaVersion":"1.0","publication":{"slug":"pivot-cursor","name":"Cursor HQ","description":"Product updates and proven workflows for building software with Cursor.","audience":"Engineers and product teams using the Cursor editor.","geography":null},"edition":{"id":"45501760-ea88-4e93-bbcd-315f659561be","date":"2026-10-02","status":"locked","createdAt":"2026-10-01T16:34:36.560Z","storyCount":6,"newsletterSubject":"Grok Bots integrate Cursor Projects, Pro 500 plan hits limits fast, Six habits for Cursor Projects"},"updatedAt":"2026-10-01T17:00:30.376Z","stories":[{"id":"a847ab70-1ef4-4060-bcb5-41c1982873af","title":"Grok Bots can now use Cursor Projects, with Cursor's cloud agents doing the coding, users say","dek":"A Grok Bot is a bot you set up and message, for example in Slack; users say it can now send coding work to Cursor's cloud agents, which each have their own computer.","bodyMd":"Grok Bots, which are bots users set up and message, can now connect to Cursor Projects and record video demos of their work, according to posts on 30 September. One post describes the result as \"model-agnostic coding work with long-context conversations, from anywhere.\"\n\nThe Slack setup is the most concrete workflow described. A user says they create a new team engineer bot, add it to Slack, and then @-mention it whenever they want coding done. The bot can also be told to create new Projects, which the same post describes as a way to group many related agents into one conversation.\n\nThe coding itself runs on Cursor's cloud agents. According to that post, any model available in Cursor can be used with them, and because each cloud agent has its own computer, the bot acts more like a manager than a coder. That split is the practical point: the bot coordinates, and the agents do the typing on their own machines.\n\nAnother user calls the Cursor integration worth trying and compares it to phoning an assistant and telling them to get the factory building something new, by simply telling the bot to work on a big project in Cursor. That is one person's impression, not a measured result.\n\nA separate post says the Grok Bots that SpaceXAI's engineers use are free to import and remix. It adds that Cursor's SWE bot alone writes code, triages issues and monitors production.","status":"published","storyType":"news","category":"Ecosystem","clusterKey":"grok-bots-cursor-projects-integration","slug":"grok-bots-can-now-use-cursor-projects-with-cursor-s-cloud-agents-doing-t-a847ab","url":"https://cursorhq.ai/news/grok-bots-can-now-use-cursor-projects-with-cursor-s-cloud-agents-doing-t-a847ab/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/a847ab70-1ef4-4060-bcb5-41c1982873af","role":"lead","position":0,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/grok-bots-can-now-use-cursor-projects-with-cursor-s-cloud-agents-doing-t-a847ab/c7aa6df3d4d05030-c29bf76bf71500a3/web_hero.webp","imageAlt":"A communication hub device with an antenna connected to several individual, independent metal compute cartridges.","createdAt":"2026-10-01T16:50:18.100Z","updatedAt":"2026-10-01T17:00:30.376Z","sources":[{"role":"primary","title":"Grok Cloud Agents Now Work With Cursor Models in Slack for Team Coding","url":"https://x.com/poteto/status/2105377066942349794","sourceName":"lauren","author":"lauren","publishedAt":"2026-09-30T19:19:43Z"},{"role":"supporting","title":"Grok Bot Now Connects to Cursor for Hands-Free Project Delegation","url":"https://x.com/mikepat711/status/2105401258290848226","sourceName":"Mike P","author":"Mike P","publishedAt":"2026-09-30T20:55:51Z"},{"role":"supporting","title":"SpaceX AI Engineers' Grok Bots Are Now Free to Import and Remix","url":"https://x.com/kloss_xyz/status/2105397644940161422","sourceName":"klöss","author":"klöss","publishedAt":"2026-09-30T20:41:29Z"},{"role":"supporting","title":"Grok Bots Now Connect to Cursor Projects and Record Video Demos","url":"https://x.com/Baconbrix/status/2105381262559256604","sourceName":"Evan Bacon","author":"Evan Bacon","publishedAt":"2026-09-30T19:36:23Z"}]},{"id":"bbffe929-fc39-4179-aa65-de98ba4d7b42","title":"A builder says a \"Pro 500\" plan with Ultrafast used 20% of a weekly limit in 90 minutes","dek":"Vibin Signal frames the X post as a Cursor story, though the post never names Cursor; its author called the plan \"not worth it\" and wrote \"Opus 5.5 we are back.\"","bodyMd":"A builder posted on X on Sept. 30 that they tried a \"Pro 500 plan with Ultrafast\" and \"blew 20% of my WEEKLY limit in about 1.5 hours.\" Their verdict: \"Not worth it.\" They closed with \"Opus 5.5 we are back.\"\n\nThe post does not mention Cursor. The link to Cursor comes from a Vibin Signal page whose URL slug and title are written as a Cursor story (\"cursor-pro-500-burns-through-20-of-weekly-limits-in-90-minutes\"). That page carries a source date of Sept. 29, a day before the X post's Sept. 30 timestamp, so the two dates conflict. Treat the Cursor connection as the page's title and slug, not something the post itself states.\n\nIt is also one person's experience. It does not say what work the session involved or how Ultrafast is metered, so it cannot be read as a typical rate.\n\nSeparately, a post on r/cursor describes usage on a different plan: the $200-a-month Ultra tier. The subscriber, who signed up Sept. 2, shared figures from their own usage CSV and the `/api/usage-summary` endpoint, and stresses that the numbers are not official. Nothing in the post ties it to the \"Pro 500\" plan above.\n\nBy their account, the \"Other Models\" pool, which they say covered Opus 5.5, some Gemini and GPT-5.6 Sol use, was $400 that cycle, and they burned about $390 of it (the dashboard showed 98%). They say Auto requests that routed to Claude, GPT or Gemini also drew from that pool.\n\nThe poster says Cursor never prints a dollar cap for the first-party pool, which covers Grok and Composer, and that the docs just call it \"generous.\" From the ratio of the percentages in the usage endpoint, they infer that pool is about eight times larger, roughly $3,200. They say their list-rate Grok and Composer spend of about $2,005 matches the dashboard's 63%. They also say Fast variants cost twice as much and that one Grok model charges more past 256k context.\n\nThose pool sizes are this subscriber's own estimates from one account, not published limits. The poster adds that \"people now say\" renewals get only $100 on the Other Models pool; they could not confirm that, and said they would not pay $200 again if it were true. They asked other subscribers to run the same calculation on their own accounts to see whether the 8:1 ratio holds.","status":"published","storyType":"news","category":"Pricing","clusterKey":"cursor-pro-500-ultrafast-burn","slug":"a-builder-says-a-pro-500-plan-with-ultrafast-used-20-of-a-weekly-limit-i-bbffe9","url":"https://cursorhq.ai/news/a-builder-says-a-pro-500-plan-with-ultrafast-used-20-of-a-weekly-limit-i-bbffe9/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/bbffe929-fc39-4179-aa65-de98ba4d7b42","role":"item","position":1,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/a-builder-says-a-pro-500-plan-with-ultrafast-used-20-of-a-weekly-limit-i-bbffe9/ddb58c5d83cbf6b5-9fbffa5369ae369b/web_hero.webp","imageAlt":"A close-up of a vintage-style industrial fuel gauge with a needle indicating the 20 percent mark on a dial.","createdAt":"2026-10-01T15:41:31.014Z","updatedAt":"2026-10-01T16:00:49.686Z","sources":[{"role":"primary","title":"Cursor Pro 500 With Ultrafast Burns Through Weekly Limit in 90 Minutes","url":"https://x.com/tdinh_me/status/2105160556210786797","sourceName":"Tony Dinh","author":"Tony Dinh","publishedAt":"2026-09-30T04:59:23Z"},{"url":"https://x.com/theo/status/2105010828433051904","title":null,"sourceName":"x.com","author":"Theo - t3.gg","publishedAt":"2026-09-29T19:04:25.000Z","role":"supporting"},{"url":"https://reddit.com/r/cursor/comments/1wu299z/ultra_usage_for_one_cycle_subbed_sept_2","title":null,"sourceName":"reddit.com","author":"/u/Additional_Welcome23","publishedAt":"2026-09-30T11:18:50.000Z","role":"supporting"}]},{"id":"d57dacba-b954-448e-b30e-dfec83fc2dae","title":"Six habits for running Cursor Projects, from a Hub that audits the rest to a dedicated debug project","dek":"A developer who has used Cursor Projects since its internal debut says one coordinating \"Hub\" project should review the others, and that you should start with a few projects rather than overdoing it.","bodyMd":"A developer who has used Cursor Projects since it debuted internally shared six tips for running them. Projects, in Cursor, use a coordinator agent that dispatches other agents. By default they run in Cloud Agents.\n\n1. **Create one `Hub` project.** The developer likens it to an office manager. Use it for best practices, and ask it to investigate how each project is working, what's missing and what could be done better.\n2. **Start with a few projects.** With time you learn how many is enough. The developer's example: while debugging some Cloud Agent nodes, they knew they would need several agents, including review agents, so they created a single Project just for that debug session.\n3. **Pick the coordinator model deliberately.** The developer calls Grok 4.7 \"pretty good\" for the coordination part and uses it for chores too. For heavy work, the coordinator dispatches agents running Opus or Fable (Anthropic's Claude Opus 5 and Claude Fable 5.1). The point, they say, is that Cursor doesn't bind you to one model.\n4. **Give coordinators more autonomy.** Tell the coordinator you \"don't want to be bothered,\" and have it ask upfront whether the work needs any MCP logins or website authentications. The goal is to remove self-inflicted blocking, then let it run.\n5. **Set icons and colors on purpose.** The developer says they help when switching context between projects.\n6. **Enable remote workers.** If something can only be done on your localhost, the coordinator can dispatch an agent that runs on your machine instead of in the cloud.\n\nThese are one user's practices, not documented Cursor guidance. The developer also points to a longer write-up and a blog post for more detail.","status":"published","storyType":"tip","category":"Workflow","clusterKey":"cursor-projects-tips","slug":"six-habits-for-running-cursor-projects-from-a-hub-that-audits-the-rest-t-d57dac","url":"https://cursorhq.ai/guides/six-habits-for-running-cursor-projects-from-a-hub-that-audits-the-rest-t-d57dac/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/d57dacba-b954-448e-b30e-dfec83fc2dae","role":"item","position":2,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/six-habits-for-running-cursor-projects-from-a-hub-that-audits-the-rest-t-d57dac/94c93760a5a78de3-f4a4d117a96874a8/web_hero.webp","imageAlt":"A large central metal hub unit connected to five smaller, identical worker units by short cables in a tiered, hierarchical arrangement.","createdAt":"2026-10-01T15:42:19.381Z","updatedAt":"2026-10-01T16:00:40.587Z","sources":[{"role":"primary","title":"Six Cursor Projects Tips for Better AI Agent Coordination","url":"https://x.com/fatih/status/2103471040126967890","sourceName":"Fatih Arslan","author":"Fatih Arslan","publishedAt":"2026-09-25T13:05:51Z"}]},{"id":"9ec8a79d-b330-4d69-83a0-8582b80e009a","title":"Cursor's Plan Mode lets you edit the AI's checklist before it touches your code","dek":"Plan Mode has Cursor draft a checklist first, and pressing Build then starts Agent mode, the setting where the AI writes and edits your files directly.","bodyMd":"A 25-tip Cursor walkthrough argues that the most common way to get stuck is opening Agent mode and describing a feature cold, with no plan or context. The agent produces something plausible but slightly off, you correct it, it drifts again, and you end up in a long fix-and-retry loop. Plan Mode is the walkthrough's fix.\n\n**How to do it**\n\n1. Switch the chat to Plan Mode and describe what you want. The example is a task-labels feature (tags such as urgent, blocked and in review) that needs frontend changes, backend changes and a database migration.\n2. Cursor writes no code at this stage. It returns an architecture overview, database schema changes and a checklist of every step it intends to take.\n3. Edit the plan. Add a to-do, remove anything out of scope, adjust the approach.\n4. Click Build. Cursor switches to Agent mode and works down the checklist: migration, model, API endpoints, frontend, ticking items off as it goes.\n5. Test before you accept. The agent writes into your real files as it works, so run the app and check the behavior first, then accept the changes. Undo All exists, but that window closes while the build continues.\n\nIf you have a requirements document or a pull request, the walkthrough says to attach it as a file at the start of Plan Mode.\n\n**When to use it.** For anything non-trivial. Vague instructions in Agent mode produce vague output, and a clear plan up front saves several correction rounds.\n\n**Related habits from the same walkthrough**\n\n- Command K (select code, describe the change, review the diff) is for targeted edits inside a single file. Once a change touches more than one file, move to Chat, which opens with Command L.\n- In Chat, use @ to point Cursor at the relevant files, terminal output or a screenshot rather than dumping in the whole codebase. The walkthrough's rule: relevance beats volume.\n- Open a new chat for each new task. Leftover context from an earlier task pushes the agent to make assumptions based on the wrong problem.","status":"published","storyType":"tip","category":"Workflow","clusterKey":"cursor-plan-mode-25-tips","slug":"cursor-s-plan-mode-lets-you-edit-the-ai-s-checklist-before-it-touches-yo-9ec8a7","url":"https://cursorhq.ai/guides/cursor-s-plan-mode-lets-you-edit-the-ai-s-checklist-before-it-touches-yo-9ec8a7/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/9ec8a79d-b330-4d69-83a0-8582b80e009a","role":"item","position":3,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/cursor-s-plan-mode-lets-you-edit-the-ai-s-checklist-before-it-touches-yo-9ec8a7/c60f0d976dea060c-7554e111342656e8/web_hero.webp","imageAlt":"A physical metal device with a vertical stack of adjustable tiles, representing a task checklist, and a heavy lever ready to engage the mechanism.","createdAt":"2026-09-30T12:14:24.225Z","updatedAt":"2026-09-30T12:30:22.584Z","sources":[{"role":"primary","title":"Cursor Plan Mode Deep Dive With 25 Practical Tips for Faster Coding","url":"https://www.youtube.com/watch?v=CZUtIIK4fdw","sourceName":"@ByteMonk","author":"@ByteMonk","publishedAt":"2026-09-30T04:55:57Z"}]},{"id":"23770ce0-69d2-4491-b1e6-a5d1646bab30","title":"Supermemory rebuilds its Cursor plugin and lists it on the Cursor Marketplace","dek":"Supermemory is an add-on that lets an AI assistant remember things from earlier sessions, so you don't have to repeat yourself each time.","bodyMd":"Supermemory has rebuilt its Cursor plugin, and the plugin is now on the Cursor Marketplace. The company announced it on X on September 28, in a roundup of integrations it shipped over recent months. The post does not say when the Cursor rebuild itself happened. Supermemory is an add-on that gives an AI assistant a way to remember what happened in earlier chats and sessions.\n\nThe Cursor listing was one of six in a post that Supermemory says covers what it shipped \"over the last few months.\" The post says Supermemory \"now lives in 6 more places your agents run.\" It gives no detail on what the rebuilt Cursor plugin changes. It says only \"rebuilt plugin, now on the Cursor Marketplace.\"\n\nThe other five integrations in the post:\n\n- **Muse Code**, from Meta's AI group, \"picks up what Claude Code already learned about your repo.\"\n- **Grok Bot** can be told to \"add supermemory.\"\n- **Vercel's eve** lists Supermemory as the first official memory item in its registry.\n- **Hermes**, from Nous Research, now has Supermemory as a standalone plugin in the Hermes plugin market.\n- **Stripe Projects** lets agents set up their own memory by running `stripe projects add supermemory/memory`.\n\nFor teams already working in Cursor, the plugin is now listed on the Cursor Marketplace. The announcement gives no detail on what changed in the rebuilt plugin compared with the earlier version.","status":"published","storyType":"news","category":"Ecosystem","clusterKey":"supermemory-cursor-marketplace-plugin","slug":"supermemory-rebuilds-its-cursor-plugin-and-lists-it-on-the-cursor-market-23770c","url":"https://cursorhq.ai/news/supermemory-rebuilds-its-cursor-plugin-and-lists-it-on-the-cursor-market-23770c/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/23770ce0-69d2-4491-b1e6-a5d1646bab30","role":"item","position":4,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/supermemory-rebuilds-its-cursor-plugin-and-lists-it-on-the-cursor-market-23770c/e55228323a114223-8a3fe6b68104c208/web_hero.webp","imageAlt":"A modular data cartridge is inserted into the center of a hardware hub that has five other empty ports surrounding it.","createdAt":"2026-10-01T16:54:09.580Z","updatedAt":"2026-10-01T17:00:18.068Z","sources":[{"role":"primary","title":"Supermemory Expands to Cursor, Vercel Eve, Stripe, and Four More Agent Platforms","url":"https://x.com/supermemory/status/2104601236582654384","sourceName":"supermemory","author":"supermemory","publishedAt":"2026-09-28T15:56:51Z"}]},{"id":"4475c228-3139-4bb7-b295-867a3bd02f04","title":"Cursor can work like VS Code for browser-test projects, with an AI you tell not to edit","dek":"Playwright, a tool that clicks through your web app in a browser to check it works, runs in Cursor with the same commands as VS Code, and you can tell Cursor's AI to review your test code without changing any files.","bodyMd":"Cursor looks and behaves like VS Code, so an existing Playwright project needs no special setup. A recent walkthrough shows the editor used both ways: as a plain code editor, and as an AI helper that is told to read and comment only.\n\n**Use it as a regular editor**\n\nCursor has a built-in terminal like VS Code's. The walkthrough says there are no Cursor-specific commands for Playwright: whatever npm and Playwright commands you use in VS Code work the same. To run tests, use:\n\n```\nnpx playwright test\n```\n\n**Ask the agent to review without editing**\n\nThe agent is Cursor's AI assistant, the part that can edit files and run commands. Open a new agent and put the limit in the prompt. The prompt used in the demo:\n\n> Review this login file and suggest improvements to make it more readable and maintainable. Do not modify the test file and explain your suggestion first.\n\nThe agent scanned three files, ran one search, and returned suggestions with no file changes. It proposed pulling the login page into a page object (one class that holds a page's selectors and steps), adding methods to read the logged-in username and check expectations, and replacing hardcoded URLs with Playwright's base URL setting. The presenter declined to apply them and said he would make the changes by hand.\n\n**When it helps**\n\nThe presenter recommends this when you are unsure your code is right and want a second opinion before anything changes.\n\n**Building a project from scratch**\n\nThe same walkthrough opens an empty folder and prompts the agent to build a beginner-friendly Playwright framework in TypeScript for the Sauce Demo site, using page objects. The prompt says not to add Cucumber, API testing, database integration, CI/CD reporting, or unnecessary files, and to run the login test if credentials are available. The agent installed the npm dependencies and browsers, created the pages and a spec file, and ran `npm test`: one login test passed in Chromium. The presenter says this would have taken two to three hours by hand and took a few minutes.\n\n**Caveats the presenter raises**\n\n- AI-generated code is not always correct, so you need enough Playwright knowledge to review it and spot errors.\n- Agent usage can hit limits depending on the tool and plan, and more complex tasks use more of it.\n- Learn Playwright concepts first (selectors, assertions, fixtures, page objects, configuration), and be able to work without the AI.","status":"published","storyType":"tip","category":"Workflow","clusterKey":"playwright-in-cursor-editor","slug":"cursor-can-work-like-vs-code-for-browser-test-projects-with-an-ai-you-te-4475c2","url":"https://cursorhq.ai/guides/cursor-can-work-like-vs-code-for-browser-test-projects-with-an-ai-you-te-4475c2/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/4475c228-3139-4bb7-b295-867a3bd02f04","role":"item","position":5,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/cursor-can-work-like-vs-code-for-browser-test-projects-with-an-ai-you-te-4475c2/fa12dcd7f568d29e-f4ad6ca88285e829/web_hero.webp","imageAlt":"A metallic device with a locked central file slot and three mechanical output cartridges resting beside it.","createdAt":"2026-09-29T18:56:31.378Z","updatedAt":"2026-09-29T19:01:05.366Z","sources":[{"role":"primary","title":"Use Cursor IDE as a Regular Editor Plus AI for Playwright Testing","url":"https://www.youtube.com/watch?v=RvFQIkrVVBk","sourceName":"@scriptandexecute","author":"@scriptandexecute","publishedAt":"2026-09-27T14:55:54Z"}]}],"tips":[{"id":"7ab55b05-0f3c-466a-b353-6fcb7c6da174","title":"Find the good edit one agent silently overwrote for another, using git log","dek":"When parallel agents work in one repo, a file committed by two different sessions within an hour is the sign that one fix may have erased another.","bodyMd":"Running several background agents (AI assistants that edit code) or chats on one repository, or Cursor beside Claude Code or Codex, carries a failure that rarely shows up as a bad edit. It shows up as a good edit that vanishes. Agent A fixes a file. Agent B, working from what it read twenty minutes earlier, rewrites the same file and commits. A's fix is gone, nothing errors, and tests may still pass.\n\nGit keeps the evidence, according to the memento team, which builds a free, MIT-licensed tracker and disclosed that interest. The overwrite leaves the same trace each time: one file, two different sessions (a different author or a different branch), commits less than an hour apart. The tool for finding it is `git log`, the command that lists a repository's commit history.\n\n**How to look**\n\n1. Pull a month of history with the session identity attached to each commit:\n `git log --all --source --since='1 month ago' --name-only --format='@%at|%an|%S'`\n Each commit prints a timestamp, author and branch, followed by its files.\n2. Pipe that into an awk filter (awk is a command-line text-processing tool) that flags any file committed by two different author/branch pairs less than an hour apart, then sort by frequency. The memento team's git log plus awk one-liner does this and prints the most frequent files first. The same check also runs in the browser in its overwrite-risk grader, and the team says the log is not uploaded.\n3. Look at the top of the list. If it is config, routes or schema files, that is where your agents collide.\n\n**Two fixes**\n\n- Give each agent its own worktree (a separate working folder checked out from the same repository), so the clash becomes a visible merge conflict instead of a silent overwrite.\n- Have an agent claim a file before it writes: append one line to a shared file under `flock`, and tell the other agents to skip claimed files.\n\n**Caveats.** The check cannot separate sessions that share one branch and one author name. A hit is also a near miss, not proof of a lost edit, so read the two diffs before concluding anything.","category":"Workflow","slug":"find-the-good-edit-one-agent-silently-overwrote-for-another-using-git-lo-7ab55b","url":"https://cursorhq.ai/guides/find-the-good-edit-one-agent-silently-overwrote-for-another-using-git-lo-7ab55b/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/7ab55b05-0f3c-466a-b353-6fcb7c6da174","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/find-the-good-edit-one-agent-silently-overwrote-for-another-using-git-lo-7ab55b/9b0bb9ac47984186-b6371947454b2e54/web_hero.webp","imageAlt":"Two rectangular metal cartridges are forced into a single vertical slot, with the second one partially overlapping the first.","createdAt":"2026-10-29T15:55:37.440Z"},{"id":"22bfcd77-ec8c-43ee-a7a7-d7f074c74961","title":"Have a different model review your agent's PR from inside Cursor","dek":"ThinkReview's MCP server lets Cursor call a single tool on a pull request URL and get back severity-ranked findings, so the agent can fix them in the same session.","bodyMd":"A quick glossary first: a PR (pull request) is a proposed code change awaiting review, and the agent is Cursor's AI assistant that writes and edits code.\n\nThinkReview, a pull request review tool for GitHub, GitLab, Azure DevOps and Bitbucket (including self-hosted), has an MCP server that works in Cursor, Claude Code, Codex, Antigravity and Windsurf. Your agent calls one tool, `review_url_code`, with a PR or MR URL. ThinkReview fetches the diff using git credentials stored in its portal, so nothing is pasted into chat.\n\nThe result is the structured review the ThinkReview extension already returns: a summary, severity-ranked findings, security notes and a plain-language reason. Your custom rules and chosen model apply, so the review can come from a different model family than the one that wrote the code. The reasoning is that the agent is the weakest last reader of its own change, and a recap in chat can drift from what the diff actually does.\n\n## Set it up in Cursor\n\n1. Before the first review, add a git PAT under Settings → Integrations in the ThinkReview portal. Without it, private diffs can't be read.\n2. Add the server to your MCP config. The hosted endpoint is `https://mcp.thinkreview.dev/v1`, which uses browser OAuth, so no token goes in config files.\n3. Click Authenticate.\n4. Ask the agent: \"Call thinkreview for https://github.com/org/repo/pull/123\".\n5. Then run `/mcp` and authenticate.\n\nCopy-paste configs for each client are on ThinkReview's MCP setup page.\n\n## Turn it into a loop\n\nWrapping the call in a skill is the better use. A Cursor skill such as `/thinkreview-pr` can find or open the PR, call `review_url_code`, fix the critical and high findings that deserve a change, run the tests, push to the same PR and review again. The same pattern works in Claude Code and Codex through a prompt, a custom command or an agent instruction file.\n\n## When it earns its keep\n\nTwo runs on real pull requests show the kind of problem it surfaces. On one PR, the review flagged that a Google sign-in popup handler was never set up, so the window could fail to open; the Cursor agent then patched `searchConsole.js` and restored a clear message when Google rejects the account. On a billing change, the review flagged a critical issue: when a cancel call failed, the handler still returned HTTP 200, so the billing provider would not retry and a trial could stay live. Both were easy to miss in the chat summary.\n\nReach for it on agent-written branches before merge, when the summary says \"done\" and you want a reader from outside the authoring session.","category":"Workflow","slug":"have-a-different-model-review-your-agent-s-pr-from-inside-cursor-22bfcd","url":"https://cursorhq.ai/guides/have-a-different-model-review-your-agent-s-pr-from-inside-cursor-22bfcd/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/22bfcd77-ec8c-43ee-a7a7-d7f074c74961","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/have-a-different-model-review-your-agent-s-pr-from-inside-cursor-22bfcd/e9a2f1c5685ca535-d1e1b4689b6c5f4a/web_hero.webp","imageAlt":"A metal cartridge with two glass chambers slides into a hardware dock to bridge a code agent with an external review tool.","createdAt":"2026-10-29T15:08:20.314Z"},{"id":"633ea1f3-ccdd-4279-99b0-490dd30577ff","title":"Vicem swaps unchanged function bodies for one-line stubs to slim Agent Mode's context","dek":"Vicem, a free MIT-licensed MCP server, swaps unchanged function bodies for stubs to trim the context its developer says Cursor re-sends each turn, and hands full bodies back to the agent only when needed.","bodyMd":"Agent Mode is Cursor's AI agent: it reads files, runs commands and edits code across a chat. The developer behind Vicem says it is quick in a fresh chat, but that after 20 to 30 turns of file reads and test runs the \"Planning next moves\" pause grows noticeably. They attribute it to each turn re-sending a large payload built from chat history. That is the developer's own observation, not a documented description of how Cursor works. Starting a new chat restores the speed but costs the context: which files changed, what broke, what constraints apply.\n\nVicem, an open-source tool under the MIT license, attacks the payload size. It is also an MCP server, meaning a small local program that gives the agent extra tools it can call (MCP stands for Model Context Protocol). Its developer says it runs on Node.js built-ins only, with zero npm dependencies and no network calls, and cuts tokens per turn by \"usually 55% to 78%\". Tokens are the chunks of text a model reads and is billed for.\n\n**What it trims**\n\nA function body is the code between a function's braces, the part that does the work; the signature is the line that names the function and its inputs. A stub is a short placeholder left in the body's place.\n\n- **Code skeletonizer:** keeps imports, exported types and function signatures, and replaces unchanged function bodies with a one-line stub carrying an ID, such as `{ /* vicem:fn_a8c39f (42L) */ }`.\n- **Log slimmer:** strips passing test lines and `node_modules` stack frames from terminal output, so the agent sees the failing assertions.\n- **Data diet:** condenses large JSON, CSV and SQL files into compact schemas and ignores lockfiles.\n- **Secret guard:** masks `.env` values and keys such as `sk-*`, `ghp_*` and `AKIA*` locally before they reach the prompt.\n\n**Getting bodies back**\n\nStripped blocks are stored in `.vicem/ledger.json`. Vicem registers a lightweight stdio MCP server (one that talks to Cursor over standard input and output rather than a network port) in `~/.cursor/mcp.json`, with an optional `.cursor/rules/vicem.mdc` rule. When the agent needs to read or edit a skeletonized function, it calls `vicem_rehydrate_node` and pulls back only those lines.\n\n**Carrying state into a new chat**\n\nVicem can also snapshot the workspace: it copies `state.vscdb` plus the `-wal` and `-shm` files to a temp file (so it never locks a running Cursor window), adds your git diff and recent terminal output, and writes a `BATON.md` handoff file you can use to start a fresh chat without re-explaining.\n\n**Trying it**\n\nThe code is at github.com/RAKKUNN/vicem. `npx vicem-cli gui` launches a local three-column web GUI, and a browser sandbox runs at rakkunn.github.io/vicem.\n\nThe developer built it for long sessions on larger codebases. The token savings and the explanation of the slowdown are the developer's own; the source gives no speed measurement.","category":"Workflow","slug":"vicem-swaps-unchanged-function-bodies-for-one-line-stubs-to-slim-agent-m-633ea1","url":"https://cursorhq.ai/guides/vicem-swaps-unchanged-function-bodies-for-one-line-stubs-to-slim-agent-m-633ea1/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/633ea1f3-ccdd-4279-99b0-490dd30577ff","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/vicem-swaps-unchanged-function-bodies-for-one-line-stubs-to-slim-agent-m-633ea1/13d5362447afa6e3-56073ef165789f7d/web_hero.webp","imageAlt":"A row of document stacks, with one full stack and several others compressed into thin placeholders by metal spacer plates.","createdAt":"2026-10-29T00:20:09.117Z"},{"id":"e9e0ebc4-2dbe-4f7f-b238-896f0f17f3a1","title":"Track Cursor CLI tasks and approvals across repos from one dashboard","dek":"Denly, a web dashboard for coding agents, runs Cursor's CLI (the command-line interface, a text-based way to run the agent from a terminal) on your own machine and collects whatever needs a human decision in one place.","bodyMd":"Denly gathers the work that is waiting on you across several projects: plans to approve, questions from agents, failures and PRs ready for review. Its Cursor integration drives Cursor's CLI on your own machine, according to its developer's forum post. The CLI is the command-line interface, the text-based way to run the Cursor agent from a terminal. The tool also supports other coding-agent CLIs, so different projects can use different providers.\n\n**How the workflow runs**\n\n1. Submit a task for a project.\n2. Review the agent's proposed plan and approve it.\n3. Let the agent build and run the checks configured for that repository.\n4. Review the resulting PR, then request changes or merge.\n\n**Who it is aimed at**\n\nThe developer pitches Denly at people using Cursor across several repositories and asks for feedback on whether the workflow helps. The part the developer says they are focusing on now is coordinating work across projects and keeping track of where a person needs to step in.\n\n**Limits to know**\n\n- The runner makes outbound requests to the control service, so no port needs to be opened on your machine.\n- Your machine must be awake and online for tasks to execute.\n- Selected plans, transcripts and other content can be uploaded, so local execution does not mean everything stays local.\n- Denly has a free plan and paid tiers. You use your own agent account, with its existing limits and charges.\n\nThe developer's post links a product page at denly.dev and an illustrated demo walkthrough with sample tasks.","category":"Ecosystem","slug":"track-cursor-cli-tasks-and-approvals-across-repos-from-one-dashboard-e9e0eb","url":"https://cursorhq.ai/guides/track-cursor-cli-tasks-and-approvals-across-repos-from-one-dashboard-e9e0eb/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/e9e0ebc4-2dbe-4f7f-b238-896f0f17f3a1","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/track-cursor-cli-tasks-and-approvals-across-repos-from-one-dashboard-e9e0eb/aecba402adeae18f-570bf920197284f3/web_hero.webp","imageAlt":"A metallic central hub with four cables connecting to four separate workstation towers, representing the coordination of multiple coding tasks in one location.","createdAt":"2026-10-28T19:11:12.546Z"},{"id":"0f97b24d-6df1-42d8-abb5-e096c1f17ea9","title":"Write a pull request prompt as a Cursor custom command in a markdown file","dek":"A markdown file in a commands folder inside the cursor folder holds a prompt that asks for a PR with a descriptive title and the GitHub CLI.","bodyMd":"Cursor custom commands are markdown files in a `commands` folder inside the cursor folder, each holding a prompt. The walkthrough's example is a command for making pull requests.\n\nA few terms in plain language:\n\n- **Markdown file:** a plain-text file, ending in `.md`, that uses simple formatting symbols.\n- **Pull request (PR):** a proposal to merge your code changes into a project so others can review them.\n- **Prompt:** the written instructions you give Cursor's AI.\n- **Command:** here, a named markdown file that holds a prompt you have written down.\n- **GitHub CLI:** GitHub's command-line tool, which can create pull requests from the terminal.\n\n**How to set it up**\n\n1. In the cursor folder, create a new folder named `commands`.\n2. Inside it, add a markdown file. The example uses `pr.md`, but the file can be named whatever you want.\n3. Put the prompt in the file. The example reads: \"Your job is to create a PR with a descriptive title. Always use the GitHub CLI.\"\n\nThe prompt text is free-form, so you decide what goes in it. The walkthrough notes you could also add specific rules or commit guidelines to the same file.\n\n**What the example shows**\n\nThe example keeps a pull request prompt in a `pr.md` file inside the `commands` folder. That prompt asks for a PR with a descriptive title and says to always use the GitHub CLI.\n\nThe source covers only the file setup and the example prompt. It does not show how the command is then invoked.","category":"Workflow","slug":"write-a-pull-request-prompt-as-a-cursor-custom-command-in-a-markdown-fil-0f97b2","url":"https://cursorhq.ai/guides/write-a-pull-request-prompt-as-a-cursor-custom-command-in-a-markdown-fil-0f97b2/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/0f97b24d-6df1-42d8-abb5-e096c1f17ea9","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/write-a-pull-request-prompt-as-a-cursor-custom-command-in-a-markdown-fil-0f97b2/ce519ee6e9295810-7821bc6d791aef8f/web_hero.webp","imageAlt":"A metal cartridge with etched markings is shown being inserted into a slot on the side of a larger, modular hardware device.","createdAt":"2026-10-28T08:39:32.458Z"}]}