You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] apm pack --format plugin for a multi-target producer ships one primitive in several renderings, and a Claude consumer keeps the wrong one #3686
When the producer's apm.yml targets more than one runtime (for example claude and copilot) and a dependency has an agent and an applyTo-scoped instruction, the plugin bundle contains both renderings: agents/reviewer.agent.md and agents/reviewer.md, instructions/x.instructions.md and instructions/x.md (plus .mdc with cursor). Installing the bundle into a fresh Claude project prints "Skipped .claude/rules/x.md: file exists with different content" and keeps the Copilot rendering, so a **/*.py-scoped instruction loses its scoping in Claude. The pack output already says bundles are target-agnostic.
To reproduce
Producer targets [claude, copilot], depends on a package with an agent and an instruction with applyTo: "**/*.py".
apm pack --format plugin, then install the bundle into a fresh Claude project.
Expected behavior
One rendering per primitive in the bundle, and the consumer gets the correct target rendering.
Actual behavior
Duplicate renderings, a collision warning, and the wrong rule kept.
Options
Keep only the Claude rendering per primitive stem.
Build plugin components from the source primitive once (target-agnostic).
Deterministic stem precedence with a warning.
Found by the 0.36.0 pre-release lifecycle sweep, round 2 (#3649). Same behavior on v0.35.1, so this is not a 0.36 regression.
Activity
danielmeppiel commentedon Nov 12, 2026
Decision (maintainer): deferred to 0.37.0.