Wake phrase Computer → AutoVoice grabs the follow-up → Tasker POSTs to /ask → system TTS speaks the response over A2DP to the Ray-Bans. Same delivery pattern as the proven 7 AM brief.
AutoVoice is the only Tasker-native, battery-friendly, always-listening wake-word path that doesn't put Google Assistant in front of Claude. Your stack is already Tasker-centered (the 7 AM brief profile is the proven pattern). Picovoice Porcupine is technically cleaner but needs a custom Android wrapper and a JS binding to bridge into Tasker — that's a half-day, not five minutes. Free AutoVoice caps commands at 4 characters after the trial, so the $3.99 unlock is the actual line item, not the base install.
Computer. Continuous listening ON, "use Google offline recognition" ON (keeps it off Google servers).Command Filter = Computer (.*) with regex on. %avcommnofilter captures the follow-up.Computer Ask:
POST https://memory.thebarnetts.info/ask, header Authorization: Bearer ijrM5jNq1gSCrIiEy3opZwjPTgbCeM7uWK7CgS36IAY, body {"question": "%avcommnofilter"}, timeout 25s.Text: %http_data (routes to Ray-Bans via A2DP).If AutoVoice's recognition service gets killed by Pixel 8 Pro's aggressive doze (it sometimes does on Android 14+), the drop-in alternative is the Hotword Plugin for Tasker (nl.jolanrensen.hotwordPlugin, free, on-device Vosk). Heavier battery, but no Google round-trip and no IAP — same Tasker profile shape (Event → Plugin → Hotword), same /ask POST. If even Hotword struggles, escalate to a Picovoice Porcupine-based custom APK — the right-answer durable path, but a full session of work, not tonight's ship.
reference_tasker_brief_pipeline_2026-05-05.md — HTTP Request → Say → A2DP to Ray-Bans is already proven on this device.