v2026.11.5 — Keep Your Project Rules and Use More Worker Tools

Single-addon deployments preserve other bundles' rules, Factory BYOK and Copilot workers receive fixes, Grok gains worker discovery and native agents, and project-local skills load correctly.

AIWG 2026.11.5 - Keep your project rules and use more worker tools

AIWG 2026.11.5 keeps other bundles' rules in place when you deploy a single addon. It also fixes worker setup and task delivery for Factory Droid, Copilot CLI and Grok Build, giving you more ways to work with the tools and provider keys you already use.

Add one bundle without losing the others

Deploying one addon could remove rules installed by another bundle, including two safety rules for hardware work and interactive operations. AIWG now limits that deployment's cleanup to the selected addon's own files. Your other bundles' rules and deployment records stay in place.

Project-local addons also have a consistent manifest format, with useful validation errors when something needs fixing. Their skills now land in the folders your tool actually loads, including `.claude/skills/` for Claude Code. Ask your assistant to refresh your project-local addon after updating so its skills are available in your next session.

Run workers with your own provider key

Factory Droid's BYOK path now connects custom-model discovery, worker setup and task execution. AIWG reads the registered model's context limit and builds the exact selector Droid expects. For a custom model, ask your assistant to check its input context limit and configure the worker role for models without selectable reasoning effort.

The steward now explains BYOK settings for Hermes, OpenCode, Factory and Copilot. You can ask:

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

The guidance explains how to supply the key securely and check which provider and model actually ran. Codex and Muse routes remain unverified. See the provider guide for the available routes.

Copilot CLI 1.0.106 workers now receive the full task brief through stdin and return their final answer correctly. Existing worker setup checks still apply; update AIWG before asking your assistant to dispatch tasks through that CLI version.

Use Grok workers in AIWG projects

Grok Build workers can now complete their required AIWG discovery step without stopping for an approval that headless mode cannot provide. Worker commands also block Grok's workflow tool from creating extra workers.

AIWG agents now deploy to Grok's native project agent folder. Grok ignores model settings in agent files, so the worker command selects the model. Ask your assistant to refresh AIWG for Grok Build, then open a new session. The Grok Build quickstart explains setup.

Experimental session import also preserves captured resume, fork and compaction information, including interactive compaction checkpoints. Live Grok features beyond these supported paths remain experimental, with attachment and other uncaptured behavior still deferred.

Find the right help and see pending hook approval

Discovery requests containing a slash now search as ordinary text, and agent results show their declared names. In Hermes, setup and health checks explain when task suggestions are waiting for your hook acceptance. Review that request in Hermes; changed hook scripts need acceptance again.

If you are upgrading

  • Ask your assistant to refresh AIWG after updating, including any project-local addons.
  • For Factory BYOK workers, have it check the custom model's context limit and role settings.
  • In Hermes, review pending hook acceptance before expecting task suggestions.

See the CHANGELOG entry and hook guide for details.