liveBook · Manning

Conflicting context

As explained in Vibe Engineering

A conflicting signal is a context failure in which instructions or guidance are contradictory, ambiguous, or inconsistently presented.

Conflicting context occurs when an agent receives contradictory, ambiguous, or inconsistently presented guidance. Prompt wording, documentation, and code comments can pull the implementation toward incompatible approaches, producing code that partially satisfies several instructions but fully aligns with none. section 3.6

Choosing the reliable signal

A refactoring request names the StripeV3 client, while an old code comment references v1. A disciplined agent identifies the conflict, treats the package.json dependency as the stronger source of truth, states its interpretation, and asks for approval before proceeding. section 3.6.1

Reduce the risk before accepting generated code:

  • Require the agent to analyze dependencies, compare available guidance, describe intended changes, and plan error-handling or data-structure updates before coding. section 3.6.1
  • Review the stated interpretation before reviewing implementation details; explicit reasoning exposes outdated assumptions and makes human approval part of the workflow. section 3.6.1
Figure 3.12 Cline drafting plan of the execution.

A visible execution plan makes the agent’s chosen interpretation inspectable before implementation begins; the companion approval view supports a human checkpoint. section 3.6.1

How Vibe Engineering covers it

How deep it goes
Defines the failure and demonstrates interpretation, planning, auditability, and approval, while distinguishing it from poisoned context.
Examples
Uses a StripeV3 migration conflicting with an old v1 comment, plus Cline execution plans awaiting approval.
What you can do after
Diagnose/debug with it by exposing conflicting guidance, selecting a stronger source of truth, and reviewing the agent’s plan before coding.
How it connects
Connects prompt interpretation with documentation, code comments, dependency definitions, Chain-of-Thought, auditability, and human-in-the-loop review.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.