Signals — Error Inbox Overview

What Signals Is

Signals is VORTΞXHQ's error inbox. Your applications send errors to a per-app endpoint; the desktop client shows them as a chat-style feed grouped by hour, with severity and type on every entry.

Apps (Sources)

• Create an app per project/environment — each gets its own ingest credentials.
• Edit or delete apps at any time; deleting an app clears its feed.
• Mute a noisy source without deleting it.

Local vs Cloud Mode

• Local: errors are stored in an embedded SQLite database on your machine — works without an account. The client also runs a local ingest endpoint (http://127.0.0.1:7755/errors) for apps on the same machine.
• Cloud: errors stream in real time over WebSockets and are shared with your Nexus members.

Notifications

• Sound, OS notification and dock badge — each toggleable separately.
• Quiet hours: a start/end window during which Signals stays silent.

Working the Feed

• Open an error for full context; run AI error analysis to get a probable cause and fix suggestion.
• Mark errors as seen, delete individual entries, or clear a whole app.

For Agents (MCP)

External agents connected over MCP can read Signals data:

• signal_list_apps — list signal apps, optionally scoped to a nexus.
• signal_get_app — details for one app by id.

Both are read-only and need no approval. Credentials never leave the app — responses are sanitized before they reach the agent.