CLAUDE CODE + EXCEL VBA

Stop doing
AI's job.

For VBA developers.

You paste. You fix conflicts. You test. You paste the error back. You wait. You run again.
This isn't AI-assisted development. This is you doing all the work while AI watches.

Clawd
Claude Code
  Powered by Claude Code
Claude tests itself Finds its own bugs No pasting errors No manual testing
// your current workflow

The loop that never ends.
Sound familiar?

Every VBA developer using ChatGPT or Claude right now is stuck in the same exhausting cycle. Not because you're doing it wrong — because the tools have no way to close the loop themselves.

STEP 01

Ask AI for code

You get a function. Looks right. Copy it.

STEP 02
📋

Paste into VBA editor

Conflict with an existing variable. Wrong module. Something's already named that. Fix manually.

STEP 03
💥

Run it. Something breaks.

Compile error. Runtime error. Wrong result. Or worse — it runs fine and silently breaks something else.

STEP 04

Paste the error back to AI

Describe what happened. What you expected. What you got. AI can't see your screen. You are the debugger.

STEP 05
♻️

Get a fix. Paste it again.

The fix breaks something that was already working. Regression. Back to step 3.

STEP 06
🐛

Debug.Print. Everywhere.

Add Debug.Print to find where it goes wrong. Check Immediate Window. Clean up later.

↻   repeat until you give up or it accidentally works   ↻
THE RESULT

Half the session spent testing manually. Bugs pile up. Every fix risks breaking something else. Progress is slow. Documentation is whatever you remember to ask for. And you do all of it — AI just watches and suggests.

THE HIDDEN COST

You're a VBA developer. You know Excel inside out. Instead of using that knowledge to make decisions and build things, you spend it copy-pasting and babysitting an AI that could do 90% of this itself.

The VBA IDE was a closed door to AI.
Until now.

Other developers using AI can run code, see the output, and react in a loop. VBA developers couldn't. There's no terminal. No open API. No way for Claude to see what happened inside your workbook.

So Claude gave you one function at a time, and you carried everything else yourself.

VBridge Agent opens that door. VBScript acts as the bridge — native Windows scripting, syntax close enough to VBA, and not blocked by corporate IT the way PowerShell or Python often are.

No installs. No admin rights. No IT exception required.

For the first time, Claude can import code, run it, read the results and fix what broke — without you in the middle. That was always a tooling problem, not a skill problem.

"I've tried AI but it only works for small things."

Because you've been closing the loop yourself. Without a way to test and verify, AI can only do one small step at a time before it needs you back.

"Professional devs look down on VBA."

They had better tooling. Now you can have the same: automated testing, autonomous sessions, crash-safe imports, in Excel. The gap was tooling, not skill.

"I fix one bug and two more appear."

That's regression without a safety net. When Claude runs all checks after every change, it catches what it broke before you ever see it.

"I never have time to write documentation."

Because you're too busy manually testing. When Claude handles the test loop, you get time back and the framework generates docs automatically.

What your workflow looks like
with VBridge Agent

The same Claude that gives you one function at a time becomes something that develops, tests, finds its own bugs, fixes them, and confirms everything passes — autonomously.

✗   YOUR CURRENT WORKFLOW
  • Ask AI for code. Copy it. Paste it. Fix conflicts manually.
  • Run it. Something breaks. You're the one who notices.
  • Copy the error. Describe it to AI. Wait for a fix.
  • The fix breaks something that worked last week.
  • Debug.Print everywhere. Clean up later. Maybe.
  • Every fix risks breaking something else.
  • No tests. No safeguards.
  • Documentation only if you remember to ask separately.
