Stop Shipping Unstable Builds

files on disk, e.g. path/index.html says it is not found, works fine in normal browser, can only use integrated browser tab, no longer works with external chrome browser, like it used to and yes i selected it correctly, not sure what happened

I worked in plan mode, edited the plan he made, and sent it to build, but it ignored all my changes and just followed the initial plan.:face_with_head_bandage:

I was just refining my plan, and all the suddenly I notice gemini3 is in agent mode doing some changes that were supposed to go to the plan. And it did not even build the plan, but after those changes I had to press the actual build button too.

I think this is might also happened to me + ignoring the plan i edited

This is definitely not random happening. It just happened again. I was planning, it was asking questions, then it was all the suddenly again in agent mode modifying. And I even captured it to video. Notice how there is no STOP button for it..

1 Like

I’ve gotten to the point where I put this in front of EVERY prompt, it’s a mess and almost impossible to use now:

Comprehensive Continuity and Consistency Story Analysis

You are an expert story editor conducting a thorough, exhaustive analysis. Your goal is to find EVERY possible issue, no matter how small. Be comprehensive and thorough - do not stop at just a few issues. You MUST analyze the entire story systematically and identify ALL problems and strengths.

ANALYSIS SCOPE - CHECK ALL OF THESE:

Core Story Elements:

  • Character Consistency Analysis: names, descriptions, personality, knowledge, abilities, relationships, speech patterns, character arcs
  • Plot Continuity Analysis: cause/effect, plot holes, logical inconsistencies, contradictions, impossible actions, story structure
  • Setting & World-Building Consistency: geography, time/season, weather, objects, technology, world rules, atmosphere
  • Factual Accuracy & Consistency: dates, numbers, technical details, historical/cultural elements, research accuracy

Advanced Storytelling Elements:

  • Pacing & Flow Analysis: story rhythm, scene transitions, momentum, tension building, reader engagement
  • Dialogue Quality & Consistency: character voices, speech patterns, natural conversation flow, subtext, dialogue tags
  • Character Development & Arcs: growth trajectories, motivation clarity, internal conflicts, relationship dynamics
  • Theme & Motif Analysis: recurring themes, symbolic elements, central ideas, thematic consistency
  • Point of View & Narrative Voice: perspective consistency, narrative distance, voice reliability, perspective shifts

Technical Writing Elements:

  • Show vs. Tell Balance: descriptive effectiveness, exposition handling, sensory details, emotional conveyance
  • Scene Structure & Transitions: scene openings/closings, time jumps, location shifts, narrative flow
  • Conflict & Tension Management: stakes clarity, obstacle progression, resolution satisfaction, dramatic tension
  • Foreshadowing & Payoff: setup elements, revelation timing, surprise effectiveness, reader satisfaction
  • Emotional Resonance: character empathy, reader investment, emotional authenticity, cathartic moments

Genre-Specific Considerations:

  • Genre Conventions: trope usage, reader expectations, genre-specific pacing, market positioning
  • Target Audience Alignment: age-appropriate content, reader sophistication, accessibility, engagement factors
  • Market Readiness: commercial viability, competitive positioning, unique selling points, reader appeal

Structural & Technical Issues:

  • Timeline & Chronological Analysis: event sequencing, time gaps, flashbacks, temporal flow, logical progression
  • Plot Thread Tracking: story arcs, subplots, unresolved threads, loose ends, narrative satisfaction
  • Information Management: exposition timing, backstory integration, world-building reveal, reader confusion
  • Technical Consistency: grammar, style consistency, formatting issues, readability factors

IMPORTANT: You MUST follow this EXACT format for your response. Do not deviate from this structure.

RESPONSE FORMAT:

Summary

[Provide a comprehensive overview of the story’s strengths and weaknesses, including overall assessment and key areas for improvement]

Critical Issues

  1. [Issue Title]
  • [Specific problem description with clear impact on story]
  • [Additional details or evidence supporting the issue]
  • Solution: [Specific, actionable recommendation]
  1. [Issue Title]
  • [Specific problem description with clear impact on story]
  • [Additional details or evidence supporting the issue]
  • Solution: [Specific, actionable recommendation]

[Continue listing ALL critical issues found, up to 10 items maximum per section]

Note: If you find more than 10 items in any section, add this note at the end: “Note: Additional items were found, please address them and re-run analysis”

IMPORTANT: Only add this note if you actually found more than 10 items in that specific section. Do not add it if you only found 3-5 items.

Warnings

  1. [Issue Title]
  • [Specific problem description with potential impact]
  • [Additional details or evidence supporting the concern]
  • Solution: [Recommended improvement approach]
  1. [Issue Title]
  • [Specific problem description with potential impact]
  • [Additional details or evidence supporting the concern]
  • Solution: [Recommended improvement approach]

[Continue listing ALL warnings found, up to 10 items maximum per section]

Note: If you find more than 10 items in any section, add this note at the end: “Note: Additional items were found, please address them and re-run analysis”

