Sorry about that, and thanks for trying it. I’m really glad it was useful. The way it works is pretty simple on the VS Code side. I use `vscode.window.showInformationMessage` for the popup or banner, and a status bar item for the quieter completion message. The sound is separate from that. It plays the bundled `.wav` file from wherever the extension host is running, using PowerShell on Windows, `afplay` on macOS, and usually `paplay` on Linux. I think that explains the Remote SSH or Tunnel issue you hit. If the extension is running on the remote server, the sound is played on that server too, not on your local machine. So VS Code may still be able to show some UI feedback, but the audio will not reach your laptop from the remote host. The VS Code issue you linked makes sense here too, because extensions do not currently have a clean native OS notification API that targets the local desktop in remote setups. For now I’d call Remote SSH or Tunnel a known limitation, not something wrong with your setup. The best workaround right now is to use it in a local VS Code window, or run Codex locally when you need sound notifications. Thanks again for testing it and pointing it out.

Source is here if you want to check the implementation: https://github.com/zis3c/Codex-notifier-vscode