Extend YAML file protection in dangerous-command approval

Cluster 45749 · agent. Data as of 2026-10-25 11:21 UTC

2 open items. Fix attempted, not merged.

open issue

open PR

items grouped

Known?: Yes. 3 related items grouped here, 0 issues already closed.
Fix event: No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: 1 issue and 1 PR.

Next step: read the attempts below. Your case may extend or revive that work.

These items propose blocking sed/perl in-place edits on all .yaml/.yml files, not just config.yaml, within a dangerous-command approval mechanism.

Open issues1

Issue#45749Dangerous-command approval: extend YAML protection to all .yaml/.yml files (not just config.yaml)

From the close comments: closed without comment 1

#45750 feat(approval): block sed/perl -i on all .yaml/.yml files · closed without comment

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

The same facts, typed.