Feature request: Frictionless VBA/Excel workflow between Claude Code and Claude Excel

Context

I'm a VP of Operations at a manufacturer, building production tools. Today I needed Claude Code to write VBA macros for an Excel shift report template, while Claude Excel (the add-in) handled workbook structure (named ranges, formatting, data validation). This two-tool workflow works but required an entire session of trial-and-error to discover.

Pain Points

1. No standard VBA handoff protocol

Claude Code writes .bas files but can't test them. Claude Excel can't create/modify VBA. The gap between them required inventing a "bootstrapper" module (VBA that reimports other VBA modules from disk) so Claude Code's changes could be refreshed with one button click. This pattern should be a known recipe.

2. Import vs copy-paste confusion

Claude Code generated .bas files with Attribute VB_Name headers. Copy-pasting into VBA editor causes syntax errors. The correct path is File > Import — but nothing suggested this. Cost: ~20 minutes of debugging a non-bug.

3. No shared debugging channel

VBA runtime errors are invisible to Claude Code. We solved this by writing a log file to a path Claude Code could read (output/shift_report_log.txt). This should be a built-in pattern when Claude Code generates VBA.

4. Claude Excel can't touch VBA

The add-in explicitly cannot create or modify VBA macros. This forces a two-tool workflow for any macro-enabled workbook. If Claude Excel could at least import .bas modules, the entire bootstrapper pattern becomes unnecessary.

5. No coordination protocol

There's no way for Claude Code to send instructions to Claude Excel or vice versa. I manually copy-pasted setup prompts between them. Even a shared context file would help.

What Would Help

• A "VBA project" recipe in Claude Code: generates .bas files + a bootstrapper module + a log utility, with instructions for the user
• Claude Excel .bas import support: let the add-in import VBA modules from disk
• Shared context between Claude Code and Claude Excel: if both are open, they should be able to see each other's work
• Or just let Claude Code drive Excel via COM/automation on Windows — this would eliminate the two-tool problem entirely

Environment

• Windows 11, Excel 365, Claude Code CLI, Claude Excel add-in (Pro plan)
• Use case: manufacturing production tools, VBA macros for supervisor shift reports

🤖 Generated with Claude Code