felt-desktop-agent

Felt's desktop-side sensor — currently: D-Bus desktop-notification passthrough, read aloud via felt-voice's TTS. Part of the Felt project.

Runs on the user's own desktop (not the server) since it needs the session D-Bus and the local audio output — a natural home for other desktop-side pieces later (fullscreen/game-focus gating, KDE Connect integration).

Why it exists

"If I'm playing I don't want to have to read it, just read my WhatsApp message or something" (Mario) — a fullscreen game means desktop toast notifications go unseen.

Config

• FELT_AGENT_VOICE_URL — felt-voice's URL (default assumes the Nitro5).
• FELT_AGENT_ALLOWED_APPS — comma-separated, case-insensitive app-name allowlist. Empty by default — nothing is read aloud until an app is explicitly added. This is deliberate: no default-everything behavior.

Quickstart

uv sync
cp .env.example .env   # set FELT_AGENT_ALLOWED_APPS
uv run felt-desktop-agent

Status (2026-09-12)

Built and verified: fires a real D-Bus notification, reads it aloud through felt-voice + local audio playback, confirmed with a live test (notify-send, allowlisted for the test). Fullscreen/game-focus gating is built too — the actual ask was "while I'm playing," not "always." Uses Wayfire's own ipc plugin (via the wayfire PyPI client) to check for a fullscreen+activated view; confirmed live against a real running game, not just in theory. Fails closed (won't speak) if the IPC socket is ever unreachable.

Not yet done: real D-Bus notification app_name values for WhatsApp/Discord. Their Wayland app-ids are confirmed live (com.ktechpit.whatsie / WhatSie, vesktop), but that's a different identifier space from the D-Bus notification app_name this watcher actually filters on — still needs an observed real Notify() call from each before they can be safely added to the allowlist.