Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Herapheri Terminal SoundsNew to Visual Studio Code? Get it now.
Herapheri Terminal Sounds

Herapheri Terminal Sounds

sjoshi

|
1 install
| (1) | Free
Plays Herapheri-style audio when integrated terminal commands succeed or fail. Add success-1.mp3, success-2.mp3, error-1.mp3, error-2.mp3 under media/herapheri/ or set paths in settings.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Herapheri Terminal Sounds

Plays fun audio when commands in the integrated terminal finish: one random clip on success (exit code 0) and another on failure (non-zero exit code). Built on VS Code shell integration (VS Code 1.93+).

Try it locally

  1. Open this folder in VS Code or Cursor.
  2. Run Run → Start Debugging (or F5) — an Extension Development Host window opens.
  3. In that window, open the integrated terminal and run:
    • true or exit 0 → success sound
    • false or exit 1 → error sound
  4. From the Command Palette (⇧⌘P / Ctrl+Shift+P):
    • Herapheri: Play test success sound
    • Herapheri: Play test error sound

If nothing plays, confirm Terminal › Integrated › Shell Integration is enabled (default on current VS Code).

Install from a .vsix

code --install-extension herapheri-sounds-0.2.0.vsix

(Adjust the filename to match the version you built.)

Build the package:

npm install
npm run package

Settings

Search for herapheri in Settings, or edit settings.json:

Setting Purpose
herapheri.enabled Turn sounds on/off
herapheri.successSounds Optional: absolute paths to success clips (overrides bundled files)
herapheri.errorSounds Optional: absolute paths to error clips
herapheri.playOnUnknownExitCode Play error sound when exit code is unknown (e.g. Ctrl+C)

Bundled defaults (if settings are empty) are:

  • media/herapheri/success/success-1.mp3, success-2.mp3
  • media/herapheri/error/error-1.mp3, error-2.mp3

Publish to the Visual Studio Marketplace

  1. Publisher — Create one at Azure DevOps and register a VS Code publisher. Your publisher id is the short id in the Marketplace manage UI (not your personal user id).

  2. Personal Access Token (PAT) — In Azure DevOps: User settings → Personal access tokens → create a token with scope Marketplace → Manage.

  3. In package.json, set "publisher" to that id (replace your-publisher). Optionally set repository.url to your real GitHub repo.

  4. From the project folder, log in once per machine (paste the PAT when asked):

    cd /path/to/vscode-shahrukh
    npx @vscode/vsce login YOUR_PUBLISHER_ID
    
  5. Publish:

    npm run publish:marketplace
    

    This runs a check that you changed "publisher" away from the placeholder. For later releases, bump "version" in package.json (or run npx vsce publish patch / minor / major).

Full detail: Publishing extensions.

Redistribution of audio

If you ship movie, TV, or other third-party audio inside the extension, you are responsible for having the rights to redistribute it. The Marketplace may remove extensions that violate copyright. For a public listing, use audio you own or have properly licensed.

License

MIT — see LICENSE.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft