You describe what to build.
Claude Code builds, tests and fixes.
VBridge Agent is a framework that puts Claude Code inside the Excel VBA editor (VBE). You describe what to build; Claude writes the VBA, imports it, runs 45+ automated checks, reads the error log, and fixes root causes autonomously, with no copy-paste. It runs 100% locally on Windows.
VBridge lets Claude Code close the loop itself: writes, imports to the VBE, tests and fixes. You describe, it works.
Stop doing AI's job. You paste, you fix conflicts, you test, you paste the error back. This is you doing all the work while AI watches.
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.
Ask AI for code
You get a function. Looks right. Copy it.
Paste into VBA editor
Conflict with an existing variable. Wrong module. Something's already named that. Fix manually.
Run it. Something breaks.
Compile error. Runtime error. Wrong result. Or worse, it runs fine and silently breaks something else.
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.
Get a fix. Paste it again.
The fix breaks something that was already working. Regression. Back to step 3.
Debug.Print. Everywhere.
Add Debug.Print to find where it goes wrong. Check Immediate Window. Clean up later.
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.
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.
Start by just asking. Nothing changes.
You don't have to let it touch anything to get value on minute one. Point VBridge at the workbook you already have open and ask about it, live. It reads the file and answers on the spot.
"What's in Dashboard!B5 right now?"
The value, the formula behind it, and its number format, straight back.
"Which modules and forms does this workbook have?"
The full component list with types, so Claude knows the lay of the land before it writes a line.
"Where does 'Invoice' appear on this sheet?"
A live search across values or formulas, answered on the spot.
It only reads. It never writes. That guarantee is the whole point: explore your file with zero risk, and move to the build-and-fix loop only when you're ready.
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.
- 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.
- 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.
In one sentence: Claude updates the VBA code right inside the editor, runs the code that lives there, reads the logs and errors, and iterates, with no intervention needed from you, until everything passes.
Your workbook is never at risk
Every session starts from a saved recovery point. A timestamped backup is taken before any change, so one click puts you back exactly where you started, no matter what happens during the session.
Automatic write and import
No copy-paste. Claude edits VBA source files directly and imports through a safe bridge, fully automatic, with no manual VBE work.
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.
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.
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.
Autonomous loop until zero issues
Say "full auto" and Claude keeps cycling, test, fix, guard, recheck, until a full scan finds nothing.
Safe. Unattended. Verified.
Everything above runs without putting your file, your time, or your afternoon at risk. Here is what that means in practice.
It never corrupts your code
Every module keeps its exact type and content through the whole automated loop. A class stays a class, a form stays a form, every line and character preserved, Hebrew comments and special symbols included. This is proven by an automatic test on every build, not just promised.
Your file is never at risk
Every change is verified before it's applied, and a timestamped backup of your workbook is taken first. A change that doesn't pass is never applied, and anything that is applied stays recoverable from the backup. No "hopefully it saved correctly" step, no cleanup you have to do yourself. You can leave it running and walk away.
Works with the workbook you already have
Point VBridge at your existing workbook and start. No new API to learn, no wrapper functions to add, no refactor before you get value. Your code stays your code. Most tools ask you to rewrite first and automate second. VBridge automates the project you have today.
It tells you exactly where it broke
When something fails, you get the exact location, module, procedure and line, on the first failure. No bare error code, no guessing game, no re-running in a special debug mode. That's the difference between a fix that takes one cycle and a fix that takes six.
It fails before it wastes your time
The errors that normally kill a run in the first thirty seconds are caught up front, reported in plain language, and fixed before anything starts. A run that begins is a run that will finish.
Dialogs don't stop the run
Message boxes, prompts and file pickers are the reason unattended VBA usually isn't unattended. With VBridge you decide what every prompt should answer before the run starts, and you can run the same flow twice with opposite answers to prove both paths work. Most projects have branches nobody has tested in years. This is how you find them.
You know what will be covered before you start
Before a run begins, you see exactly which parts of your project will be exercised and which won't, and why. No ten-minute run that ends in a report full of "skipped".
Excel never gets left wedged
If something stalls, VBridge notices, stops it, and leaves your machine clean. Your own Excel session, the workbooks you have open and unsaved, is never touched. There's no task-manager cleanup ritual afterwards.
Built for the agent, not just the human
Every result comes back in a form the AI can act on directly: what happened, where in the process, and what to do next. Fewer wasted cycles, less token spend on the agent re-reading logs, and faster convergence on a working fix.
Why other options don't solve the problem for VBA developers
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.
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.
Feature Comparison
| CAPABILITY | VBridge Agent | Manual Copy-Paste | Claude Add-in | MCP Excel Server |
|---|---|---|---|---|
| 🔁 Development Loop | ||||
| Writes new VBA automatically | ✓ | ✓ | Partial | ✗ |
| Auto-imports to VBE | ✓ | ✗ Manual | ✗ | ✗ |
| Runs automated checks | ✓ | ✗ | ✗ | ✗ |
| Reads its own error log | ✓ | ✗ | ✗ | ✗ |
| Autonomous bug fixing (no user) | ✓ | ✗ | ✗ | ✗ |
| Reads the open workbook live, read-only | ✓ | ✗ | Cells only | Cells only |
| ⚙️ Infrastructure | ||||
| Works with existing VBE | ✓ | ✓ | ✗ | ✗ |
| No server / Python / npm | ✓ | ✓ | ✓ | ✗ Required |
| Setup in minutes | ✓ | ✓ | ~10 min | 30+ min |
| 📊 Productivity | ||||
| Parallel project development | ✓ | ✗ | ✗ | ✗ |
| Auto documentation | ✓ | ✗ | ✗ | ✗ |
| Full Auto development | ✓ | ✗ | ✗ | ✗ |
| 🛡️ Safety & Unattended Runs | ||||
| Verified and backed up before every change | ✓ | ✗ | ✗ | ✗ |
| Code type preserved on import (class stays class) | ✓ | ✗ | ✗ | ✗ |
| Exact failure location (module, procedure, line) | ✓ | ✗ Error code | ✗ | ✗ |
| Runs containing prompts complete unattended | ✓ | ✗ | ✗ | ✗ |
| Coverage known before the run | ✓ | ✗ | ✗ | ✗ |
| Automatic hang recovery | ✓ | ✗ Manual | ✗ | ✗ |
| Machine-readable results (JSON) | ✓ | ✗ | ✗ | Partial |
Bottom line: Other AI tools touch the spreadsheet from the outside, reading data, writing formulas, filling cells. VBridge Agent is the only one that puts Claude inside the VBA editor itself, to write code, run it, and fix what breaks on its own.
What people say about VBridge
You're putting me out of business.
It's a genius framework.
I'm already having fun with it. This framework will save me a lot of work.
Watch: VBridge Agent in action
A talk by Noam Brand at the Excelists Club, using Claude Code as an AI agent that works for you in Excel: it reads your files, writes, tests and runs code end to end. The video starts directly at the VBridge segment (34:30).
How to get started? Choose your installation path.
Affiliate disclosure: this is a referral link. If you later purchase a subscription, I receive $10 in Claude usage credits, at no extra cost to you.
- Installs Node.js, Git and Claude Code automatically
- Bright blue terminal theme, no black screen
- Visual folder picker, no
cdcommands - Re-running updates Claude Code to the latest version
- Live status bar: model, context, tokens, cost & duration
- Preserves the original Claude Code experience, no extra UI layers
- Installs Node.js, Git and Claude Code automatically
- Full BiDi rendering: Hebrew, Arabic, Persian, Urdu & 8+ more
- Hebrew text aligns right; mixed English/Hebrew positioned correctly
- Bright blue terminal theme, no black screen
- Live status bar: model, context, tokens, cost & duration
- Re-running updates Claude Code to the latest version
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
- ✓Set up for parallel project development
- ✓VBA development sessions with VBridge Agent running live
Not a developer, or you would rather not touch VBA at all? There is a guided option where the Excel work gets done with you, on your own files: Claude Code for Excel →
Frequently Asked Questions
What is VBridge Agent?
I already use ChatGPT and it works fine. Why would I need this?
What's the difference between VBridge and the Claude add-in for Excel?
Do I have to work with the black screen (CMD)?
Do I need to know DOS commands?
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)?
How long does setup take?
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?
What's included in the Upwork session?
Want to talk before you start?
Leave your details and I'll get back to you. No spam, no mailing list, just an answer to what you asked.
- 1You write what you'd like to build or automate in Excel.
- 2I reply with a short feasibility take, no commitment.
- 3If it's a fit, we book a first training session on Upwork.