A community proof of concept for starting ChatGPT Voice on a Windows PC after Home Assistant verifies that someone has arrived home, including workflows that use Voice to coordinate Codex tasks.
Project status: Experimental and currently untested on physical hardware. This repository documents a proposed workflow and provides starter automation scripts. It is not an official OpenAI project and should not be treated as production-ready until tested on your own system.
Phone enters home zone
+
Phone connects to trusted home Wi-Fi
↓
Home Assistant confirms arrival
↓
Home Assistant calls the Windows endpoint
↓
Windows opens or focuses ChatGPT/Codex
↓
Windows sends your configured Voice shortcut
The project deliberately does not assume a default Voice shortcut. Configure your shortcut in the ChatGPT/Codex app, then place the same shortcut in the Windows script.
OpenAI documents a configurable Voice chat hotkey under Settings > Voice in the ChatGPT desktop app. Home Assistant can verify presence using multiple signals. Combining the two creates a practical "welcome home" voice workflow without requiring an official geofence integration.
See the official ChatGPT Voice documentation for current availability, startup behavior, and limitations. This repository is an independent automation layer around that documented hotkey.
home-assistant/arrival-automation.yaml— example verified-arrival Home Assistant packagewindows/autohotkey/start-codex-voice.ahk— AutoHotkey v2 implementationwindows/powershell/Start-CodexVoice.ps1— PowerShell implementationdocs/SETUP.md— setup walkthroughdocs/SECURITY.md— safeguards and privacy considerationsdocs/TROUBLESHOOTING.md— common Windows focus and shortcut issues
- Windows 11 or a supported Windows version
- ChatGPT desktop app with Voice available for your plan and workspace
- A Voice keyboard shortcut configured in the app
- Home Assistant with a working presence entity
- One Windows automation path:
- AutoHotkey v2, or
- PowerShell plus a trusted remote execution mechanism
The repository does not provide a Windows HTTP listener or arbitrary remote-command server. The Home Assistant package is wiring for a separately configured, authenticated, encrypted trigger that can invoke only the reviewed Voice-start command.
Use at least two presence signals before starting Voice automatically:
- A person or phone enters
zone.home. - The same phone connects to trusted home Wi-Fi.
Also consider:
- Only running when the PC is unlocked
- A cooldown that prevents repeated launches
- A quiet-hours condition
- A manual enable/disable helper in Home Assistant
- Prompted mode before fully automatic mode
- In the ChatGPT desktop app, open Settings > Voice > Voice chat hotkey and assign a shortcut.
- Copy either the AutoHotkey or PowerShell script to the Windows PC.
- Pass the shortcut to the PowerShell script or set
voiceShortcutin the AutoHotkey script. - Test the Windows script manually.
- Add the Home Assistant automation.
- Replace the placeholder Windows command with your own trusted execution method.
See docs/SETUP.md for details.
- Window titles, app identifiers, and shortcut behavior may change between app releases.
- Windows may block microphone use while locked.
- The app may need to be running and signed in.
- Only one Voice chat can be active in the desktop app at a time.
- A task that did not begin in Voice mode may offer dictation rather than a full Voice conversation.
- Focus-stealing protections can prevent synthetic shortcuts from reaching the intended window.
- This proof of concept has not yet been validated on physical hardware by the original author.
Hardware reports are welcome. Please include:
- Windows version
- ChatGPT/Codex app version
- Launch method used
- Whether the PC was locked or unlocked
- Whether the shortcut opened a full Voice session
- Any focus, microphone, or timing problems
This is an independent community project. It is not affiliated with or endorsed by OpenAI or Home Assistant. Use local automation carefully and review every script before enabling remote execution.
MIT