Disabling Features

Weave lets you selectively disable agents, hooks, and skills via top-level disable statements in your .weave config.

Disable Syntax

disable agents ["warp", "spindle"]
disable hooks ["context-window-monitor"]
disable skills ["tdd"]

Each statement takes an array of string identifiers. Entries from your user config and project config are unioned. If your user config disables context-window-monitor and your project config disables warp, both are disabled.

Disabling Agents

Remove agents you don't need from the system entirely:

disable agents ["warp", "spindle"]

Alternatively, you can disable an agent via its per-agent config block:

agent warp {
  # disabled by omitting it from active config
  # or use: disable agents ["warp"] at the top level
}

The disable agents top-level statement is the recommended approach.

Disabling Hooks

Weave's governance hooks run automatically during agent execution. You can disable individual hooks if they interfere with your workflow:

disable hooks ["context-window-monitor", "verification-reminder"]

Available Hooks

Hook	Purpose
start-work	Parses plan files and switches to Tapestry when /start-work is called
work-continuation	Handles work resumption signals: idle work nudges and post-compaction work recovery
workflow	Handles workflow start, workflow commands, and workflow continuation behavior
todo-continuation-enforcer	Finalizes leftover in_progress todos automatically, or prompts as a fallback if enabled
compaction-todo-preserver	Preserves and restores todo state across compaction
pattern-md-only	Blocks Pattern from writing non-.md files (plan discipline enforcement)
context-window-monitor	Warns when context window usage is high
write-guard	Validates write targets before file operations
rules-injector	Loads AGENTS.md and .rules files into agent context
keyword-detector	Detects specific keywords in messages and triggers actions
verification-reminder	Prompts agents to run verification steps before completing
analytics	Tracks session activity (tool usage, delegations) and generates project fingerprints

INFO

Hook names use kebab-case. For example, use context-window-monitor in your disable hooks array, not contextWindowMonitor.

Continuation-related hooks

Preview

The newer continuation config surface and its interaction with recovery/idle behavior are currently in preview.

Continuation behavior is split across several controls.

• Disable work-continuation to turn off both idle work nudges and post-compaction work recovery
• Disable workflow to turn off workflow continuation behavior entirely
• Disable todo-continuation-enforcer to stop automatic todo cleanup
• Disable compaction-todo-preserver to stop preserving todo state across compaction

If you want to tune continuation behavior without disabling a feature entirely, use the continuation config block instead of disable hooks.

continuation {
  recovery {
    compaction true
  }
  idle {
    enabled false
    work false
    workflow false
    todo_prompt false
  }
}

See Execution & Continuation for the full behavior model.

Common Disables

context-window-monitor is the most commonly disabled hook. It produces informational noise during long sessions. verification-reminder is useful to disable when you're doing rapid exploratory work and don't want the extra checkpoint prompts. analytics can be disabled if you don't want session tracking or project fingerprinting (see Analytics).

Disabling Skills

Exclude specific skills from being loaded, even if they exist in the skill path:

disable skills ["tdd", "some-inherited-skill"]

This is useful when you have inherited skills from a shared skill library (for example, a monorepo) and want to opt out of specific ones for a particular project.