nosignal/omalocal
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

skill: document omarchy-send v0.1.6 headless send + notifications

Browse source 
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) <noreply@anthropic.com>
This commit is contained in:
28allday 2026-05-29 14:47:22 +01:00
parent 30333acccb
commit ac6f23ded5
1 changed files with 38 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
omalocal.sh
View file

@ -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 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 "<peer alias>" --message "backup finished"
omarchy-send --to "Slate Starburst" --message "deploy done" --wait 20s # peer-discovery timeout (default 15s)
omarchy-send --to "<alias>" --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 ```bash
curl -fsSL https://raw.githubusercontent.com/28allday/omarchy-send/main/install.sh | 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 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 "<peer alias>" --message "backup finished" # also --send-pin, --wait; file send stays TUI-only
```
If install was skipped, run:
```bash ```bash
curl -fsSL https://raw.githubusercontent.com/28allday/omarchy-send/main/install.sh | bash curl -fsSL https://raw.githubusercontent.com/28allday/omarchy-send/main/install.sh | bash