# Cursor (IDE-first) > If you'd rather see the diff as you go than read a terminal log, Cursor is the answer. Cmd-K for inline edits, agent mode for multi-file changes, Bugbot reviews the PR. The editor stays the source of truth all the way through. Source: https://aistack.sh/stack/ship-code-cursor Category: Code · Workflow Level: Beginner Last verified by a human: 2026-05-05 ## The tools ### Cursor — Plan + write + review - Pricing: Free Hobby · $20/mo Pro · $60/mo Pro+ · $200/mo Ultra · $40/seat Teams · $120/seat Teams Premium - Site: https://cursor.com - Why this one: Cmd-K for surgical edits, Cmd-L for chat with file context, Composer (agent mode) for multi-file work, Bugbot for PR review on push. One tool for the whole loop. - Swap in instead: Claude Code, Codex - More: https://aistack.sh/tool/cursor ## Monthly cost ### $0/mo — Solo OSS, Hobby tier (small) - Cursor: Free Hobby (Bugbot included) ### $20/mo — Indie dev, daily PRs (medium) - Cursor: $20 Pro ### $200/mo — 5-dev team, Business plan (heavy) - Cursor: $200 (5× $40 Business) ## Workflow ### 1. Plan in Cursor's chat panel (Cursor) Cmd-L. Add the ticket and the most-relevant 2 to 3 files via @-mentions. Get the plan there; you stay in the editor. **Prompt: Scope a change inside Cursor (Cmd-L)** ``` Plan a small, well-scoped PR for the change below. Don't write the code yet. Ticket / problem: """ {{paste ticket}} """ I've @-mentioned the most relevant files. Use them as the source of truth for current behavior. Output: 1. Restated problem in 2 sentences. 2. Files to touch + 1-line "why" each. 3. Smallest viable diff in 5 to 8 bullets. 4. Edge cases (3 to 5). 5. What I should NOT change. Ask 1 to 2 clarifying questions if the ticket is genuinely ambiguous. ``` ### 2. Implement with Composer (Cursor) Switch to agent mode (Composer). Hand it the plan + the files. Cursor proposes a multi-file diff inline; accept or reject hunks visually. ### 3. Inline iterate with Cmd-K (Cursor) For tight edits inside one file, skip the agent — Cmd-K is faster. The editor stays in flow. ### 4. Open the PR (Cursor) Push the branch. Bugbot posts its review on the PR automatically — same surface as a human reviewer, so teammates see the findings too. ### 5. Patch findings inline (Cursor) Bring the Bugbot comments back into Cursor's chat panel; Composer turns them into a patch you can review hunk-by-hunk. ## What it produced **Frontend-heavy team, comparison week** On UI work, the IDE-first loop won: changes are visual, the editor is where you naturally iterate. On backend refactors that span 10+ files, the team preferred Claude Code because Composer's hunk-by-hunk acceptance got tedious. Mixed-mode users tended to keep both subscriptions active. ## Pitfalls - **Composer's tab cost on big diffs** — On a 12-file diff, accepting hunks one at a time in the editor takes longer than reading a CLI agent's summary. Pick the right surface for the size of the change. - **Bugbot is Cursor-only** — If your team also reviews from the GitHub web UI without Cursor open, Bugbot's comments are still visible (they post to the PR), but the inline IDE features are not. Make sure the PR-level review is the source of truth, not the in-editor markers. ## Verifiable artifacts - [madewithlove — testing Bugbot on real PRs](https://madewithlove.com/blog/automatic-pull-request-reviewing-with-cursors-bugbot/) — Independent dev consultancy (not Anysphere). Includes screenshots of actual Bugbot comments on their own PRs and an honest tradeoffs section — they later switched away. Good for setting expectations before adopting. ## Recent changes affecting this stack - **Cursor launches Projects for coordinating large bodies of work with multiple subagents** (2026-09-10, feature) — Projects is a new feature that maintains context over months of work and delegates tasks to thousands of subagents. A coordinator agent plans the work and delegates to implementation agents that run in parallel. Projects can watch Slack channels, follow PRs, or run on a schedule to take action automatically without prompting. Source: https://cursor.com/changelog - **Cursor launches Projects for coordinating multi-month work across thousands of subagents** (2026-09-10, feature) — Projects maintain context over months of work, with a coordinator agent that plans work and delegates to subagents running in parallel. Projects can watch Slack channels or run on schedules to take action without being prompted, keeping shared context across all agents involved. Source: https://cursor.com/changelog - **Cursor launches Projects to coordinate large bodies of work with subagent delegation** (2026-09-10, feature) — Projects enables managing feature development, migrations, and full apps with a coordinator agent that plans work, delegates to subagents, and maintains context over months. The coordinator runs agents in parallel and can watch Slack channels or run on schedules to automatically pick up work without explicit prompting. Source: https://cursor.com/changelog - **Cursor adds support for self-hosted machines with dynamic pool scheduling and computer use on Linux and Mac** (2026-09-02, feature) — Self-hosted machines keep tool execution in your own network with infrastructure like AWS Lambda, Cloudflare, and Modal. Dynamic pool scheduling lets team pools scale capacity with demand and hibernate idle machines. Agents can now use computer use (clicking, typing, screenshots) on Linux and Mac. Source: https://cursor.com/changelog - **Cursor adds self-hosted machines with dynamic pool scheduling and multi-platform computer use** (2026-09-02, feature) — Cursor now supports self-hosted machines that keep tool execution entirely in your infrastructure. Features include dynamic pool scheduling for teams with auto-scaling capacity, execution on existing platforms (AWS Lambda, Coder, Cloudflare, Modal, etc.), and computer use support on Linux and Mac for browser automation and desktop interaction. Source: https://cursor.com/changelog ## Other ways to do this - [Ship code with AI](https://aistack.sh/stack/ship-code-with-ai): Plan in Claude chat, write in Claude Code, review with CodeRabbit — $50/mo - [Antigravity (Google)](https://aistack.sh/stack/ship-code-antigravity): Google's AI IDE: Gemini 2M-context inside the editor — $40/mo - [Claude Code only](https://aistack.sh/stack/ship-code-claude-code): Pure-CLI: scope, plan, write, fix all inside Claude Code — $50/mo - [Codex (CLI + cloud)](https://aistack.sh/stack/ship-code-codex): OpenAI Codex: terminal CLI for active work, cloud lane for autonomous PRs — $40/mo - [Windsurf (Devin Local)](https://aistack.sh/stack/ship-code-windsurf): Cognition's IDE with the Devin Local autonomous-edit agent — $15/mo --- Curated by alex-w on aistack.sh. Last updated 2026-05-05.