[BUG] VS Code extension: Claude can't see problems of the file past a certain line

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

IDE diagnostics (TypeScript/ESLint errors) are only reported in the PostToolUse hook output when the edited line is near the top of the file. Errors on lines further down are silently missing even when an edit is made directly on that line.

What Should Happen?

After any edit, Claude should receive all diagnostics for the edited file (or at minimum all diagnostics in the vicinity of the edited line), regardless of the line number.

Error Messages/Logs

Steps to Reproduce

1. Open a file that is ~290+ lines long in VS Code with the Claude Code extension active.
2. Introduce an identical linter/TS error near the top of the file (e.g. line 14: unused variable const x = 5).
3. Introduce the same type of error near the bottom of the file (e.g. line 274: another unused variable).
4. Make a small edit on line 14 -- Claude correctly receives the diagnostic for line 14 in the PostToolUse hook output.
5. Make a small edit on line 274 -- Claude receives NO diagnostics at all, even though the error is visible in VS Code's Problems panel.

Both errors are confirmed present in the Problems panel throughout. The only difference is the line number.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.183

Platform

AWS Bedrock

Operating System

Windows

Terminal/Shell

Other

Additional Information

The PostToolUse system-reminder for the deep-line edit contained no ide_diagnostics block at all. This prevents Claude from seeing and fixing linter/TS errors in the lower portion of longer files, making the diagnostics feature unreliable for any file of meaningful size.