I believe this is a known VSCode issue in Sonoma. We likely inherited it from a recent upstream merge.