dogierror

A short sound when a new code error appears. Keep your attention on the editor, with a quick mute switch when you need quiet.

Features

• Randomly plays one of three bundled voice clips for new error diagnostics. Warnings, hints, and information stay silent.
• Starts playback as soon as VS Code reports a new error, with no added debounce delay by default. A cooldown prevents repeated alerts.
• Tracks error messages and codes, so moving an unchanged error to another line does not replay the sound.
• Listens to the active editor by default. You can enable alerts across the workspace.
• Provides a status bar on/off toggle, a test command, and a local sound picker.
• Runs locally, with no telemetry, network requests, or runtime npm dependencies.
• Works alongside ErrorLens without requiring it to be installed.

Get started

1. Install the extension in desktop VS Code.
2. Open the Command Palette and search for dogierror. Run the test sound command to check your audio output.
3. Create a new error in a file supported by your language extension.
4. Click dogierror in the status bar to turn automatic alerts off or on.

The extension reacts to errors reported in VS Code's Problems system. It does not analyze code itself or listen to arbitrary terminal output. Errors already present when the extension starts are treated as a silent baseline.

Using ErrorLens

You can enable ErrorLens and dogierror together. ErrorLens displays diagnostics inline; dogierror plays a sound for new error diagnostics. Both use VS Code's diagnostics, and neither needs the other to be installed.

ErrorLens's display filters do not control dogierror. Hiding a message in ErrorLens does not mute the corresponding error alert. dogierror uses its own active-editor, focus, cooldown, and mute settings. Warnings, hints, and information stay silent even if ErrorLens displays them.

For the fastest response, set dogierror.debounceMs to 0. That removes dogierror's deliberate wait; the language extension still needs time to detect and report the error, and the operating system's audio player still needs time to start. Existing nonzero user settings remain in effect until changed.

Commands

Search for dogierror in the Command Palette.

Settings

All settings apply at the user level. A repository cannot select a sound file through its workspace settings.

Automatic alerts play only while the VS Code window is focused. Events suppressed while muted, outside the active editor, during cooldown, or while another clip plays are not queued for later playback. Only one sound plays at a time. Immediate handling does not bypass the three-second default cooldown or interrupt a playing clip.

Custom sounds

The bundled clips are Haluh ka!, Tanginang lala, and Anong ginagawa mo sa buhay mo. Selection is random; consecutive repeats can occur. The clips include strong language. Audio provenance is documented in media/NOTICE.md.

Use the sound picker or set dogierror.soundPath in User Settings. Choose an uncompressed mono or stereo PCM .wav file no larger than 10 MiB. Short clips work best; playback stops after 30 seconds. MP3 and other compressed formats must be converted to PCM WAV first. Use a local path on the computer running VS Code, even when editing a remote workspace.

Platform support

The extension runs beside the desktop UI, including when using a remote workspace. Browser-based VS Code is not supported. Linux and Windows playback paths have automated simulation coverage; native playback should be checked on each platform before a public release.

Troubleshooting

If the test command is silent, check your system output device and volume. For a custom file, confirm that it is PCM WAV rather than an MP3 renamed to .wav. On Linux, confirm that paplay or aplay is available in your PATH.

If test playback works but editing is silent, check that alerts are on, the editor is focused, and VS Code reports an error, rather than a warning. Wait for both the cooldown and the current clip to finish before introducing another error. If alerts feel delayed, set dogierror.debounceMs to 0; detection time in the language extension and audio-player startup time still apply.