✓   WITH VBRIDGE AGENT
  • You describe what you need. Claude writes it, imports safely, tests automatically.
  • If something breaks, Claude finds it — you don't have to run anything.
  • No pasting errors. Claude reads the test log directly and fixes root causes.
  • Every fix gets a permanent guard — the same bug cannot come back.
  • Full trace logging shows exactly which line got wrong output.
  • Say "full auto" and walk away. Claude tests, fixes, guards, repeats.
  • 45+ automated checks after every change. Regression caught instantly.
  • Documentation generated as part of the session, not an afterthought.

AI that tests its own work.
Every single time.

The framework builds the bridge between Claude and Excel so Claude can see what it produced, verify it works, and fix what it broke — without you in the middle.

01

Automatic write and import

No copy-paste. Claude edits VBA source files directly and imports through a safe bridge — always on a shadow copy, never the live file.

02

Checks run instantly

45+ checks verify output against expected results. A checklist that runs itself every time Claude touches anything. Pass/Fail in seconds — no manual testing.

03

Reads results automatically

No pasting error messages. Claude reads the check log directly, sees exactly which function returned the wrong result, and traces the input to find the real cause.

04

Fix root cause. Add permanent guard.

Not patches. Every fix targets the root cause. A permanent guard check is added so the same error pattern can't recur. No more regression surprises.

05

Autonomous loop until zero issues

Say "full auto" and Claude keeps cycling — test, fix, guard, recheck — until a full scan finds nothing.

VBridge Agent / YourProject/
> full auto - fix all failing checks
Running 45 checks...
✗ ConvertDate returned null for "29/02/2023"
✗ FormatCurrency wrong for negative values
✗ ExportRows skips last row when filtered
─────────────────────────────
Fixing ConvertDate - root cause: leap year not handled
✓ Fix applied · guard check added
Fixing FormatCurrency - root cause: ABS missing on negative
✓ Fix applied · guard check added
Fixing ExportRows - root cause: off-by-one on LastRow
✓ Fix applied · guard check added
─────────────────────────────
Re-running full scan...
✓ 48/48 checks passed · 0 failed
TRUE_SUCCESS - session complete.
You typed one line. Claude found 3 bugs, traced each to its root cause, fixed them, added 3 permanent guards, and confirmed all 48 checks pass. You did nothing except say "full auto."
0 errors you paste manually
0 checks run after every change
faster than manual loop
0 loop iterations while you sleep

Why other options don't
solve the problem for VBA developers

OPTION 1 / MCP EXCEL SERVER

Install hell. And it still can't write VBA.

MCP for Excel requires Python, pip, a running MCP server, Node or uvx depending on the version, and usually a fight with IT policy just to start. Then after all that: it can read and write cells. It cannot write new VBA, cannot run a test loop, cannot see its own output. You are still the one reporting what happened.

30 minutes of setup to end up with the same workflow you started with.

OPTION 2 / CLAUDE ADD-IN FOR EXCEL

It works on spreadsheet data. Your VBA code is invisible to it.

The Claude add-in lives in the Excel ribbon and can read cells, analyze data, write formulas. It has zero access to the VBA editor, the module list, the code behind your workbook, or the output of any macro you run. From the add-in's perspective, your VBA project does not exist.

Useful for cell work. Useless for VBA development.

VBridge Agent vs MCP Excel Server

CAPABILITY VBridge Agent Manual Copy-Paste MCP Excel Server Claude Add-in
🔁 Development Loop
Writes new VBA automaticallyPartial
Auto-imports to VBE✗ Manual
Runs automated checks
Reads its own error log
Autonomous bug fixing (no user)
⚙️ Infrastructure
Works with existing VBE
No server / Python / npm✗ Required✗ Required
Setup in minutes30+ min~10 min
📊 Productivity
Parallel dev (shadow build)
Auto documentation
Full Auto development

Bottom line: MCP is a remote control for spreadsheet data. VBridge Agent is the first tool that puts Claude inside the VBA development loop.

Frequently Asked Questions

