Bump to v2.10.39: Allow YAML files with Home Assistant custom tags in ha_write_file (reported by @ghzgod)

Author: Coolver

CHANGELOG.md

@@ -2,6 +2,15 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.10.39] - 2026-02-18
+
+### 🔧 Allow YAML files with Home Assistant custom tags in `ha_write_file` (reported by @ghzgod)
+
+- **Issue**: The file write endpoint rejected valid YAML that uses HA custom tags such as `!include`, `!include_dir_merge_named`, etc., with an error like: *"Invalid YAML in configuration.yaml: could not determine a constructor for the tag '!include'"*. Users had to fall back to SSH to edit `configuration.yaml` and other files that rely on these directives.
+- **Cause**: Validation used `yaml.safe_load()`, which only supports standard YAML types and does not handle custom tags. Home Assistant uses `!include` and related tags throughout configs, so such files were incorrectly treated as invalid.
+- **Fix**: Introduced a custom SafeLoader that treats unknown `!…` tags as opaque placeholders during validation. The document is only checked for parseability; includes are not resolved. File content is written as-is. Both `write` and `append` now accept YAML containing `!include`, `!include_dir_merge_named`, and other HA tags.
+- **Thanks**: Bug reported by [@ghzgod](https://github.com/ghzgod). Thank you for the clear description and steps to reproduce.
+
 ## [2.10.38] - 2026-02-18
 
 ### 🔧 Accept plural automation fields (thanks to @CrazyCoder, PR #26)

README.md

@@ -1,6 +1,6 @@
 # HA Vibecode Agent - Home Assistant Add-on
 
-[![Version](https://img.shields.io/badge/version-2.10.38-blue.svg)](https://github.com/Coolver/home-assistant-vibecode-agent)
+[![Version](https://img.shields.io/badge/version-2.10.39-blue.svg)](https://github.com/Coolver/home-assistant-vibecode-agent)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 [![MCP Package](https://img.shields.io/npm/v/@coolver/home-assistant-mcp?label=MCP%20Package)](https://www.npmjs.com/package/@coolver/home-assistant-mcp)
 

app/api/files.py

@@ -19,19 +19,47 @@ def _is_yaml_path(path: str) -> bool:
     return lower.endswith(".yaml") or lower.endswith(".yml")
 
 
+class _HAAllowTagLoader(yaml.SafeLoader):
+    """SafeLoader that treats unknown !tags (e.g. !include) as placeholders."""
+
+    pass
+
+
+def _unknown_tag_constructor(loader, tag_suffix, node):
+    if isinstance(node, yaml.ScalarNode):
+        return node.value or ""
+    return None
+
+
+_HAAllowTagLoader.add_multi_constructor("!", _unknown_tag_constructor)
+
+
+def _safe_load_yaml_allow_ha_tags(content: str):
+    """
+    Load YAML like safe_load but allow Home Assistant custom tags (!include,
+    !include_dir_merge_named, etc.) by treating them as opaque placeholders.
+    We only validate that the document is parseable; we do not resolve includes.
+    """
+    return yaml.load(content or "", Loader=_HAAllowTagLoader)
+
+
 def _validate_yaml_syntax(path: str, content: str) -> None:
     """
     Basic YAML syntax validation.
 
     Prevents writing obviously invalid YAML that would break Home Assistant.
+    Accepts HA custom tags (!include, !include_dir_merge_named, etc.) without
+    resolving them; only checks that the document is parseable.
     """
     if not _is_yaml_path(path):
         return
 
     try:
-        # We don't care about structure here, only that YAML parses
-        yaml.safe_load(content or "")  # empty file is valid YAML (None)
-    except Exception as e:  # yaml.YAMLError and others
+        _safe_load_yaml_allow_ha_tags(content or "")
+    except yaml.YAMLError as e:
+        logger.error(f"Invalid YAML when writing {path}: {e}")
+        raise HTTPException(status_code=400, detail=f"Invalid YAML in {path}: {e}")
+    except Exception as e:
         logger.error(f"Invalid YAML when writing {path}: {e}")
         raise HTTPException(status_code=400, detail=f"Invalid YAML in {path}: {e}")
 
@@ -53,7 +81,7 @@ def _validate_automations_structure(path: str, content: str) -> None:
         return
 
     try:
-        data = yaml.safe_load(content or "")
+        data = _safe_load_yaml_allow_ha_tags(content or "")
     except Exception as e:
         # Syntax errors are handled separately in _validate_yaml_syntax
         logger.debug(f"Skipping automations structure check for {path} due to YAML error: {e}")

app/main.py

@@ -26,7 +26,7 @@
 logger = setup_logger('ha_cursor_agent', LOG_LEVEL)
 
 # Agent version
-AGENT_VERSION = "2.10.38"
+AGENT_VERSION = "2.10.39"
 
 # FastAPI app
 app = FastAPI(

config.yaml

@@ -1,6 +1,6 @@
 # Home Assistant Add-on Configuration
 name: HA Vibecode Agent
-version: "2.10.38"
+version: "2.10.39"
 slug: home_assistant_cursor_agent
 description: "Enable Cursor, VS Code, Claude Code, or any MCP-enabled IDE to help you vibe-code and manage Home Assistant: create and debug automations, design dashboards, tweak themes, modify configs, and deploy changes using natural language"
 url: https://github.com/Coolver/home-assistant-cursor-agent

tests/HA_AGENT_TEST_SUITE.md

@@ -1,6 +1,6 @@
 # 🧪 Home Assistant Agent - Comprehensive Test Suite
 
-**Version:** 2.10.38  
+**Version:** 2.10.39  
 **Purpose:** Complete testing of all HA Cursor Agent MCP functions  
 **Usage:** Say "run Home Assistant Agent test suite" to run full suite
 
@@ -1140,5 +1140,5 @@ HA_AGENT_KEY=<your-token>
 
 **Last Updated:** 2026-01-27  
 **Test Suite Version:** 1.2.0  
-**Compatible with:** HA Cursor Agent v2.10.38+
+**Compatible with:** HA Cursor Agent v2.10.39+