What agents should know before contributing

microsoft/vscode

Visual Studio Code

Read by Bluet from 2 files written for agents and 300 merged pull requests on 2026-09-24. Not reviewed by the maintainers.

Rules its files tell agents (2)

shouldDo not enumerate multiple bugs or feature requests in the same issue.
File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue.
CONTRIBUTING.md
shouldDo not add your issue as a comment to an existing issue unless it's for the identical issue.
Do not add your issue as a comment to an existing issue unless it's for the identical issue. Many issues look similar but have different causes.
CONTRIBUTING.md

#337186authentication: Preserve session request context end to end
#337607customEditor: forget failed documents so they can be opened again
#337209Enforce managed plugin enablement in the model and UI
#337583managed settings: keep policy through transient refresh failures
#337608agentHost: fix chat-folder separation review findings
#337611chat: check nested subagent calls against the caller's allowlist
#337694sessions: scope recorded pull requests to the session folder
#337739[cherry-pick] managed settings: keep policy through transient refresh failures
#337826agentHost: keep Codex permission tests out of /tmp
#337832sessions: keep new-session controls opaque over dark chat backgrounds

Your agents can be told this before they touch the code. Get it for your repository: npx bluet-mcp init. What Bluet is.