Claude Code: Don't Attach Open File by Default
Original title:Claude Code – Don't Attach Open File by Default
AI Summary
A GitHub issue asks Claude Code not to automatically attach the file currently open in an editor by default. The available material identifies this as a product interaction request, but provides no issue-body details, reproduction steps, maintainer response, or implementation status. Its Hacker News listing has a score of 2 and 0 comments, so the discussion has received little visible attention. The practical concern is control and predictability around contextual file sharing.
Why it's worth reading
As Claude Code expands editor integrations, default file attachment directly affects context boundaries, privacy expectations, and user control, making this small issue relevant to workflow design.
Deep Read
What happened
Original facts: The supplied source points to GitHub issue #63925 in anthropics/claude-code, titled “Don't Attach Open File by Default.” The Hacker News summary reports a score of 2 and 0 comments.
Core tech
Original facts: The supplied material does not explain which editor integration, hook, or request-building path attaches the open file. Analysis: The underlying design question is whether editor state should be converted into model context automatically or require explicit user confirmation. The implementation mechanism remains unknown.
Key evidence & numbers
Original facts: The issue number is #63925; the supplied publication timestamp is 2026-08-02T10:00:58.000Z; the Hacker News listing shows score 2 and 0 comments. Unverified inference: These figures do not establish how many users are affected, nor whether the issue has been accepted or fixed.
Why it matters
Analysis: Automatically attaching a file changes the boundary of what users may believe they sent. It can create risks involving accidental code disclosure, larger prompts, and shifted model attention. For agentic development tools, implicit context also affects predictability and auditability.
Practical impact
Analysis: If the behavior exists as described, users may need to inspect which files are actually included in each request. Product options could include disabling default attachment, asking for confirmation, clearly listing attached files, and exposing a persistent preference. These are design suggestions, not features confirmed by the source.
Limitations & uncertainty
Quality note: The available evidence contains only a title and a Hacker News summary. It does not include the issue body, screenshots, client version, editor scope, maintainer comments, commits, or current status. Therefore the trigger, severity, affected platforms, and resolution cannot be established. The supplied publication timestamp was not independently verified here.