Dream Collection Hall

Push notifications without a platform

2026-10-12

Every tool in your life wants to tell you something. The build finished. The backup failed. The agent you left running hit an error at 3 a.m. The disk on your NAS is at 91%. Each of these is a small, urgent, private message — and the industry has settled on a strange idea of how to deliver it: sign up for something.

The platform tax on a simple message

Look at what "getting notified" usually requires:

Every one of these makes a third party a mandatory participant in a conversation that was never any of their business. The message is yours, the machine that sent it is yours, the screen it should land on is yours — and yet delivery requires renting a seat on someone else's infrastructure.

What the last mile should look like

A notification is a file with a destination. If we accept that, the whole architecture collapses into something embarrassingly simple: a watched folder, a command-line tool, and a localhost HTTP endpoint. That's WDD Inbox, and it's the entire stack:

  1. Anything that can write a file can message you. Drop a small JSON event into the push directory. Done. No SDK, no account, no API key ceremony.
  2. Anything that can run one command can message you. wdd push --project ops --level action_needed --type todo --title "Renew the TLS certificate" — a shell script's way of tapping you on the shoulder.
  3. Anything that can make an HTTP call can message you. Including AI agents, which are increasingly fluent in exactly one protocol. POST an event to localhost and go back to work.

Three layers, one principle: if it can happen on your machine, it can land in your inbox. And because the endpoint is plain HTTP on your own computer, you can put your own relay in front of it and receive events from anywhere you choose — a VPS, a build farm, a sensor in another country. The relay is yours. The rules are yours.

The differences that actually matter

Strip the feature lists and three things separate this from every platform option:

Senders pay nothing. No signup, no token approval, no quota, no rate limit negotiated with a vendor. A cron job written in 2010 and an AI agent written this afternoon have the same, zero-friction way to reach you. When the cost of sending an event is zero, tools that never used to speak up start reporting back.

The data is a file you own. Events are plain JSON on your disk, written once and never modified. No server-side database, no retention policy, no analytics. You can archive them, grep them, delete them — the history is inspectable because the history is the filesystem.

Delivery is the operating system's job. Messages land in macOS Notification Center: banners, sounds, Focus modes, per-app controls. Not another app's idea of a feed, but the notification discipline you already configured for your life. One inbox for the machines, with the same respect your phone gives your messages.

Where it shines — and where it doesn't

This is a Mac-native, local-first channel. It shines for automation receipts, AI agent progress, home-lab alerts, and anything privacy-sensitive you'd rather not route through a cloud. It does not try to be a chat tool — it's a doorbell, not a salon. Your phone can't receive it; group conversations aren't its job; nobody's building a social graph on a folder full of JSON.

We think that's exactly right. The tools that run your life should report to you the way a good colleague does: quietly, completely, and without involving the whole office.

WDD Inbox is available on the Mac App Store.