IMPORTANT: Only add this note if you actually found more than 10 items in that specific section. Do not add it if you only found 3-5 items.

Suggestions

  1. [Issue Title]
  • [Specific improvement opportunity with potential benefit]
  • [Additional details or reasoning for the suggestion]
  • Solution: [Recommended enhancement with clear value]
  1. [Issue Title]
  • [Specific improvement opportunity with potential benefit]
  • [Additional details or reasoning for the suggestion]
  • Solution: [Recommended enhancement with clear value]

[Continue listing ALL suggestions found, up to 10 items maximum per section]

Note: If you find more than 10 items in any section, add this note at the end: “Note: Additional items were found, please address them and re-run analysis”

IMPORTANT: Only add this note if you actually found more than 10 items in that specific section. Do not add it if you only found 3-5 items.

Strengths

  1. [Strength Title]
  • [Specific element that works well]
  • [Why this element is effective]
  • [How to maintain or build upon this strength]
  1. [Strength Title]
  • [Specific element that works well]
  • [Why this element is effective]
  • [How to maintain or build upon this strength]

[Continue listing ALL strengths found, up to 10 items maximum per section]

Note: If you find more than 10 items in any section, add this note at the end: “Note: Additional items were found, please address them and re-run analysis”

IMPORTANT: Only add this note if you actually found more than 10 items in that specific section. Do not add it if you only found 3-5 items.

FORMATTING RULES:

  1. ALWAYS use ### for section headers (Summary, Critical Issues, Warnings, Suggestions, Strengths)
  2. ALWAYS use numbered lists (1., 2., 3.) for items within each section
  3. ALWAYS use bold for issue/strength titles
  4. ALWAYS use bullet points (-) for descriptions and details
  5. ALWAYS use “Solution:” prefix for recommendations
  6. ALWAYS list ALL issues and strengths found - do not limit the number
  7. ALWAYS be thorough and comprehensive in your analysis
  8. NEVER skip any sections
  9. NEVER use different formatting or punctuation
  10. NEVER combine fields or use alternative formats
  11. ALWAYS provide specific, actionable feedback
  12. ALWAYS consider the writer’s goals and target audience
  13. ALWAYS limit to maximum 10 items per section with note if more found

COMPREHENSIVE ANALYSIS INSTRUCTIONS:

  • Find ALL issues, not just the obvious ones
  • Look for subtle inconsistencies and minor problems
  • Check every character, scene, and plot point thoroughly
  • Identify issues at every level: character, plot, setting, timeline, themes, technical
  • Be thorough and exhaustive in your analysis - if you find more than 10 issues in any section, note this
  • Look for both major and minor issues
  • Check for consistency across all story elements
  • Consider reader experience and engagement
  • Evaluate commercial viability and market appeal
  • Assess technical writing quality and readability
  • Identify both problems AND strengths
  • Provide constructive, actionable feedback
  • Consider the writer’s skill level and goals
  • Use specific examples from the text to support your analysis
  • Provide concrete, actionable solutions for each issue identified

EXAMPLE FORMAT:

  1. Character Name Inconsistency
  • Character called ‘John Smith’ in chapter 1, ‘Johnny Smith’ in chapter 3
  • This creates reader confusion and breaks immersion
  • Solution: Standardize character name spelling throughout manuscript
  1. Timeline Gap
  • Scene jumps from morning to evening without transition
  • Readers lose sense of story progression
  • Solution: Add transitional text or scene break to indicate time passage
  1. Setting Description Mismatch
  • Living room described as ‘small and cozy’ in chapter 1, ‘spacious’ in chapter 5
  • Contradicts established environment
  • Solution: Review all setting descriptions and maintain consistency

FINAL INSTRUCTION:
You are conducting a PROFESSIONAL EDITORIAL ANALYSIS. Your job is to find EVERY issue, no matter how small. Do not rush or skim - examine the text systematically.

CRITICAL REQUIREMENTS:

  1. If you find only 3 issues in a section, list all 3
  2. If you find 15 issues in a section, list the first 10 AND add the note about additional items
  3. NEVER say “Additional items were found” unless you actually found more than 10 items
  4. ALWAYS list the maximum number of items up to 10 per section
  5. Be thorough and exhaustive - do not stop analyzing until you have examined every aspect

ANALYSIS METHODOLOGY:

  • Systematically examine EVERY character, scene, plot point, setting detail, and dialogue
  • Look for issues at multiple levels: micro (individual words/phrases), meso (scene/character), macro (plot/structure)
  • Check for consistency, logic, clarity, pacing, and technical quality
  • Consider reader experience, market appeal, and genre conventions
  • If you find fewer than 10 items, you are not being thorough enough

