open_application reports launched:true when merely resolving a running app
- Dominant language
- Rust
- Stars
- 41k
- Forks
- 3.6k
- Avg merge
- 13h 59m
- Merged PRs (30d)
- 299
Description
`open_application` reports `launched: true` even when it merely resolved an already-running process. The value is hardcoded in the return at `src/backends/darwin.mjs:747` — the launch branch above it (`if (!p?.found)`) is conditional, but the receipt is not.
Observed during the 0.8.0 acceptance pass (Hmbown/Codewhale#6300): re-binding the already-running TextEdit (pid 90943) returned `launched: true`. Same receipt-honesty class as Hmbown/Codewhale#5927.
Fix: track whether this call actually launched the process and report that. JS-layer only (darwin.mjs); still needs the usual propagation (marketplace mirror, Core vendored copy, bundle rebuild) plus an app restart to pick it up — restart, not reinstall, so no TCC risk. Add a regression test asserting `launched: false` on re-bind.
Contributor guide
Research direction
Start in src/backends/darwin.mjs at line 747 and inspect the conditional launch branch above the hardcoded receipt. Add the regression test requested for rebinding an already-running app, then verify the marketplace mirror, Core vendored copy, and bundle are propagated and restart the app to confirm launched:false.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100