2.9.26
Released 2 Nov 2026
Official WindowSpan website
WoW addons written and fixed by an AI agent
WindowSpan 2.9.26 reads your Lua, TOC and XML files, proposes fixes for what a patch broke and shows every change as a diff. You reload the interface in the game and test the result yourself.
My addon is flagged out of date after the patch, so update the Interface number in its TOC file.
- glob
*\*.toc1 match - read_file
MyAddon\MyAddon.toc8 lines - grep
Interface1 match - edit_file
MyAddon\MyAddon.toc+1 -1 - Shell
type MyAddon\MyAddon.tocexit 0
waiting for your OK before the next stepRejectAccept
About 34 MB
Installer, no account needed
Windows 10/11
Runs on 64-bit (x64) PCs
13
Interface languages of the app
Ask first
Pauses before actions that change something
Cloud or local
Plus a built-in model
Write and fix wow addons with an AI agent
WoW addons are small packages of Lua 5.1 code and optional XML files that add frames, bars and tooltips to the game's interface, and WindowSpan 2.9.26 helps you write and repair them on your own PC. Names must match. Each addon sits in its own folder, and the .toc file inside carries the same name and lists every file in load order.
Update wow classic addons after a patch
Open the addon folder of your Classic game version in the chat, and the agent runs glob to find every .toc file and read_file to open the one you name. It reads the Interface line. The game often flags an addon as out of date until that number matches the game version, so edit_file changes the line and shows a diff with the old and the new value, which is 1 changed line. Read it first. You accept the diff in Ask first mode, type /reload in the game, and check that the addon loads without an error.
Tool trace
glob *\*.toc → 1 match
read_file MyAddon\MyAddon.toc → 8 lines
edit_file MyAddon\MyAddon.toc → +1 -1Create your own wow ui addons
Ask for a new addon called HelloFrame and the agent creates the folder with make_dir, then writes the .toc file and a small Lua file with write_file. The Lua file calls CreateFrame, registers PLAYER_LOGIN and prints one line in the chat window. Plan only comes first. In that mode the agent lists the 3 steps it would take and runs nothing, so you read the plan before you switch to Ask first, accept each diff and use /console scriptErrors 1 to make the game show any Lua error.
Tool trace
make_dir HelloFrame → ok
write_file HelloFrame\HelloFrame.toc → saved
write_file HelloFrame\HelloFrame.lua → savedDebug a Lua error from the game
If your combat text addon is not working after a patch, paste the error text from the game into the chat. The agent runs grep to find the event handler named in the message and read_file to show the 10 lines around it, and it can open a SavedVariables file when the saved data looks wrong. Then edit_file proposes a fix. You read the diff, accept it, type /reload and see whether the error is gone. If it is not, the next card shows what changed.
Check wow macros before you paste them
Keep your draft macros in a text file inside the working folder, and the agent reads it with read_file and flags any macro that looks longer than the 255 character limit. Macros are not addons. If one is too long, edit_file shortens the text and shows the diff, and you paste the result into the game's macro window yourself and confirm the length there, because the agent never runs inside the game. Nothing runs in the game. Plan only lists the proposed changes without touching the file.
How WindowSpan differs from a typical chat assistant
Typical assistants stop at advice. WindowSpan 2.9.26 runs the tools itself, and each action appears in the chat as a card with its real result, such as the command output or the file diff.
| Typical chat assistant | WindowSpan | |
|---|---|---|
| Files | Shows code in the chat for you to copy | Reads, edits and writes files in the working folder |
| Commands | Describes what a command might print | Runs it and reports the real exit code |
| Errors | Works only from the text you paste | Searches the code and reads the file the error names |
| Approval | Changes happen when you copy them | Ask first pauses before actions that change something |
How to start with WindowSpan
- Download the setup program, about 34 MB, and compare its SHA-256 checksum with the published manifest.
- Run the setup on Windows 10 or 11, then open WindowSpan. No account is needed.
- Connect a model: a cloud provider endpoint, a model on your PC or the built-in model.
- Choose your addon folder as the working folder and describe the change you want.
Who it is for
Addon authors who already write Lua are the first group, and they hand the agent routine jobs such as raising the Interface number after a patch or tracing an error. Review each diff. Anyone hunting for the best wow addons should know that WindowSpan does not rank addons; it writes and repairs the ones you own.
Beginners with a first project are the second group. They describe an idea in plain words and learn how a .toc file, a Lua file and a reload fit together. A player who wants an addon to show an alert when a rare beast appears can start that way. Start small. The agent drafts the event code and you check the result in the game.
Authors who maintain several addons are the third group. The task tool runs parallel sub-agents on separate files, which suits 2 or more addon folders at once. Keep each diff small. Someone adding guild crafter info to the crafting order window as an addon can let the agent read the API documentation before it writes code.
Frequently asked questions
What are wow addons?
Addons are small packages of Lua code and optional XML files that change or add parts of the game's interface, such as frames, bars, tooltips, chat windows and action bars. Each addon has one folder. The .toc file inside it lists the files in load order, and the game runs Lua 5.1.
Is ppfwebdevelopers.com the official WindowSpan website?
Yes, ppfwebdevelopers.com is the official WindowSpan website. The installer here is the original build and is not code-signed yet, so compare its SHA-256 checksum with the published manifest before you run it. Check first. Questions go through the Send feedback button inside the app.
Does the agent run inside the game?
No. WindowSpan edits the files of your addon on your PC and never runs inside the game, so you load each change yourself with /reload. Addons cannot cast spells, target or move your character, and WindowSpan does not help get around that limit of the game.
Do my files leave the PC?
Yes, if you use a cloud model, because the prompt, including the text of any file the agent reads, goes to that provider. With a local model on your PC nothing leaves the machine. WindowSpan sends no telemetry.
Does WindowSpan work with wow classic addons?
Yes. Each Classic version has its own version folder, so you choose that folder as the working folder and the agent reads and edits the addon files inside it. Match the numbers. Check the Interface number in the .toc file against your game version before you test.
Can the agent play the game for me?
No. WindowSpan is for interface and information addons only, so it does not write anything that plays for you, makes combat decisions or goes around the limits Blizzard Entertainment puts on addons in combat. Your addon shows information. You stay the one who plays.
What is the current version of WindowSpan?
The current version is 2.9.26, released on 2 Nov 2026. Updates are published automatically. The setup program is about 34 MB, and the app shows an Update button when a new version is ready.
Open your addon folder with an agent
Download WindowSpan 2.9.26 for Windows 10 or 11, open your addon folder as the working folder and review the first diff, which shows exactly what the agent changed. No account needed.
Download WindowSpan for Windows ↗Explore more on this site
Every page of this website is available in 20 languages.
What the agent can do in an addon folder ↗ Connect a cloud, local or built-in model ↗ Step-by-step addon guide ↗ Download and verify the setup ↗ Answers to common questions ↗ What data is processed ↗
