hermes - 💡(How to fix) Fix write_file creates directory with literal backslash in path containing space

Bug: write_file creates directory with literal backslash in path containing space

Description

When using the write_file tool with a path that contains a space (e.g. ~/Documents/Obsidian Vault/file.md), the tool creates a directory with a literal backslash character instead of treating the space as a directory separator.

Steps to reproduce

1. Invoke: write_file(path="~/Documents/Obsidian Vault/test.md", content="hello")
2. The tool resolves the path to /Users/user/Documents/Obsidian\ Vault/test.md (with backslash)
3. Instead of writing to the correct directory /Users/user/Documents/Obsidian Vault/test.md

Expected behavior

The tool should properly handle spaces in path components by:

• Resolving ~ to the user's home directory
• Treating backslash-space as an escaped space (i.e., breaking the path at the space, not treating backslash as a literal character)

Actual behavior

A directory named Obsidian\ Vault (with backslash in name) is created alongside the correct Obsidian Vault directory. Files are written to the wrong location.

Environment

• Hermes Agent version: latest (bank-risk profile)
• macOS 26.5.1
• path passed with ~ expansion + escaped space

Additional context

• terminal + cat heredoc works correctly with the same paths
• patch tool also has the same issue with space-containing paths
• This has been confirmed across multiple write operations