Lets Claude Code (or any local tool) edit IBM i source members by pulling them to a local temp file and pushing them back when you're done.
- VS Code
- Code for IBM i extension installed and connected to IBM i
- Get the
.vsixfile from Releases - Open VS Code
- Open the Extensions panel (
Ctrl+Shift+X) - Click the
...menu (top-right of the Extensions panel) - Choose Install from VSIX...
- Select
ibmi-member-bridge-0.0.1.vsix - Reload VS Code when prompted
Use Code for IBM i to browse to a source member and open it as you normally would. It opens in VS Code with a member:// URI.
Open the Command Palette (Ctrl+Shift+P) and run:
IBM i: Pull Member to Local
A new editor tab opens with the member content saved locally at:
C:\Temp\ibmi-members\LIBRARY_FILE_MEMBER.EXT
The status bar (bottom-left) will show the member name — e.g. ⊙ AYDEN/QCLSRC/MSGWMON.
Edit the local file however you like — including asking Claude Code to make changes.
When you're happy with the changes, open the Command Palette and run:
IBM i: Push to IBM i
Or just click the member name in the status bar. Changes are written back to the source member on IBM i.
By default, temp files are saved to C:\Temp\ibmi-members\. To change the location:
- Go to File → Preferences → Settings
- Search for
ibmi-bridge - Update Temp Dir to your preferred path
| Error | Fix |
|---|---|
| "Open an IBM i source member first" | The active editor must be a member opened via Code for IBM i |
| "No active IBM i connection" | Connect to IBM i in the Code for IBM i panel first |
| "This file is not a tracked IBM i member" | Run Pull first — Push only works on files that were pulled this session |
| "Push failed — member may be locked" | Check if the member is locked by another job on IBM i |
Note: The member tracking resets when VS Code is reloaded. If you reload and need to push, just Pull again first (it will overwrite the same temp file) and then Push.