Skip to content

[BUG] Agent generates mock/fallback data despite explicit user instructions not to #8842

@agocorona

Description

@agocorona

Problem (one or two sentences)

Roo Code consistently generates code with mock/fallback data, simulations, and fake data even when explicitly instructed in multiple iterations not to do so. The agent appears to filter out critical programmer instructions regarding this issue.

Context (who is affected and when)

This affects developers using Roo Code for code generation, particularly when working on production applications that require real data integration (APIs, databases, etc.). It happens repeatedly throughout development sessions, even after providing explicit instructions against using mock data.

Reproduction steps

  1. Start a new Roo Code task requesting code generation for a feature that requires real data (e.g., API integration, database queries)
  2. Explicitly instruct the agent: "Do not use mock data, fake data, or fallback data. Use real API/database connections."
  3. Observe the generated code
  4. Notice that despite the explicit instruction, the code contains mock/fallback data, simulated responses, or fake data
  5. Repeat the instruction in follow-up iterations
  6. Observe that the behavior persists across multiple iterations

Expected result

The agent should respect user instructions and generate code with real data connections (actual API calls, database queries, etc.) without any mock/fallback data when explicitly instructed to do so.

Actual result

The generated code includes mock data, fallback data, simulations, and fake data implementations, even after repeated explicit instructions not to include them. This creates the appearance of problem resolution without actually implementing the requested functionality.

Variations tried (optional)

  • Tried rephrasing instructions multiple times
  • Tried adding explicit notes in code comments
  • Tried using different phrasings ("no mock data", "no fake data", "no fallback data", "use only real connections")
  • Tried emphasizing the instruction in multiple iterations
  • The issue persists regardless of how the instruction is provided

App Version

Latest version (as of October 2025)

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue/PR - TriageNew issue. Needs quick review to confirm validity and assign labels.bugSomething isn't working

    Type

    No type

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions