XLIDE brings VBA into VS Code (2026)

If your VBA work still lives inside Excel's built-in editor, the pain usually starts when you want normal source control, fast navigation, tests, or an AI assistant that can inspect the real workbook instead of a pasted module. XLIDE: VBA for VS Code is today's pick because it moves .xlsm, .xlsb, and .xlam workbook code into VS Code while still writing changes back to the workbook file. 1

The important distinction: XLIDE can read, edit, analyze, import, and export VBA without COM or Office automation. It uses a Python backend with pyOpenVBA and openpyxl to work directly with the VBA source package, so editing and analysis can run on macOS and Linux as well as Windows. 2 Running macros and workbook tests still needs Windows with Microsoft Excel installed. 1

At a glance

Plugin	XLIDE: VBA for VS Code
Extension ID	`WilliamSmithE.xlide` 1
Current version	v2.5.5 3
IDE	VS Code 1.95 or newer 3
Language / files	Excel VBA in `.xlsm`, `.xlsb`, and `.xlam` workbooks 1
Use case	Workbook-aware editing, diagnostics, module sync, tests, and AI-assisted workbook automation 1
Runtime requirements	Python 3.10+, `pyOpenVBA`, and `openpyxl` for core workflows; Windows + Excel for macro and test execution 1
License / cost	MIT licensed, free to install 2
Install	Visual Studio Marketplace

What problem it solves

XLIDE is aimed at the Excel automation developer who has outgrown the Visual Basic Editor but still has to ship real workbook code. After installation, you open a VS Code folder containing macro-enabled workbooks, choose a workbook from the XLIDE Activity Bar, and open modules from a workbook tree. The modules appear as writable xlide-vba documents, and normal VS Code save behavior writes edits back to the workbook. 4

That gives VBA projects several workflows that are awkward in the stock editor: source-control-friendly .bas and .cls sync, workbook-wide static analysis, Go to Definition, Find All References, Rename Symbol, hover, signature help, semantic coloring, and completions that can include workbook symbols and Excel object model members. 1

The release pace is unusually fast for a young developer tool. William Smith Edward has shipped 13 releases from v1.0.7 on May 26, 2026 through v2.5.5 in late June, and the GitHub repository shows 46 stars, 3 forks, 617 commits, and 13 releases. 5 2

Usage demo: put workbook logic under test

Here is the workflow I would try first on a finance or operations workbook: open the workbook in XLIDE, export the modules to a folder, add a small test module, run the tests through XLIDE, then commit both the exported VBA files and the test artifacts. XLIDE's test guide defines tests as ordinary zero-argument Sub procedures in standard modules, marked by an apostrophe comment immediately above the procedure. 6

' @xlide-test tags=smoke,invoice owner=finance requirement=INV-104
Public Sub InvoiceTotal_AddsTax()
    XlideAssert.AreEqual 108, InvoiceTotal(100, 0.08)
End Sub

To run it, install the bundled XlideAssert.bas support module from XLIDE's Tests GUI, then use XLIDE: Run VBA Tests, XLIDE: Run VBA Tests With Options, XLIDE: Run VBA Tests In Current Module, or XLIDE: Run VBA Test At Cursor. XLIDE runs tests against a temporary copy of the workbook in an XLIDE-owned Excel instance, closes Excel without saving after the run, and cleans up temporary files. 6

For CI-style tracking, each run can write summary.json, host-trace.json, output.log, and status_for_ci.json under a timestamped workbook test folder. The status_for_ci.json file is the compact pass/fail artifact meant for automation. 6

Why it is interesting now

XLIDE is not just a syntax highlighter. The v2.0.0 changelog describes the extension's shift from a workbook/module bridge into a fuller VBA development environment with project-aware editing, deterministic analysis, previewable sync, workbook tests, safer workbook mutation, and agent-verifiable workflows. 5

The diagnostics work is the most convincing maturity signal so far. XLIDE v2.5.0 completed an MS-VBAL §5.6 expression binder and a syntax-corpus completeness milestone, with 2,071 tests and 397 VBE oracle cases listed in the v2.5.0 roadmap. 7 The v2.5.x patch sequence then focused almost entirely on reducing false positives in the diagnostics engine. 5

One example: v2.5.3 stopped flagging hidden VBA built-ins such as VarPtr, StrPtr, ObjPtr, byte-string helpers, and vbLongLong as undeclared, which reduced fastjson's LibJSON report from 61 errors to 2 in the changelog's example. 5 Another: v2.5.5 changed mismatched-end-keyword from an error to a warning after VBE oracle testing showed that VBE accepts cross-type procedure closers such as Property Get ... End Function. 5

The performance story also matters. XLIDE v2.3.0 cut full analysis time for a 4,000-line module from about 115 seconds to about 0.95 seconds, and the VSIX size dropped from 2.1 MB to about 536 KB. 5 Those numbers turn static analysis from a background chore into something you can use while editing.

AI and automation angle

XLIDE exposes workbook-aware tools to compatible VS Code AI assistants. The Marketplace page says AI assistants can inspect the real workbook, read and write VBA modules, analyze code, run tests, inspect worksheet data, and sync modules with files through explicit XLIDE tools. 1 The package metadata lists tools including xlide_listWorkbooks, xlide_getWorkbookInfo, xlide_readModule, xlide_writeModule, xlide_analyzeWorkbook, xlide_runVbaTests, xlide_listSheets, xlide_readCells, and xlide_writeCells. 3

That is a better fit for AI-assisted spreadsheet maintenance than pasting a module into chat. The assistant can work against the workbook model, run analysis, and use the same test loop a developer uses. Treat that as a reviewable workflow, not as permission to let an agent mutate production spreadsheets without a diff.

Adoption and caveats

Community attention is early but real. The launch post in Reddit's r/vba community, which had 63,577 subscribers in the captured data, received 49 upvotes, a 98% upvote ratio, and 10 comments. 8 Hacker News also surfaced the project with 65 points and 29 comments. 9

The caveats are practical:

Execution is still Windows-bound. Editing and analysis can avoid COM, but running macros and tests requires Windows with Microsoft Excel installed. 1
The project is young. The same rapid release cadence that produced 13 releases in under four weeks also means teams should expect behavior to move quickly. 5
UserForm support is limited. The Marketplace compatibility table says XLIDE supports VBA code-behind, not direct designer file editing. 1
Marketplace install count is not visible in the captured page. Use GitHub activity and community discussion as the available maturity signals rather than assuming broad adoption.

Install or skip?

Install XLIDE if you maintain non-trivial Excel VBA and want VS Code editing, source control, static analysis, and a test loop around workbook code. It is especially appealing if your team edits on macOS or Linux but runs validation on a Windows Excel machine.

Skip it for now if your work depends heavily on UserForm designer editing, if your organization cannot run early-stage extensions against sensitive workbooks, or if you need the whole workflow to run without Windows Excel. The core editing path is cross-platform, but execution is not.

Cover image: XLIDE Reddit post preview from r/vba

XLIDE brings VBA into VS Code