Environment:
- Obsidian app: 1.12.4
- Installer: 1.9.14
- OS: Windows 11 Home
- Shell: Git Bash (MSYS2) / PowerShell
- Obsidian.com file: missing
Reproduction:
1. Install Obsidian using an older installer (pre-CLI, e.g. 1.9.14)
2. Update Obsidian app to 1.12.4 via in-app update
3. Enable CLI in Settings > General > Advanced > Command line interface
4. Run any colon subcommand WITH parameters:
obsidian property:set name=status value=active
obsidian daily:append content=“hello”
obsidian property:read name=tags
All return exit code 127 with no output.
5. Run the SAME colon subcommand WITHOUT parameters:
obsidian property:set
obsidian daily:append
These work correctly (show usage/help text).
6. Non-colon commands with parameters work fine:
obsidian read path=“note.md”
obsidian create path=“test” content=“hello”
Expected: All CLI commands should work after enabling CLI.
Actual: Colon+parameter combinations fail silently.
Root cause: The in-app updater updates the .asar but does not
generate the Obsidian.com console redirector file needed for
full Windows CLI support.
Suggested fix:
- The in-app updater should generate Obsidian.com if missing
- Or: CLI enable toggle should check and warn if Obsidian.com
is not present
- Or: Obsidian.exe should handle these commands even without
the .com wrapper
```