Wizards errors

Failures in Attune AI's XML-enhanced wizard system, which provides guided multi-step workflows for development tasks like debugging, refactoring, and security audits.

Common error signatures

Where errors originate

Wizard errors typically start at these key entry points:

How to diagnose

  1. Check the wizard ID and registration status. Use list_wizards() to verify the wizard exists and get_wizard(wizard_id) returns a valid class. Missing wizards return None rather than raising exceptions.

  2. Examine custom wizard YAML structure. If save_custom_wizard() fails, validate that your wizard definition matches the expected schema with required fields like wizard_id, name, description, and properly formatted steps.

  3. Review step conditions and context. When BaseWizard.run() fails mid-execution, check that step conditions (WizardStep.condition) evaluate correctly and that build_prompt_context() can access all required data from the wizard session.

  4. Validate filesystem permissions. Custom wizard save/delete operations require write access to the wizard definitions directory. Permission errors manifest as ValueError with "Cannot write wizard YAML" messages.

  5. Check built-in wizard constraints. Attempts to modify built-in wizards (DebugWizard, RefactorWizard, ReleasePrepWizard, SecurityWizard, TestGenWizard) will fail with explicit error messages about protected wizard IDs.

Source files

Tags: wizards, interactive