Notification settings
AstralOverlay displays one notification card at a time. Later cards wait in a bounded queue.
Visibility and API access
Section titled “Visibility and API access”Notifications controls the presentation of cards. Notification API controls the public localhost listeners. They are separate settings.
Do not disturb silences notification presentation. Do not treat disabling presentation as an API disconnect or as guaranteed storage for later delivery.
Position
Section titled “Position”Choose head-locked or world-positioned presentation and one of nine screen positions. The default is head-locked, top centre.
The configurable distance applies to world-positioned placement. Head-locked cards use their own fixed distance in the current implementation.
Sounds
Section titled “Sounds”Notification settings control Play notification sounds and Sound volume. The current host plays the bundled notification sound using this global volume.
The API parser accepts per-message audio fields, but those do not currently select custom files or override the sound implementation. See compatibility.
Windows notifications
Section titled “Windows notifications”Mirror Windows notifications is separate from the third-party notification API and is off by default. It uses the companion process to bring Windows notifications into the same card queue.
If API notifications work but Windows notifications do not, check that setting and the companion’s access to Windows notifications.
Integrating another app
Section titled “Integrating another app”Start with the WebSocket guide, or use legacy UDP for existing tools.