Fahh 🔊

Plays the "Fahh" meme sound automatically whenever code you run or debug in VS Code errors out. No configuration required — install it and it just works.

1. Install

Pick whichever matches how you got the extension.

Option A — from the Marketplace

Open VS Code.
Open the Extensions view (Cmd+Shift+X on macOS, Ctrl+Shift+X on Windows/Linux).
Search for Fahh.
Click Install on the extension by publisher sreekaran-reddy.
That's it — no reload needed, it activates automatically.

Option B — from a `.vsix` file

If you were given a fahh-sound-extension-x.y.z.vsix file directly:

Open the Extensions view (Cmd+Shift+X / Ctrl+Shift+X).
Click the ... menu in the top-right corner of the Extensions view.
Choose Install from VSIX....
Select the .vsix file.

Or from a terminal:

code --install-extension fahh-sound-extension-x.y.z.vsix

2. Verify it's working

Right after installing, confirm playback before you rely on it:

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P).
Run Fahh: Test Sound.
You should immediately hear the "Fahh" sound.

If you heard it, you're fully set up — skip to How it detects errors. If you didn't, see Troubleshooting below before doing anything else.

3. How it detects errors

Fahh listens for two kinds of failures and doesn't need any project-specific setup for either:

Running code in the integrated terminal (e.g. "Run Python File", node file.js, npm scripts, build tasks): it listens for the terminal's shell integration to report a non-zero exit code.
- Requires VS Code's shell integration, which is on by default for zsh, bash, fish, and PowerShell.
Run and Debug (F5): it attaches a Debug Adapter Protocol tracker and triggers on an uncaught exception (debugger stops with reason exception) or the debuggee process exiting with a non-zero code. This works across any debugger that speaks DAP — Node, Python/debugpy, Java, C++, and more.

It will not trigger on editor-only issues like red squiggly lint/type errors — only on an actual terminal run or debug session that fails.

4. Settings

Change these under Settings → Extensions → Fahh, or directly in your settings.json:

Setting	Type	Default	Description
`fahh.enabled`	`boolean`	`true`	Master on/off switch. Also toggled by the `Fahh: Toggle Enabled` command.
`fahh.soundPath`	`string`	`""`	Absolute path to a custom audio file. Leave empty to use the bundled `fahh.mp3`.
`fahh.cooldownMs`	`number`	`1500`	Minimum milliseconds between plays, so a burst of errors doesn't spam the sound.

Using a custom sound

Open Settings (Cmd+, / Ctrl+,) and search for fahh.soundPath.
Enter the absolute path to your own audio file (e.g. /Users/you/Sounds/my-sound.mp3 or C:\Sounds\my-sound.mp3).
Run Fahh: Test Sound again to confirm it picks up the new file.

5. Commands

Available from the Command Palette (Cmd+Shift+P / Ctrl+Shift+P):

Command	What it does
`Fahh: Test Sound`	Plays the sound immediately, ignoring the cooldown. Use this to sanity-check your setup.
`Fahh: Toggle Enabled`	Turns Fahh on/off without opening Settings.

6. Troubleshooting

No sound at all, even from Fahh: Test Sound:

Check fahh.enabled is true in Settings.
If you set fahh.soundPath, make sure the path is correct, absolute, and points to an existing audio file — a typo here fails silently into a warning notification, not a sound.
Check for a warning notification in the bottom-right corner right after running Fahh: Test Sound. It will tell you exactly what went wrong (missing file vs. no audio player found).
Check your system volume and that VS Code isn't muted.
Linux only: playback shells out to whatever CLI audio player is installed (mpg123, mpg321, aplay, paplay, cvlc, ...). On a minimal Linux install none of these may be present. Install one, e.g.:
```
sudo apt install mpg123
```
macOS (afplay) and Windows (bundled PowerShell/WPF playback) don't need anything installed — they should always work out of the box.

Fahh: Test Sound works, but it never plays on an actual error:

Confirm you're triggering one of the two supported cases from How it detects errors — a failing terminal command/task, or a failing Run and Debug (F5) session. A red squiggle from the linter alone won't trigger it.
For the terminal case, make sure shell integration is enabled (default in recent VS Code) and that you're using a supported shell (zsh, bash, fish, PowerShell).
Check you're not inside the fahh.cooldownMs window (default 1500ms) from a previous play — rapid repeated errors are intentionally throttled.

Still stuck: open the Output panel, select "Extension Host" from the dropdown, and look for anything mentioning fahh — that will show the underlying error.

7. Uninstall / disable

Temporarily disable: run Fahh: Toggle Enabled, or set fahh.enabled to false.
Uninstall: open the Extensions view, find Fahh, click the gear icon, and choose Uninstall.

8. Building from source

git clone <this repository>
cd fahh-sound-extension
npm install
npm run compile

Then press F5 in VS Code to launch an Extension Development Host with Fahh loaded, or package it yourself:

npx vsce package

License

MIT

Fahh

Sreekaran Reddy