← All build notes

November 11, 2026 · 4 min read

AIWG 2026.11.4 and 2026.11.5: saved approvals, Windows fixes from the community, and more worker tools

Two AIWG releases let you confirm an approval once for work you repeat, bring four Windows fixes from a community contributor, keep other bundles' rules in...

AIWG shipped two more releases this week. 2026.11.4 lets you save an approval for bounded work you repeat, brings four Windows fixes from a community contributor, and adds a Grok Build preview. 2026.11.5 stops a single-addon deploy from removing other bundles' rules, and extends worker support for Factory Droid with your own provider key, Copilot CLI and Grok Build.

Confirm an approval once for work you repeat

When your assistant keeps asking about the same bounded work, you can save an authorization grant: an approval for specific actions, files, a project and an environment. In an MCP client that supports confirmation forms, ask:

Propose a saved approval for running the test suite and editing files under docs/ in this project for the next week.

Review the scope, duration and any use limit in the form before you confirm it. Supported workflows check the saved approval before asking again, and a request outside its scope still needs review. Secret access, destructive changes, production actions and changes that override policy keep their review requirements. If your client cannot show the confirmation form, a grant cannot be saved from an ordinary chat reply.

You can ask your assistant to list saved approvals, explain why one applied, or revoke one; revocation takes effect at the next check. To inspect them yourself, run aiwg config authorization list --active. The approval reference lists the commands.

Windows fixes from the community

Last week a user in our Telegram group reported symlink errors on Windows. We had no Windows machine to test on, so we asked for pull requests. They sent four, each with regression tests and notes on what they could not test, and all four shipped in 2026.11.4. Thank you, @GoryGrey.

Agent files with Windows line endings now deploy correctly, and those line endings no longer push core rules over their size checks. Temporary deployment references and worker locks use Windows junctions, so they work without symlink privileges. Update AIWG and ask your assistant to refresh the project; no new configuration is needed. The updater hang they also reported is still open.

Add one addon without losing the others

Deploying a single addon could remove rules installed by another bundle, including two safety rules for hardware work and interactive operations. In 2026.11.5 that deployment only cleans up the selected addon's own files, so your other bundles' rules and deployment records stay in place.

Project-local addons also have a consistent manifest format, with validation errors that say what to fix, and their skills now land in the folders your tool actually loads, such as .claude/skills/ for Claude Code. Refresh your project-local addons after updating so their skills are there in your next session.

More worker tools and your own provider keys

Factory Droid's bring-your-own-key path now runs from custom-model discovery through worker setup to task execution. AIWG reads the registered model's context limit and builds the exact model selector Droid expects. The steward explains key settings for Hermes, OpenCode, Factory and Copilot, so you can ask:

Use my OpenRouter key with Factory Droid. Show me the model settings and resolved worker command before running a paid task.

It explains how to supply the key securely and how to check which provider and model actually ran. Codex and Muse routes remain unverified; the provider guide lists what is available.

Copilot CLI 1.0.106 workers now receive the full task brief and return their final answer correctly. Grok Build workers can complete their required discovery step without stopping for an approval that headless mode cannot provide, and their commands block Grok's workflow tool from starting extra workers. AIWG agents now deploy to Grok's own project agent folder; Grok ignores model settings in agent files, so the worker command chooses the model.

The Grok Build preview

2026.11.4 adds a preview of Grok Build, xAI's coding-agent CLI: expanded headless output, and listing, searching, exporting and importing sessions through its public CLI. CLI exports omit tool output, and AIWG records that limitation. 2026.11.5 keeps resume, fork and compaction information when importing sessions. The preview is experimental and based on Linux 1.0.77 captures; Windows checks and several native session features remain deferred. Start with the Grok Build quickstart.

Smaller fixes

  • Codex discovery no longer stalls on stdin pipes in its sandbox, and fails promptly if temporary storage is unavailable.
  • Copilot's rule paths match its native instructions folder, and Hermes has an optional hook for task suggestions; setup and health checks say when that hook is waiting for your acceptance.
  • Discovery requests that contain a slash search as ordinary text, and agent results show their declared names.

Upgrading

npm install -g [email protected]

Then ask your assistant to refresh AIWG in each project, including any project-local addons, or run aiwg refresh. In Codex, review folder and hook trust when prompted, including after managed hook scripts change. In Hermes, review pending hook acceptance before expecting task suggestions.

The release discussions are open on GitHub for 2026.11.4 and 2026.11.5, and the changelog has every change.