pnpm-to-Bun silent swap reveals agent rules governance gap
Key insights
- Coding agents resolve conflicts between instruction files silently, choosing arbitrarily with no indication a conflict was detected or logged.
- Split .rules files with contradictory directives caused an agent to swap package managers mid-PR without surfacing the conflict.
- The failure pattern extends beyond package managers to security policy conflicts and environment-specific configuration files.
Why this matters
As coding agents operate across larger repos with more instruction files, silent conflict resolution becomes a source of undetected infrastructure drift that standard CI checks won't catch. Teams relying on multi-file governance architectures (CLAUDE.md, Cursor rules, Copilot instructions) currently have no tooling to detect or prioritize contradictions between files. The governance gap applies to any LLM-based coding tool that processes multiple instruction sources without a conflict-resolution protocol, making this a cross-vendor structural problem rather than a single-product bug.
Summary
Coding agents don't adjudicate between competing instruction sources. They pick one silently, with no audit trail.
A developer on r/PromptEngineering found this firsthand: their agent switched from pnpm to Bun mid-PR, causing split lockfile conflicts across the repo. Two separate .rules files had contradictory package-manager directives. The agent resolved the contradiction arbitrarily and kept generating code as if nothing had happened.
Essentially: any team running multi-file agent instruction governance is exposed to this gap.
- Agents silently arbitrate conflicting rules files with no priority system or conflict surfacing.
- The failure mode is a governance-layer gap, separate from prompt quality or model capability.
- Commenters noted the pattern extends to security policy conflicts and environment-specific config files.
With multi-file instruction architectures now standard practice, silent conflict resolution is a systemic engineering risk.
Potential risks and opportunities
Risks
- Teams using Cursor or GitHub Copilot with overlapping rules files could experience silent config drift in production infrastructure, undetected until a deployment fails
- Security policy conflicts between instruction files could cause agents to silently drop access controls, creating audit failures for companies in regulated industries (finance, healthcare)
- Monorepos using package-manager-sensitive tooling (Nx, Turborepo) face lockfile corruption if agents resolve competing directives without flagging the contradiction to the developer
Opportunities
- Agent governance tooling vendors (Promptfoo, Invariant Labs) could build conflict-detection layers for multi-file instruction architectures as a distinct product category
- Cursor, Windsurf, and GitHub Copilot have an opening to differentiate by adding conflict surfacing and explicit priority rules to their instruction-file parsing pipelines
- Enterprise DevOps teams could formalize single-source-of-truth instruction files as policy, creating demand for linting tools that validate agent configuration files before PRs run
What we don't know yet
- Whether major coding agent platforms (Cursor, GitHub Copilot, Windsurf) have any documented conflict-resolution priority order between instruction files
- The specific agent product used in the original report was not named, leaving open whether this behavior is platform-specific or universal across agent tooling
- Whether any agent vendor plans to surface instruction-file conflicts as an explicit warning before proceeding, rather than resolving them silently
Originally reported by reddit.com
Read the original article →Original headline: r/PromptEngineering: Agent Silently Switched From pnpm to Bun Mid-PR Because Two Rules Files Contradicted Each Other — Conflicting Governance Documents Are an Underreported Failure Mode