macOS: launching Kiri from Finder/Dock exits silently (open returns 0), and the log records command="" instead of what failed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
Research direction
Start by tracing the macOS Finder/Dock launch path that emits the command failed log in ~/.kiri/logs/ui.log, then compare it with the working shell launch described in the issue. Reproduce with open -a /Applications/Kiri.app and inspect how the command and LaunchAgent are selected; the issue does not name source files or tests. Done means GUI launch opens the window or reports an actionable error, and the failure log identifies the attempted command.
Written by the indexing model from the issue text.
Description
Environment
- Kiri 0.2.0 (arm64, thin), macOS 27.2.1 (26B131), Apple M3 Max, 128 GB
- Installed from the website download into
/Applications/Kiri.app - Binary verified
Mach-O 64-bit executable arm64; Gatekeeper:accepted,source=Notarized Developer ID,origin=Developer ID Application: PRECIOUS CHIGOZIE OKWU (Z44N5GDT9TQ) - OrbStack also installed and running (left untouched throughout)
What happens
Launching Kiri as a normal application (Finder, Dock, or open -a) exits immediately. No window, no daemon, no error. open returns 0.
$ open -a /Applications/Kiri.app; echo "rc=$?"
rc=0
$ ps aux | grep Kiri.app | grep -v grep
(nothing)
The only trace is one line in ~/.kiri/logs/ui.log:
{"time":"2026-11-15T04:32:09.507Z","level":"warn","part":"ui","msg":"command failed","fields":{"command":"","error":"No such file or directory (os error 2)"}}
command is an empty string, so the log does not say what it tried to exec and could not find. That is the blocker: every other avenue of diagnosis here was closed by that one blank field.
The same binary launched from a shell works:
$ /Applications/Kiri.app/Contents/MacOS/kiri ui
2026-11-15T04:35:45.187Z INFO update check latest=0.2.0 current=0.2.0
$ ps aux | grep "MacOS/kiri ui" | grep -v grep
24643 /Applications/Kiri.app/Contents/MacOS/kiri ui
So the engine, the window and the app itself are fine. Only the launchd/GUI launch path fails.
Steps to reproduce
-
Quit Kiri completely; confirm no
Kiri.appprocess remains. -
Wipe all state, to rule out config corruption:
rm -rf ~/.kiri ~/Library/Application\ Support/Kiri \
~/Library/Caches/dev.kiri.app
- Launch it the way a user does:
open -a /Applications/Kiri.app
Actual: rc=0, no process, no window, no daemon.
~/.kiri is recreated containing only bin/kiri (a correct symlink to the app binary) and logs/ui.log with the single command="" ENOENT line.
Expected: the window opens and the engine starts, as documented — "Opening the app starts it as a LaunchAgent".
Control: running /Applications/Kiri.app/Contents/MacOS/kiri ui from a shell immediately afterwards starts fine and stays up.
Reproduces every time; observed on roughly 10 launch attempts across three separate sessions, including a fully wiped config.
Also relevant
docs.runkiri.com (How it works) states the daemon "is started as a LaunchAgent". No LaunchAgent exists on this machine, and launchd does not know the service:
$ find ~/Library/LaunchAgents /Library/LaunchAgents /Library/LaunchDaemons -iname "*kiri*"
(nothing)
$ launchctl print gui/502/dev.kiri.app
Could not find service "dev.kiri.app" in domain for user gui: 502
This matches #48 point 1, where launchctl kickstart -k gui/501/dev.kiri.daemon also reported Could not find service. I cannot tell from the logs whether the missing LaunchAgent causes this failure or is a consequence of it, because command is not logged.
Expected
- Launching from Finder/Dock opens the window, or shows an explicit error the user can act on. Exiting silently with a zero exit code is the worst case for a user: nothing to report, nothing to retry.
command failedlogs the command it actually tried to run.command=""makes the failure undiagnosable from the shipped logs. This is the same class of problem as #94, where the real error was hidden behind "the test container did not run" — now fixed for Windows setup by #101. macOS launch needs the same treatment.- Opening the app should not depend on a LaunchAgent that the installer did not create.
Workaround
Start it from a shell, then the window attaches:
/Applications/Kiri.app/Contents/MacOS/kiri daemon &
/Applications/Kiri.app/Contents/MacOS/kiri ui
Reported as a bug rather than used quietly, because a desktop app that only starts from a terminal will lose most users on first run.
- Dominant language
- Rust
- Stars
- 7.5k
- Forks
- 329
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 105
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libracoder/kiri
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#289 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 47/100
libracoder/kiri#365 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
libracoder/kiri#362 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 47/100
libracoder/kiri#359 ·
Maintainers usually reply within 1 day
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matrix-org/matrix-rust-sdk#7495 ·
Maintainers usually reply within 1 day