From ac6f23ded553e6f43b97321c644e4d450d912047 Mon Sep 17 00:00:00 2001 From: 28allday Date: Fri, 29 May 2026 14:47:22 +0100 Subject: [PATCH] skill: document omarchy-send v0.1.6 headless send + notifications MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The baked omalocal-server skill (SKILL.md) and CLAUDE.md now cover the v0.1.6 additions: - Headless one-shot message send (--to/--message, no TTY) — usable from scripts/cron/ssh on this headless box to ping a desktop or phone. - Desktop notifications: noted as a no-op here (self-disables without a session bus); relevant for the desktop side that receives from this box. Co-Authored-By: Claude Opus 4.8 (1M context) --- omalocal.sh | 40 ++++++++++++++++++++++++++++++++++++++-- 1 file changed, 38 insertions(+), 2 deletions(-) diff --git a/omalocal.sh b/omalocal.sh index 680684b..305e6ff 100755 --- a/omalocal.sh +++ b/omalocal.sh @@ -811,7 +811,35 @@ omarchy-send --alias "Gold Cluster" # one-off alias override ``` The TUI needs a real TTY — over SSH that means an interactive session (or -`ssh -tt user@host omarchy-send` for scripted runs). If install was skipped: +`ssh -tt user@host omarchy-send` for scripted runs). + +### Headless one-shot message send (no TTY — for scripts/cron) + +Since **v0.1.6** a plain-text message can be sent with NO TUI and NO TTY, so it +works from a bare `ssh user@host '...'`, a cron job, or a deploy hook on this +headless box — ideal for pinging your desktop or phone from the server: + +```bash +omarchy-send --to "" --message "backup finished" +omarchy-send --to "Slate Starburst" --message "deploy done" --wait 20s # peer-discovery timeout (default 15s) +omarchy-send --to "" --message "hi" --send-pin 2468 # if the target requires a PIN +``` + +Matches the target by display name (case-insensitive), discovers it over +multicast (waits up to `--wait`), sends, prints a one-line result, and exits +non-zero if the peer isn't found or the send fails. Discovery-only — it doesn't +bind the receiver port, so it's safe to run while the TUI is also up. File +sending stays in the TUI for now. + +### Desktop notifications + +A running receiver raises a `notify-send` notification on an incoming +message/file. On this headless box it self-disables (no `notify-send` / session +bus), so it's a no-op here — its value is that a *desktop* running omarchy-send +pops a mako toast when this server messages it. Suppress with `--no-notify` or +the `n` key in Settings. + +If install was skipped: ```bash curl -fsSL https://raw.githubusercontent.com/28allday/omarchy-send/main/install.sh | bash @@ -967,7 +995,15 @@ omarchy-send # open the TUI (Devices / Transfers / Mess ``` The TUI needs a real TTY — over SSH that means an interactive session (or -`ssh -tt user@host omarchy-send`). If install was skipped, run: +`ssh -tt user@host omarchy-send`). To send a one-off message with NO TTY (from +a script/cron on this headless box — e.g. ping a desktop/phone), use the +headless mode added in v0.1.6: + +```bash +omarchy-send --to "" --message "backup finished" # also --send-pin, --wait; file send stays TUI-only +``` + +If install was skipped, run: ```bash curl -fsSL https://raw.githubusercontent.com/28allday/omarchy-send/main/install.sh | bash