v2026.11.4 — Save Approvals and Work Across More AI Tools
Saved approvals with confirmed scopes, Windows fixes from @GoryGrey, a Grok Build preview, and more reliable AI tool setup and discovery.
AIWG 2026.11.4 - Save approvals and work across more AI tools
AIWG 2026.11.4 adds saved approvals you confirm once for a specific scope, Windows fixes from community contributor @GoryGrey, and a Grok Build support preview. It also improves setup and discovery in the AI tools you already use, including Codex, Copilot and Hermes.
Confirm an approval once for work you repeat
When your assistant keeps asking about the same bounded work, you can now save an authorization grant: an approval for specific actions, files, a project and an environment. In an MCP client that supports confirmation forms, ask your assistant to propose a saved approval. Review the scope, duration and any use limit in the form before confirming it.
Supported workflows check that saved approval before asking again. 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`. The approval reference covers the available commands.
Use Windows checkouts without line-ending failures
Four fixes contributed by @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. These fixes need no new configuration. They help when a checkout uses CRLF line endings or your Windows account cannot create symbolic links.
Try the Grok Build 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; AIWG records that limitation.
Start with the Grok Build quickstart. Ask your assistant to preview connecting AIWG to Grok Build in your project. Review the project before granting folder trust in Grok Build, then open a new session after setup.
This remains an experimental preview based on Linux 1.0.77 captures. Windows PowerShell/WSL checks and several native session features remain deferred, including compaction, resumed-session relationships and subagents. Grok Bot and Grok web Build are separate products.
Get more reliable setup and task discovery
Codex discovery avoids the stdin-pipe stalls seen in its sandbox and fails promptly if temporary storage is unavailable. Setup guidance explains the folder and hook trust Codex requires. 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.
If you are upgrading
- Ask your assistant to refresh AIWG after updating.
- In Codex, review folder and hook trust when prompted, including after managed hook scripts change.
- For Hermes task suggestions, ask your assistant to enable the optional cross-provider hooks and review the command consent in Hermes.
See the CHANGELOG entry and hook guide for details.