Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Feature Request] MCP protocol needs push-style edit notifications for IDE integrations [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52360•Fetched 2026-04-24 06:09:14
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
sinkovskysinkovsky
Participants
sinkovskysinkovsky
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Experimenting with a claude-code-ide.el fork for Emacs and hit a gap in the IDE protocol.

Observation: In acceptEdits permission mode for in-project files, the CLI writes directly to disk without emitting any MCP signal to the connected IDE. Verified via WebSocket trace — no openDiff, no openFile, no notification. Only getDiagnostics pings around the edit.

This forces IDE integrations to fall back to OS-level file watchers, losing semantic context (which tool, what changed, what the diff was).

Verification:

  • Reverse-engineered the compiled CLI binary (2.1.118, Mach-O) via string analysis
  • Extracted the official VS Code extension and confirmed all 12 MCP tool registrations: openDiff, openFile, close_tab, closeAllDiffTabs, getDiagnostics, getOpenEditors, getWorkspaceFolders,
    getCurrentSelection, getLatestSelection, checkDocumentDirty, saveDocument, executeCode
  • None are push-style; none fire for auto-mode in-project edits

Request: Push-style lifecycle events via MCP —

  • editApplied { path, oldText, newText, range, tool }
  • editPending { path, tool }
  • sessionStarted / sessionEnded

Would let IDEs render live edit views, highlight changed lines, navigate edit history — without
filesystem polling. Happy to help design/test.

extent analysis

TL;DR

Implementing push-style lifecycle events via the MCP protocol, such as editApplied and editPending, could resolve the issue of IDE integrations losing semantic context during in-project file edits.

Guidance

  • Review the MCP protocol documentation to understand the existing event types and their limitations.
  • Discuss the proposed editApplied and editPending events with the protocol maintainers to determine the best approach for implementation.
  • Consider implementing a proof-of-concept using the proposed events to demonstrate the benefits of push-style lifecycle events.
  • Investigate the feasibility of adding sessionStarted and sessionEnded events to provide additional context for IDE integrations.

Example

No code snippet is provided as the issue focuses on protocol design and implementation rather than specific code changes.

Notes

The implementation of push-style lifecycle events may require significant changes to the MCP protocol and the CLI binary. Collaboration with the protocol maintainers and the development team will be necessary to ensure a successful implementation.

Recommendation

Apply a workaround by implementing the proposed editApplied and editPending events, as this would provide the necessary semantic context for IDE integrations without relying on OS-level file watchers.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#integration issue#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING