Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

AIWG 2026.11.5: worker addons get scoped

Written November 12, 2026

Installing one addon should never delete the rules another addon put down. AIWG 2026.11.5, released November 11, limits each deployment's cleanup to its own files, and gives Factory, Copilot and Grok workers a better path in.

The scoping fix

The headline change in AIWG 2026.11.5 is about what an addon deployment is allowed to remove. Before this release, deploying one addon could remove rules installed by another bundle, including two safety rules for hardware work and interactive operations. The deployment now limits its cleanup to the selected addon's own files. Other bundles' rules and deployment records stay in place. For anyone who stacks addons, that turns an install from a risk to your existing setup into a contained change.

Project-local addons change with it. They now have a consistent manifest format, with validation errors that say what needs fixing, and their skills land in the folders each tool actually loads, including .claude/skills/ for Claude Code. After updating, ask your assistant to refresh your project-local addon so its skills are available in your next session.

Factory Droid workers with your own key

Factory Droid's bring-your-own-key path now connects custom-model discovery, worker setup and task execution in one flow. AIWG reads the registered model's context limit and builds the exact selector Droid expects. For a custom model, the release notes advise checking its input context limit and configuring the worker role for models without selectable reasoning effort. The steward also now explains bring-your-own-key settings for Hermes, OpenCode, Factory and Copilot, including how to supply a key and how to see which provider and model actually ran. Codex and Muse sit outside the routes that guidance covers.

Copilot CLI and Grok Build workers

Copilot CLI 1.0.106 workers now receive the full task brief through stdin and return their final answer correctly. The existing worker setup checks still apply, and the notes say to update AIWG before dispatching tasks through that CLI version.

Grok Build workers can now finish 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 deploy to Grok's native project agent folder, and because Grok ignores model settings in agent files, the worker command selects the model instead. 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 behaviour still deferred.

Smaller fixes

If you are upgrading

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: AIWG 2026.11.4: save an approval once