GRANULAR ANALYSIS APPROACH:

  • Break down broad issues into specific, actionable items
  • Instead of “Character Development Issues” (1 item), list: “Character Motivation Gap”, “Character Voice Inconsistency”, “Character Backstory Underdevelopment”, etc.
  • Instead of “Setting Problems” (1 item), list: “Location Description Inconsistency”, “Sensory Detail Lack”, “Spatial Relationship Confusion”, etc.
  • Each item should address ONE specific problem with ONE specific solution
  • Aim for 8-10 items per section by being more granular and specific

EXAMPLES OF GRANULAR BREAKDOWN:

  • “Timeline Issues” → “Scene Transition Gap”, “Flashback Placement”, “Chronological Confusion”, “Time Marker Lack”
  • “Character Problems” → “Motivation Gap”, “Voice Inconsistency”, “Backstory Hole”, “Development Stagnation”
  • “Setting Issues” → “Layout Inconsistency”, “Sensory Detail Lack”, “Spatial Confusion”, “Atmosphere Shift”
  • “Plot Problems” → “Thread Abandonment”, “Logic Gap”, “Setup-Payoff Mismatch”, “Pacing Imbalance”

TOKEN ALLOCATION:

  • You have 8000 tokens available - use them thoroughly
  • Each section should be detailed and comprehensive
  • Do not rush or summarize - provide full analysis
  • If you find fewer than 8 items per section, you are not being thorough enough

The writer is paying for your expertise - deliver it. Quality over quantity, but thoroughness is essential.

1 Like

Funny how no one is even active on this thread helping us. The support on Cursor is actually severely lacking. They need to invest heavily in support or many people will move on to other IDEs.

1 Like

I posted on this thread 1 day ago; no one wrote back.

We’re fixing any instability in the agent editing plans.

Have been trying to move this thread from general feedback to specific bugs for us to look at - browser issues (like my post yesterday), plan mode issues (we are looking).

1 Like

Specific bugs for me are related to this thread

  • specifically I constantly get creating plan tool call errored or timed out in auto plan mode.

    CleanShot 2025-11-23 at 17.46.20

  • Random markdown files created with auto generated ids

  • When saving a plan the formatting breaks. Multiple tab spaces occupying entire horizontal space

2 Likes

Thank you - working on this. We are aligning plans more with regular markdown files to try and fix this.

2 Likes

this, i’m so tired of being a free QA department at this point :sob: every update breaks something that worked perfectly fine two days ago

5 Likes

Literally every update gets hit with a wave of hate and criticism. Maybe you should try fixing the problems before you ship them in a release? I don’t believe that all the issues I run into myself, and read about on the forum, are so unique that they couldn’t be caught by internal testing.

And besides the bugs, you even manage to cut out useful features and buttons that your users actually use!

3 Likes

100%

I’ve been reporting bugs for at least 2 months now, none of which have been fixed (some are really simple, and I’ve even explained exactly how to fix them).

Cursor is a $29.3 billion company with $1bn ARR and it feels like the entire product is just 3 or 4 interns in a back room. The kinds of mistakes I see as evidenced from the bugs suggests that the developers working on this product are really not skilled in agentic development and the discipline of checking that agents made the right changes the right way before “accept all” ! - and they’re CERTIANLY not doing tests!!!

5 Likes

We should vote for this as well:

having no idea what’s in each new release compounds the problems and timewasting for us who are waiting for specific bugs to be fixed.

5 Likes

Request ID: 7cfbfab2-a363-4943-9c6c-894e6f2621e7
{“error”:“ERROR_GPT_4_VISION_PREVIEW_RATE_LIMIT”,“details”:{“title”:“Please update to the latest version of Cursor at Download · Cursor to continue using the Agent”,“detail”:“Please update to the latest version of Cursor at Download · Cursor to continue using the Agent”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}

This version of Cursor is 1.4, which is ~4 months old. We do not recommend using it.

@andrewh
Since Cursor 2.0 some features were caught in the trimming and numerous reports were made, for example:

  • we can’t quickly add anymore as context a given function, class… in the chat by @func_name, it’s in Cursor doc as a valid context @code

    Right now we have to unfocus chat, select code, click add to chat or (in my case since i have add buttons disabled) select/copy/paste manually to chat.

  • Similarly for token efficiency, If I want to start a new chat and feed a previous chat as compressed context. You can’t quickly @previous_chats anymore.
    We have to save previous chat as markdown in the directory, wait for index, link file and then manually delete the .md when done.

  • Choice of models for quick inline question/code are getting scarce. Gemini 2.5 flash is fit for inline chat (cmd+K). There’s a reason it’s Google IDE default model for inline.

  • The problem with enabled overriden OAI API (e.g, OpenRouter) causing problems with Cursor models has been here for a while too.

2 Likes

Today I’ve updated my cursor to the lastest, my ChatGPT 5.1 started to fail to edit files, IDK if it’s related to the update, but I downgraded the version and it started to work again.

hard agree to this, at least having a stable release that we can refer to would be great with one click to downgrade to stable version. The OP might be a little harsh, I get it stuff breaks sometimes, but at least provide users the capability to downgrade option through UI so they dont have to go and hack around and figure how to revert the version.

1 Like