Playbooks · Coding
AIWG 2026.11.4: save an approval once
Written November 11, 2026
AIWG 2026.11.4 lets you confirm an approval once for a bounded job, instead of approving the same work every time it comes up.
The problem
An assistant that asks for approval on the same bounded work every time trains its user to click approve without reading. That defeats the approval: the check becomes a reflex instead of a decision.
What saved approvals are
AIWG 2026.11.4 adds saved approvals you confirm once for a specific scope: the actions, the files, the project, and the environment. In an MCP client that supports confirmation forms, ask your assistant to propose a saved approval, then review the scope, duration, and any use limit in the form before confirming 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 the client cannot show the confirmation form, it cannot save a grant from an ordinary chat reply.
You can ask your assistant to list saved approvals, explain why one applies, or revoke one. Revocation takes effect at the next check. For direct inspection, use:
aiwg config authorization list --active
A saved approval is scoped, not blanket. It covers the work you named, and nothing else.
Windows fixes
Four fixes from community contributor @GoryGrey address Windows setup problems. Agent files with Windows line endings now deploy correctly, and those line endings no longer cause core rules to exceed their size checks. Temporary deployment references and worker locks use Windows junctions without requiring symlink privileges. Update AIWG and ask your assistant to refresh the project. The fixes need no new configuration, and they help when a checkout uses CRLF line endings or your Windows account cannot create symbolic links.
Grok Build support preview
Grok Build, xAI's coding-agent CLI, now has expanded headless-output support and session import through its public CLI. AIWG can list, search, and export sessions, then import the exported conversation. CLI exports omit tool output, and AIWG records that limitation. This remains an experimental preview based on Linux 1.0.77 captures. Windows PowerShell and WSL checks and several native session features remain deferred, including compaction, resumed-session relationships, and subagents.
Setup and discovery
The same release improves setup and discovery in Codex, Copilot, and Hermes. Codex discovery avoids the stdin-pipe stalls seen in its sandbox and fails promptly if temporary storage is unavailable. Copilot's rule paths now match its native instructions folder, while Hermes offers an optional hook for task suggestions. Shared setup checks continue to cover OpenCode alongside these tools.
Limits
- A saved approval covers one scope. Anything outside it still needs a review, and the risky categories keep theirs no matter what is saved.
- Grok Build support is a preview, not a release. It is built from Linux captures, with Windows checks deferred.
- After updating, ask your assistant to refresh AIWG, and review folder and hook trust in Codex when prompted, including after managed hook scripts change.
Related playbooks
- AIWG 2026.11.5: worker addons get scoped
- ReSharper 2026.3 brings Claude and Codex in
- Visual Studio 2026 runs on the Copilot SDK
- Add tests to an untested module with an agent
Sources
Back to: Coding playbooks hub · Copilot CLI now configures MSBuild itself · VS Code 1.146 retires the Local harness