What CoIsland watches in Shell command

Each monitor kind brings its own query and its own card in the notch.

How to monitor a command from your Mac’s notch

Health checks, backups, a folder that should stay empty: a lot of what needs watching already has a command. A Shell command monitor runs it on a schedule and opens the notch when its answer changes.

-- name: Website down
-- kind: shell.exit-code
-- connector: mac
-- every: 5m

/usr/bin/curl -fsS --max-time 10 https://example.com/health

Run a command covers the quoting rules, the three kinds and each error. All connectors share one page.

Connect it in three steps

  1. Add a Shell command connector: a name and, optionally, the folder commands run in and a timeout.

  2. Write the command: the program and its arguments, quoted as in a shell. A pipeline goes in a script file.

  3. Pick what it alerts on: new lines, new JSON objects, or a failure. It checks every 5 minutes unless you change it.

Built for Shell command

  • No shell reads the command: what you type is what runs, and nothing in it can start a second command.
  • It runs on your Mac as you; nothing is sent anywhere, and nothing is kept in the Keychain.
  • A command still running at its timeout is stopped.

Then hand it to an agent

A click on the alert opens the agent in a terminal under it, with the whole alert as its first message.

Shell command questions

Can I use a pipe or a redirection?

Put them in a script file and run the script, or write /bin/sh -c '...' yourself. CoIsland refuses an unquoted | or > so a command never does something other than what it looks like.

Is it safe?

A command runs as you, with your files, keys and network, like one you type in Terminal. Only run what you wrote or trust. Opening an alert never runs it again.

Other connectors

Put your work stack in the notch

Regular price: $59.99 Early bird price: $19.99 once, for 2 Macs. Native for Apple Silicon, macOS 14 and later.

Early bird price until October 25