{"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":"a21617e4-435c-4ced-b6e7-affce89babd4","date":"2026-09-30","status":"locked","createdAt":"2026-09-29T17:16:42.704Z","storyCount":3,"newsletterSubject":"Cursor adds Rollouts and Security bots, Google open sources phone testing tool, GLM 5.3 spotted in Cursor menu"},"updatedAt":"2026-09-29T18:00:30.038Z","stories":[{"id":"176a3d59-d787-4868-b055-a2b6273adc26","title":"Cursor's Rollouts bot watches code once it goes live, and Security Review scans every PR for exploits","dek":"Rollouts writes a monitoring plan for every pull request and checks it against real logs and metrics after the code ships, while Security Review flags exploits—ways an attacker could take advantage of a flaw in the code to break in, steal data, or cause harm—before merge, the point when the proposed code changes are combined into the main version of the project, and Cursor gave Teams and Enterprise trial credits to test Rollouts on real changes.","bodyMd":"Cursor put two automated bots to work on the last stretch of shipping code: Rollouts, which watches a change after it deploys and flags when something that used to work breaks, and Security Review, which reads every pull request for exploitable bugs before it merges. Both went live for Teams and Enterprise plans on September 23.\n\nRollouts attaches itself to a pull request before the code ever ships. It reads the diff and the systems the change touches, then posts a monitoring plan as a comment on the PR: the risks it spotted, what the change is supposed to do, the signals it will watch, and any gaps in logging that would make the change hard to verify. Engineers can edit that plan before it runs. Once the change deploys, Rollouts wakes up and checks it against logs, metrics, and traces, tracking staging and production separately so a fix that looks fine in one environment can still get flagged in the other. It reports back one of three verdicts: verified healthy, regression detected, or inconclusive.\n\nWhen Rollouts calls a regression, it names the change it suspects and notifies whoever wrote it. Depending on how a team configures it, Rollouts can open a revert pull request for a human to approve, or route the problem to a cloud agent to fix. It does not merge or roll back code on its own. The bot is Cursor's rebuild of Firetiger's Change Monitors, a deployment-monitoring tool, built on Cursor's own Bot Development Kit. It connects to GitHub or Cursor's Origin repos for source control, a team's existing deploy pipeline for release events, and Datadog and other providers for telemetry; support for feature flags hasn't shipped yet.\n\nSecurity Review works differently: it reads a pull request in the context of the whole codebase and posts a single comment listing exploitable bugs, skipping draft PRs entirely. It checks for SQL, command, and template injection, authentication and authorization bypasses (including cases where a refactor accidentally stopped an old check from running), leaked secrets and credentials, server-side request forgery, unsafe deserialization, and dependency updates that pull in known vulnerabilities. Each finding comes with a severity rating, the attack path, and a proposed fix, and dismissing one with a reason keeps it from resurfacing on that same PR. Teams can also add their own rules, such as which client all external calls must route through, and Security Review enforces them going forward. Code style and general quality checks stay with Bugbot, Cursor's separate review bot.\n\nFor the ten days after launch, Cursor handed out trial credits so teams could test Rollouts on real deployments: roughly 50 changes for Teams accounts and 500 for Enterprise. Both bots are opt-in per repository, enabled from the automations tab.","status":"published","storyType":"news","category":"Agents","clusterKey":"cursor-rollouts-and-security-reviewer-bots","slug":"cursor-s-rollouts-bot-watches-code-once-it-goes-live-and-security-review-176a3d","url":"https://cursorhq.ai/news/cursor-s-rollouts-bot-watches-code-once-it-goes-live-and-security-review-176a3d/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/176a3d59-d787-4868-b055-a2b6273adc26","role":"lead","position":0,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/cursor-s-rollouts-bot-watches-code-once-it-goes-live-and-security-review-176a3d/81b1a2b928053c7a-42fc7c8185189df6/web_hero.webp","imageAlt":"Two mechanical monitor devices connected to a central cable, representing automated security scanning and post-deployment monitoring for software pull requests.","createdAt":"2026-09-27T23:22:43.434Z","updatedAt":"2026-09-27T23:30:16.511Z","sources":[{"role":"primary","title":"Cursor Launches Rollouts and Security Review Bots for Teams and Enterprise","url":"https://cursor.com/changelog","sourceName":"\"when:7d Cursor Anysphere AI editor\" - Google News","author":"\"when:7d Cursor Anysphere AI editor\" - Google News","publishedAt":"2026-09-23T12:00:00Z"},{"role":"supporting","title":"Cursor Rollouts Watches Your Deploys Live, Plus New AI Dev Tools Drop","url":"https://tiktok.com/@saaketvarma/video/7689776481626606861","sourceName":"saaketvarma","author":"saaketvarma","publishedAt":"2026-09-26T09:40:27Z"},{"role":"supporting","title":"Cursor Rollouts Watches Your Deploys, Plus Antigravity, Kiro and Hermes Full written briefing, every source linked: myownai-daily-signal.ver...","url":"https://tiktok.com/@saaketvarma/video/7689776481626606861","sourceName":"saaketvarma","author":"saaketvarma","publishedAt":"2026-09-26T09:40:27Z"},{"role":"supporting","title":"Cursor Adds Rollouts to Monitor Deployments and Speeds Up Security Reviewer","url":"https://x.com/cursor_ai/status/2102861817160904808","sourceName":"cursor_ai","author":"cursor_ai","publishedAt":"2026-09-23T23:42:01Z"},{"role":"supporting","title":"Cursor Adds Rollouts to Monitor Deployments and Speeds Up Security Reviewer","url":"https://x.com/cursor_ai/status/2102861817160904808","sourceName":"Cursor","author":"Cursor","publishedAt":"2026-09-23T20:45:01Z"},{"role":"supporting","title":"What's New in Cursor — Latest Updates & Release Notes - Cursor","url":"https://cursor.com/changelog","sourceName":"\"when:7d Cursor Anysphere AI editor\" - Google News","author":"\"when:7d Cursor Anysphere AI editor\" - Google News","publishedAt":"2026-09-23T00:00:00Z"}]},{"id":"9a7fbf9d-b8e6-47e7-9013-da0883dffd11","title":"Google open-sourced ARTEMIS, a tool that lets coding agents tap and swipe on real phones","dek":"The tool connects over MCP, the protocol that lets assistants like Cursor call outside programs, so an agent can install an app on a real Android or iPhone, log in, and screenshot whatever breaks.","bodyMd":"Google open-sourced ARTEMIS on September 20, an MCP tool that lets a coding agent operate a real Android or iOS device the way a person would: it reads the screen, locates the buttons and fields, taps, swipes, navigates between screens, and checks whether the result matches what was asked. MCP, or Model Context Protocol, is the connector standard that lets an AI coding assistant call out to an outside program, and Google built ARTEMIS to speak it, so it plugs into Cursor, Claude Code, Codex, Windsurf, Antigravity, and VS Code without custom wiring. The code is released under the Apache 2.0 license, meaning anyone can use, modify, or fold it into their own product for free.\n\nFor teams shipping UI changes through Cursor, that closes a gap that usually falls to a human: does the feature actually work when someone's thumb is on the glass? A developer's post describing the tool frames it as \"the missing piece after you ship a UI change,\" aimed at indie developers and testers. It works on both iOS and Android, and can run either locally or in the cloud, according to that post.\n\nThe pitch is that it replaces the usual native test-writing work. Instead of hand-coding scripts in XCUITest, Apple's UI testing framework, or Espresso, Google's equivalent for Android, a developer just tells the agent what to check in plain English. Google's own example: tell Codex to build the app, install it, log in with a test account, walk through checkout, flag any unexpected popups, and hand back screenshots of whatever failed. ARTEMIS drives the phone itself and reports what it finds, rather than the developer writing and maintaining a separate test suite.\n\nUnder the hood, Google says ARTEMIS locates on-screen elements by combining accessibility data, optical character recognition, and computer vision, rather than relying on any single method that can break when an app's layout shifts. Every run produces screenshots, execution traces, and diagnostics, which gives a developer something to inspect when a step fails instead of just a pass or fail flag. Google reports the tool completed more than 99% of tasks on AndroidWorld, a benchmark suite of Android device-control tasks, across over 100 multi-step scenarios, at roughly three to five seconds per step in its faster \"Flash\" mode. A Python SDK lets teams call ARTEMIS from their own test pipelines rather than only through a chat-based agent.\n\nThose completion numbers come from Google's own reporting rather than an independent test, and neither post that surfaced the release cites outside benchmarking. What's verifiable is the license and the integration path: it's free to inspect and modify, and any MCP-compatible agent, Cursor included, can call it today.","status":"published","storyType":"news","category":"Ecosystem","clusterKey":"google-artemis-phone-control-for-agent-testing","slug":"google-open-sourced-artemis-a-tool-that-lets-coding-agents-tap-and-swipe-9a7fbf","url":"https://cursorhq.ai/news/google-open-sourced-artemis-a-tool-that-lets-coding-agents-tap-and-swipe-9a7fbf/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/9a7fbf9d-b8e6-47e7-9013-da0883dffd11","role":"item","position":1,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/google-open-sourced-artemis-a-tool-that-lets-coding-agents-tap-and-swipe-9a7fbf/e0c993d7015895a4-c77a401db54b81a4/web_hero.webp","imageAlt":"A mechanical robotic finger assembly positioned over a smartphone to simulate human touch on the screen.","createdAt":"2026-09-27T20:12:13.512Z","updatedAt":"2026-09-27T20:30:16.075Z","sources":[{"role":"primary","title":"Google Open-Sources ARTEMIS for AI Agents to Control Real Phones","url":"https://x.com/dr_cintas/status/2101768566164840752","sourceName":"Alvaro Cintas","author":"Alvaro Cintas","publishedAt":"2026-09-20T20:20:49Z"},{"role":"supporting","title":"New Tool Lets Claude and Cursor Control Real Phones for Automated Bug Testing","url":"https://x.com/0x0SojalSec/status/2103616740810989700","sourceName":"Md Ismail Šojal 🕷️","author":"Md Ismail Šojal 🕷️","publishedAt":"2026-09-25T22:44:48Z"}]},{"id":"67785431-1481-4708-ac0a-47a27c92db74","title":"A Cursor user reports GLM 5.3, an AI model, in Cursor's model menu","dek":"A post dated 2026-09-29 reports GLM 5.3, an AI model, in what the poster calls the Other Models picker, a menu for choosing which model Cursor uses; GLM 5.3 Flash appears only in the post's link.","bodyMd":"One Cursor user reports in a Reddit post dated 2026-09-29 that they noticed GLM 5.3 in what they call the \"Other Models picker\". GLM 5.3 is an AI model, and the picker is a menu in Cursor where you choose which AI model to use, though the post doesn't say how to reach it. The poster says they saw it while checking which models were available.\n\nThe post's link is named \"glm_53_and_53_flash_available\", so it mentions GLM 5.3 Flash as well. The post's own text, though, names only GLM 5.3, so the report does not show whether a Flash version is in the picker.\n\nThe user says they are \"all for\" Cursor adding open-weights models, meaning models whose trained weights are published. They add that this, along with what Cursor offers with Grok, makes Cursor \"a sweet deal for me\". That is one person's opinion. The post gives no pricing, plan or usage-limit details for GLM 5.3.\n\nThe same user says they are waiting to see whether and when Cursor brings in Grok 4.8, and are \"fingers-crossed for a new Composer soon\". The post does not confirm either.\n\nThis is a single user's report with a screenshot, not a Cursor announcement. The post does not say when GLM 5.3 appeared, which plans include it, or how it is billed.","status":"published","storyType":"news","category":"Models","clusterKey":"glm-5-3-in-cursor-model-picker","slug":"glm-5-3-appears-in-cursor-s-other-models-picker-677854","url":"https://cursorhq.ai/news/glm-5-3-appears-in-cursor-s-other-models-picker-677854/","relayUrl":"https://relaygrid.com/publications/pivot-cursor/stories/67785431-1481-4708-ac0a-47a27c92db74","role":"item","position":2,"imageStatus":"ready","imageUrl":"https://media.pivotnews.ai/brands/cursor-hq/articles/glm-5-3-appears-in-cursor-s-other-models-picker-677854/d09a538e0aa448a2-22b4ddc00b014c03/web_hero.webp","imageAlt":"A metal switch with two cylindrical cartridges labeled 5.3, one tall and one shorter, indicating the presence of two distinct model versions.","createdAt":"2026-09-29T15:39:37.727Z","updatedAt":"2026-09-29T18:00:30.038Z","sources":[{"role":"primary","title":"Cursor Adds GLM 5.3 and GLM 5.3 Flash to Its Model Picker","url":"https://reddit.com/r/cursor/comments/1wt7q23/glm_53_and_53_flash_available","sourceName":"/u/Robert-Paulson_","author":"/u/Robert-Paulson_","publishedAt":"2026-09-29T11:35:50Z"}]}],"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"}]}