Yes.
Tested in a sandbox vault with no third-party plugins, no CSS snippets, and default theme.
Expected result
The command should create a file with multibyte character content (Japanese, Chinese, Cyrillic, emoji, etc.) just like it does with ASCII and Latin-1 text.
Actual result
The command hangs and times out when trying to write multibyte characters. The file is not created. Latin-1 characters (like “Café”) work fine, but anything beyond that fails.
SYSTEM INFO:
Obsidian version: 1.12.0
Installer version: 1.11.7
Operating system: Darwin Kernel Version 25.3.0: Wed Jan 28 20:48:41 PST 2026; root:xnu-12377.81.4~5/RELEASE_ARM64_T6041 25.3.0
Login status: logged in
Language: en
Catalyst license: insider
Insider build toggle: on
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 0
Plugins enabled: 0
RECOMMENDATIONS:
none
I can confirm this on Ubuntu 24.04.3 LTS with fish shell
Environment: Obsidian 1.12.0 (installer 1.11.7), Linux x86_64 (Ubuntu 24.04, kernel 6.8), LANG=en_US.UTF-8, LC_ALL=C.UTF-8. CLI binary at /opt/Obsidian/obsidian, symlinked from
~/.local/bin/obsidian.
Problem: Any CLI command that passes a 3-byte (or wider) UTF-8 character in any parameter value hangs indefinitely. The command never returns — no output, no error. Requires manual kill.
I did some additional testing to narrow down the reproduction conditions.
Environment:
macOS Tahoe 26.3
Obsidian 1.12.0 (installer 1.11.7)
.app installation from download page
Tested on:
zsh + Ghostty 1.2.3
zsh + Terminal.app
bash + Ghostty 1.2.3
Locale: LANG=en_US.UTF-8
Key finding is that the hang occurs when the command-line arguments contain both a space and a 3-byte UTF-8 character.
The space and the 3-byte UTF-8 don’t need to be in the same parameter. For example, a space in the vault name combined with a CJK character in content= is enough to trigger the hang.
# [OK] No space anywhere + 3-byte UTF-8
obsidian create path="Test.md" content="日本語" overwrite vault="vault"
obsidian create path="Test.md" content="Test日本語" overwrite vault="vault"
# [OK] Space present + 2-byte UTF-8 only
obsidian create path="Test.md" content="Café" overwrite vault="Obsidian Sandbox"
obsidian create path="Test.md" content="Hello world" overwrite vault="Obsidian Sandbox"
# [HANG] Space in vault name + 3-byte UTF-8 in content
obsidian create path="Test.md" content="日本語" overwrite vault="Obsidian Sandbox"
obsidian create path="Test.md" content="🎉" overwrite vault="Obsidian Sandbox"
obsidian create path="Test.md" content="—" overwrite vault="Obsidian Sandbox"
# [HANG] Space in content + 3-byte UTF-8 in content (no space in vault name)
obsidian create path="Test.md" content="日本語 a" overwrite vault="vault"
obsidian create path="Test.md" content="a 日本語" overwrite vault="vault"
Additional observations:
Reproduces identically across shells (zsh, bash) and terminal (Ghostty, Terminal.app)
@vlahan’s examples are also consistent with this pattern. All hanging cases (“em dash — here”, “en dash – here”, “Price is 50€”, “Hello 你好”) contain both a space and a 3-byte UTF-8, while all working cases contain only ASCII or 2-byte UTF-8