# Reported issues for XLIDE Pod holds 6 of 6 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects. Back to [XLIDE](/mcp/xlide). ## Most discussed ### Locked-file ergonomics: name the lock, move a read-only copy aside, never lose unsaved work xlide_vscode's next release changes how it treats a file its Office application has open. Three of those changes apply to this server's write tools, which today raise one message for every locked save: "most likely open in {app} ... ask the user to close it". ### 1. Name the lock (no COM needed for most of it) An agent can only relay what it is told, and the cases are different instructions for the user. Measured on build 16.0.20326, a read-only workbook in Excel never locks the file, so for… [Read the thread](https://github.com/WilliamSmithEdward/xlide_mcp/issues/4) · 2026-09-22 · closed · 2 comments ### Tool Calls with XLIDE MCP inside of VS Code with XLIDE: VS Code Extension Installed are not Showing Edits / Tree Indicators etc. Please investigate and consider xlide: vscode specific integration (if xlide: vscode is detected) also, xlide vscode tree is not updating with tool calls like adding module / renaming etc. [Read the thread](https://github.com/WilliamSmithEdward/xlide_mcp/issues/3) · 2026-09-22 · closed · 1 comment ### Close the gap with the xlide_vscode tool surface: references, and shapes beyond the macro link The two agent surfaces have drifted apart. This server exposes 49 tools and the VS Code extension registers 25, and the overlap is close enough that the gaps are worth closing rather than living with: an agent that can reach a file through XLIDE but not through here has to be told which of two tool sets it is holding. Compared tool by tool against xlide_vscode 10.5.0. Most of the extension's surface already has an equivalent here, usually under a snake_case name - `listSubs`/`list_procedures`,… [Read the thread](https://github.com/WilliamSmithEdward/xlide_mcp/issues/2) · 2026-09-22 · closed · 1 comment ### Verify: a file with no VBA, and whether a write is visible to a file watcher Two things surfaced while fixing xlide_vscode 10.5.0 that this server is either implicated in or inherits. Both need checking here; neither is confirmed on this side yet. ### 1. A file with no VBA in it reads as a failure pyOpenVBA raises `VBAProjectError` at open for an .xlsm or .docm with no `vbaProject.bin` part, and raises "No 'dir' stream found; not a valid VBA project" on every read for a .xls or .doc with no macros. Filed there as WilliamSmithEdward/pyOpenVBA#26 with the measurements.… [Read the thread](https://github.com/WilliamSmithEdward/xlide_mcp/issues/1) · 2026-09-22 · closed · 1 comment ### Add tool for surgical in place module edit and selective reads Allow agents to make fine tuned edits to a module directly, and read portions of the module, without having to export+modify+reimport the full file, or read the full file, for every tool call. Needs to allow read/writing multiple areas or parts of the module in one tool call to be efficient [Read the thread](https://github.com/WilliamSmithEdward/xlide_mcp/issues/10) · 2026-09-24 · closed · 0 comments ### HTTP transport bug Both http transports are broken against the installed mcp 2.2.0 main.py line 130 does server.settings.host = args.host, but FastMCP's settings no longer has that field and pydantics rejects it: ValueError: "Settings" object has no field "host". the flags have defaults, so it fires even without --host. Line 128 returns first for stdio, which is why stdio is unaffected. [Read the thread](https://github.com/WilliamSmithEdward/xlide_mcp/issues/9) · 2026-09-24 · closed · 0 comments ## Most recent The remaining reports are on [the project's issue tracker](https://github.com/WilliamSmithEdward/xlide_mcp/issues).