HyperNotifyby HyperorganicInvite-only beta

GET CONNECTED

Your agent. Your Slack.

Add HyperNotify, connect your Slack account, then check one DM and return to your task.

  1. Add HyperNotify to your agent.

    The standard Mac setup includes the agent plugin, a bundled runtime, and a background sender that starts at login. The sender saves unsent notifications in an encrypted queue and retries when you're online. It has no separate app window.

    Turn-finished alerts start on. You can turn them off independently while keeping action requests, error alerts and your connection. A finished turn does not mean the whole task is complete.

    Review access and removal before installing

    Action requests send the text your agent prepares, project and task labels, and a return identifier. Automatic alerts send generic turn-status text. HyperNotify doesn't upload prompts, answers, transcripts or repositories, or ask for model-provider keys or Slack history.

    The helper keeps its own credential in your login Keychain. Slack app credentials stay in the cloud. The Mac must be awake, logged in and able to unlock Keychain until the cloud accepts the request.

    Pending content is encrypted and removed from active storage at cloud acknowledgement locally and terminal delivery in the cloud. Each queue has a maximum 24-hour pending window while running. Minimal receipts remain for duplicate prevention; Slack keeps its own copy.

    Updates preserve account choices and queues. Remove the helper with its uninstall command; remove the hosted connection in your agent too. Details below.

    Private, unsigned Mac betaThe archive isn't Apple notarized. If macOS blocks it, report the message. Don't disable Gatekeeper or remove quarantine. Intel execution remains unverified.

    Open your protected installation invitation for the Mac package and checksum. Hyperorganic is the only approved Slack workspace.

    Codex desktop

    Run the extracted package's installer:

    ./install.command

    Review and trust the HyperNotify hooks yourself. This command opens the CLI bundled with your desktop app. Enter /hooks, review HyperNotify, then exit and start a fresh task in Codex desktop.

    "$HOME/Library/Application Support/HyperNotify Employee/bin/hypernotify" review-hooks

    Codex supports automatic successful turn endings. Automatic error-stop alerts are not supported by its current public hooks.

  2. Connect Slack with your own account.

    In the new task, ask:

    Connect HyperNotify and send a test DM from this task.

    Your agent opens a Slack sign-in and connection review. Check your account, the agent and the permissions. Then confirm the local helper's matching device code so automatic alerts and the offline queue can use the same account. That code expires after ten minutes.

    The workspace administrator installs the Slack app once. As an employee, you sign in individually; you don't need administrator rights. Don't connect someone else's account.

  3. Receive a test and return to your task.

    Return to your agent to finish setup. Check the test DM and its return action. Codex uses a link when the actual desktop task ID is available. Claude Code uses a task locator.

    Let the turn finish naturally to check its automatic alert. Then restart the helper and client and try a normal turn. A Slack-accepted receipt and a notification you saw are separate checks.

    If delivery is uncertain, check the original receipt and Slack. Keep the same request ID; don't send another copy to force a test.

Your notification choices

Use HyperNotify's connection panel where your agent supports it, or sign in to connections and preferences. Turn-finished alerts, needs-input requests, review requests and Claude error alerts have separate controls. Pausing all alerts is a separate setting.

Local controls, update and uninstall

These switches apply to this Mac. Account preferences also apply. Reconnecting doesn't turn your choices back on.

"$HOME/Library/Application Support/HyperNotify Employee/bin/hypernotify" status
"$HOME/Library/Application Support/HyperNotify Employee/bin/hypernotify" alerts --automatic off
"$HOME/Library/Application Support/HyperNotify Employee/bin/hypernotify" restart
"$HOME/Library/Application Support/HyperNotify Employee/bin/hypernotify" uninstall

To update, run the new package's installer with the same client selection. Start fresh client sessions and review changed hooks. Uninstall revokes this helper's devices, removes its plugin and background job, and preserves local receipts by default. Add --forget-data to remove those receipts and the local encryption key. Remove separately added hosted connections in your agent or on the account page. Delivered Slack messages are separate.

If remote revocation fails, reconnect and retry or revoke the connection on the account page. Uninstall reports the outstanding connection rather than claiming it was removed.

Hosted connection and technical details

The plugin connects over MCP at https://notify.hyperorganic.ai/mcp, with OAuth authorization bound to your verified Slack membership. Hosted tools handle prepared action requests, preferences and receipts. Supported OpenAI clients can show a small native panel; Claude Code uses tool results and the account page.

A hosted-only connection can send action requests without downloading the Mac helper. It does not observe local turn endings or buffer events on an offline Mac. Use the full setup above for the default automatic alerts.

For a hosted-only Claude Code connection:

claude mcp add --transport http hypernotify https://notify.hyperorganic.ai/mcp

Then use /mcp to authenticate. Codex can add the private HyperNotify plugin or configure the same remote MCP endpoint in its settings. Directory publication is not part of this beta.

Company setup and connection recovery

Only approved workspaces can connect. An administrator can install or reconnect the workspace app. Employees use their own Slack account. If a pairing expires, keep your Slack sign-in and ask the agent for a new code when ready. Revoked hosted connections need authorization again. Existing requests retain their original IDs and owner.