David Heinemeier HanssonandClaude Opus 5.5
97a9fce54f
* Hand browser and web app launches to the running browser directly With a Chromium-based browser already running, each launch started a second browser process only to pass its command line over the profile's singleton socket and exit, ~165ms before the running browser even heard of it. omarchy-cmd-browser-handoff sends that message itself with socat and waits for the ACK, so a web app opens in ~210ms instead of ~430ms. It hands off only what it can do exactly as the browser would: the packaged browser binary rather than a wrapper, a flags file holding nothing beyond the process flags Omarchy ships, no other data directory, and a socket we own. Anything else, or no answer, launches the browser as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Hand Brave Origin launches to the running browser too /usr/bin/brave-origin is the package's own launcher, reading brave-origin-flags.conf, with the profile in BraveSoftware/Brave-Origin. A web app now opens in ~158ms instead of ~345ms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
18 lines
554 B
Bash
Executable File
18 lines
554 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# omarchy:summary=Launch a URL as a web app in the default supported browser
|
|
# omarchy:args=<url>
|
|
|
|
browser=$(omarchy-cmd-default-browser)
|
|
|
|
case $browser in
|
|
google-chrome* | brave* | microsoft-edge* | opera* | vivaldi* | helium*) ;;
|
|
*) browser="chromium.desktop" ;;
|
|
esac
|
|
|
|
browser_exec=$(sed -n 's/^Exec=\([^ ]*\).*/\1/p' {~/.local,~/.nix-profile,/usr}/share/applications/$browser 2>/dev/null | head -1)
|
|
|
|
if ! omarchy-cmd-browser-handoff "$browser_exec" --app="$1" "${@:2}"; then
|
|
exec setsid uwsm-app -- $browser_exec --app="$1" "${@:2}"
|
|
fi
|