I already use ChatGPT and it works fine. Why would I need this?+
ChatGPT gives you code — and you still do everything else: copy, paste into the VBE, run it, see what broke, go back and explain. VBridge Agent lets Claude Code close that loop itself. You describe what to build — it writes, imports, tests and fixes. No copy-paste, no waiting, no explaining errors.
What's the difference between VBridge and the Claude add-in for Excel?+
The Claude add-in for Excel works inside Excel — it can help you draft code in chat, but it cannot import it to the VBE, run checks, read the error log or fix itself. VBridge Agent runs outside Excel via Claude Code CLI — a system capable of managing a complete, autonomous development cycle.
Do I have to work with the black screen (CMD)?+
Not at all. Kivun Terminal gives you a modern, clean terminal with a bright theme — no black screen. It runs Claude Code natively on Windows and macOS without VS Code or any heavy editor.
Do I need to know DOS commands?+
No. Only two commands are ever used:

cd [folder path] — to navigate to your project folder.

claude — to start Claude Code.

After that, everything runs in plain language.
What's the difference between Claude.ai (the website) and Claude Code (the CLI)?+
Claude.ai is a chat — you ask, it answers, but it can't touch your files. Claude Code CLI is Claude with access to your files, commands and scripts — meaning it can take real actions, not just give suggestions. VBridge uses exactly that capability.
How long does setup take?+
If you already have a Claude Pro / Max subscription and Claude Code installed, setup takes about a minute:

1. Download the VBridge.zip file.
2. Extract the ZIP to a regular folder.
3. Start working with any file you put in that folder.

If Claude Code isn't installed yet, setup can be done as part of an Upwork session (additional fee).
Is there Hebrew / RTL support?+
By default, Claude Code does not support Hebrew in the terminal — text comes out reversed and unreadable. I built a solution for this: Kivun Terminal — installs Claude Code with full RTL support in one click, in about 2 minutes. Free, open source, Windows only. ← Kivun Terminal project
What's included in the Upwork session?+
A 120-minute session: installation and setup on your own project, walkthrough of the recommended workflow, and a first working session on a real task — so you leave with a tangible result, not just theoretical understanding.

How to get started?
Choose your installation path.

Prerequisite: A paid Claude Pro or Max subscription.
// choose installation path
🔧 Kivun Terminal
Automatic Claude Code installation in one minute — Windows & macOS
  • Installs Node.js, Git and Claude Code automatically
  • Bright blue terminal theme instead of a black screen
  • Type and receive responses in Hebrew
  • Re-running updates Claude Code to the latest version
  • Live status bar: model, context usage, tokens, cost & session duration
  • Preserves the original Claude Code experience — no unnecessary UI layers
Free Open Source Windows & macOS
01
Download and install Kivun Terminal (one time)
Download and run the installer. Automatically installs: Node.js, Git, Claude Code and a modern terminal theme
02
Copy the VBridge Agent folder to your machine
All scripts are pre-built - nothing to configure
03
Open Kivun Terminal and start working
Open Kivun Terminal from the shortcut. Claude Code launches automatically. First time requires Claude account login
04
Enable VBA Trust in Excel
Options → Trust Center → Trust VBA project access
— or —
⌨️ Manual Installation
For those who prefer full control or already know Claude Code
01
Install Claude Code manually
02
Copy the VBridge Agent folder to your machine
All scripts are pre-built - nothing to configure
03
Open a command window and navigate to the folder
Click the Windows search bar, type cmd and press Enter. Type cd then paste the path
04
Start Claude Code
claude
05
Enable VBA Trust in Excel
Options → Trust Center → Trust VBA project access
Book on Upwork

Work directly with the developer who built this and uses it daily on real Excel projects

  • Full setup for your workbook, first autonomous session running same day
  • Claude connected to your existing code + automated checks running
  • Guard checks added to existing procedures — no rewrites
  • Shadow build setup for parallel project development
  • VBA development sessions with VBridge Agent running live
Top Rated • Upwork
Book a session now →

upwork.com/freelancers/~017d992908340102a8