CLI drops output when stdin is closed (eg: coding agents)

Bug reports
1

Steps to reproduce

  • Open Obsidian like normal
  • /Applications/Obsidian.app/Contents/MacOS/Obsidian sync:deleted total # has output
  • /Applications/Obsidian.app/Contents/MacOS/Obsidian sync:deleted total </dev/null # no output

Did you follow the troubleshooting guide? Y

Please, follow the Troubleshooting Guide before answering Yes.

Expected result

obsidian sync:deleted total </dev/null should print the same result as obsidian sync:deleted total, e.g.:

  612

Commands that do not read from stdin should not lose output just because stdin is closed or non-interactive.

Actual result

The command exits with status 0 but prints nothing to stdout or stderr:

  obsidian sync:deleted total </dev/null
  # no output
  # exit code 0

Environment

SYSTEM INFO:
Obsidian version: 1.12.7
Installer version: 1.12.7
Operating system: Darwin Kernel Version 25.4.0: Thu Mar 19 19:33:25 PDT 2026; root:xnu-12377.101.15~1/RELEASE_ARM64_T6041 25.4.0
Login status: logged in
Language: en
Catalyst license: none
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: Minimal 8.1.6
Snippets enabled: 1
Restricted mode: off
Plugins installed: 16
Plugins enabled: 16
1: Vimrc Support v0.10.2
2: Templater v2.20.5
3: Tasks v8.0.0
4: Tag Wrangler v0.6.4
5: Style Settings v1.0.9
6: Settings Search v1.3.10
7: Advanced Tables v0.23.2
8: Copy Block Link v1.0.4
9: Emoji Shortcodes v2.2.0
10: Global Hotkeys v0.1.2
11: Minimal Theme Settings v8.2.3
12: Paste URL into selection v1.11.4
13: QuickAdd v2.12.2
14: Relative Line Numbers v3.0.0
15: Excalidraw v2.23.5
16: Granola Sync v2.0.25
RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Additional information

This affects coding agents like as pi, Codex, Claude Code, etc, where subprocess stdin is commonly non-TTY or already at EOF.

I searched for duplicates and did not find this exact issue - related but distinct threads:

This issue is different from requesting stdin-as-content support. The command above does not need stdin; closed/non-TTY stdin appears to cause the CLI connection to close before async command output is returned.

Note - I did use an agent to dig into this and prep the report, but tested quite a bit manually.