anotify is a cross-platform desktop companion for AI agents and remote jobs that need request-based approvals, continuously updated inbox activity, and system tray notifications in version 0.2.1.

Download anotify v0.2.1

Download Latest Build

anotify provides a desktop inbox for delivering notifications and handling approval requests from AI agents, remote jobs, and automation-focused workflows. It is built for situations where updates must reach the right person promptly and actions should be easy to acknowledge.

The application pairs a cross-platform desktop interface with an optional self-hosted relay. WebSocket delivery keeps inbox activity current, while tray alerts provide background visibility. Token authentication and request-oriented approvals add a consistent structure for processing events across different operating environments.

• Desktop notifications across supported platforms
• Approval requests for tasks that require interactive decisions
• Inbox entries for new events and available actions
• WebSocket-based updates with near real-time delivery
• Optional self-hosted relay deployment
• Token authentication for access control
• Connectivity from remote hosts that only make outbound connections
• System tray alerts for unobtrusive background notifications

Obtain the source with Git or download the newest build from the project page.

git clone https://github.com/noah-reedetle2876/anotify-desktop-approval-hub.git
cd REPO

Once the files are available, open the desktop application or run the packaged build intended for your platform. When using the source version, use the repository's documented startup process for its frontend and backend components.

The normal flow is to connect a client, listen for incoming events, and process approval requests from the desktop inbox.

1. Bring up the relay or service endpoint.
2. Authenticate and register the desktop client with a token.
3. Leave the application running so it can receive inbox events over WebSocket.
4. Inspect incoming requests and approve or reject them through the notification workflow.
5. Monitor background activity through tray notifications.

A minimal workflow looks like this:

# Start the local or self-hosted service
# Launch the desktop client
# Connect using your token and relay settings

For remote jobs, an outbound-only host can establish the client connection without exposing inbound access on that machine.

The desktop application settings and the environment values used by the relay and client provide the main configuration points. Typical values cover the relay endpoint, access token, and notification preferences.

relay_url: "https://your-relay.example"
auth_token: "your-token-here"
websocket_enabled: true
tray_notifications: true

When operating your own relay, make sure the backend and desktop client use the same service address and authentication token.

• A cross-platform desktop environment
• A compatible runtime when using either the packaged application or source build
• Network connectivity for relay communication and WebSocket updates
• Local storage for settings and inbox state
• A token for authenticated connections

How can events reach my desktop inbox?
Point the desktop client at a relay or service that emits events through WebSocket.

Does anotify support remote jobs?
Yes. Remote outbound-only hosts are supported, making the setup suitable when inbound connectivity is unavailable or restricted.

Where are the relay and connection values configured?
Review the desktop app settings and the relay environment values used by your deployment.

Why are no notifications showing up?
Verify that the client is running, the authentication token is correct, and the WebSocket session is connected. Tray notification behavior can also vary with the desktop environment.

What is the approval process?
Actions arrive as requests in the desktop inbox, where they can be reviewed and either approved or rejected.

GNU GPL v3.0 - see LICENSE for details.