Capability Toggle Scopes
Rules, workflows, skills, subagents, and MCP servers can each be turned on or off. Where that choice is saved depends on whether a task is open.
Where a toggle is saved
Section titled “Where a toggle is saved”The capabilities panel and the MCP servers popup show the current storage layer in a line under their tabs:
| Situation | Notice | Effect |
|---|---|---|
| No task is open (start screen) | Toggles saved for this workspace | Applies to new tasks started in this workspace |
| A task is open | Toggles saved for this task only | Applies only to the open task; other tasks and the workspace default are untouched |
Global preferences sit underneath both and apply across every workspace.
How scopes combine
Section titled “How scopes combine”The effective state is resolved from the strongest scope that has an entry:
task override → workspace override → global override → resource defaultA resource with no entry in a scope inherits from the next one; it is not treated as disabled. So a task only records the toggles you actually changed in it, and everything else keeps following the workspace and global settings.
Effect on a running task
Section titled “Effect on a running task”A task freezes its system prompt and tool list when it starts. Changing a toggle in the middle of a task does not silently rewrite that snapshot: the Refresh Prompt Cache button in the task header shows a warning icon and lists what changed, for example Rules changed or MCP tools changed. Select it and confirm to rebuild the prompt with the new toggles. Refreshing causes one prompt-cache miss.
