vibeaudio 0.22.0 → 0.24.0

package/README.md

@@ -442,17 +442,19 @@ Then `/reload-plugins` or a new session; `/plugin` shows `1 mod active`.
 /vibeaudio genre jazz    also: volume <n>, music on|off, speak off|auto|always, notify on|off, stop
 /vibeaudio genre zen here   genre, volume and music also take "here": save for this project only
 /vibeaudio card          make your week card; the pane shows it in terminals that draw images
-/vibeaudio strip on      an always-visible line above the prompt (off by default; strip off removes it)
+/vibeaudio strip on      an always-visible logo band above the prompt (off by default; strip off removes it)
+/vibeaudio usage on      add context fill and plan limits (ctx 42%  5h 31%) to the band (off by default; usage off removes it)
 /vibeaudio doctor        the setup check in a pane, each problem with its fix (vibe --doctor)
+/vibeaudio help          every command on one line, and the "here" option
 ```
 
-While you are muted, a line above the prompt says how many minutes are left, so a forgotten mute does not look like a broken tool. Nothing else is shown unless you turn the strip on.
+The pane is four cards under a logo header with a status pill (Playing, Ready, Muted or Music off): Now playing, Sound, Alerts and Share, which holds your last 7 days as a small chart and the week card buttons. Its colours come from the site and adapt to your Claude Code theme, light or dark. While you are muted, a line above the prompt says how many minutes are left, so a forgotten mute does not look like a broken tool. Nothing else is shown unless you turn the strip on.
 
-The optional **strip** (`/vibeaudio strip on`, remembered across sessions) keeps one line above the prompt: the genre and volume, **Mute** and **Controls** buttons, and what your other agents are doing (`api waiting, web working`, in yellow when one needs you). It runs `vibe --state` every 5 seconds while it is on, and not at all while it is off. Tab to it with Ctrl+X then Tab.
+The optional **strip** (`/vibeaudio strip on`, remembered across sessions) puts the VibeAudio logo above the prompt, three level bars that move while music is playing (an SVG on the Desktop app, text bars in the terminal). Next to it: the genre and volume, your last 7 days as the week card counts them (turns and time waited, read from `~/.vibeaudio/history.jsonl`), and what your other agents are doing (`api waiting, web working`, in yellow when one needs you). The buttons are **Mute**/**Unmute**, **Music**, **Genre >** (the next genre), **Vol -**, **Vol +**, **Week card** (makes the share card, then **Open card**) and **Controls**. In a short window it shrinks to one line. It runs `vibe --state` every 5 seconds and redraws the text bars twice a second only in the terminal, while it is on and music is playing; on the Desktop app the SVG animates itself, so only the level bars inside the headphones move. Tab to it with Ctrl+X then Tab. With `/vibeaudio usage on` it also shows how full the context window is and, on a Claude plan, your 5-hour and 7-day limits, turning the warning colour at 80%; it reads the same figures Claude Code's status line has, and nothing else. While Claude works, the spinner also says what is playing (`· ♪ jazz…`, or `· ♪ muted`).
 
 - **Per project.** The pane's **Saving** button switches genre, volume and music between everywhere and this project, and the pane notes when this folder has its own settings (`vibe --genre zen --here`, found from a subfolder the way the CLI does). There is no way to remove a project's settings yet, in the mod or the CLI.
 - **It changes nothing itself.** Every action runs the `vibe` command with a fixed argument list (no shell), so settings stay in `~/.vibeaudio/config.json` and the pane cannot disagree with the CLI. The one thing it keeps for itself is whether the strip is on, in Claude Code's own store for the mod. It needs `vibe` on your `PATH` (`npm i -g vibeaudio`) and **Claude Code 2.1.287 or later** (Desktop app 2.1.286). It draws in the terminal and the Desktop app; in the VS Code panel and `claude -p` the same commands answer in text. It makes no network request.
-- **A mod is code, not configuration.** It runs inside Claude Code with your permissions and is not sandboxed, which is why `--install-hooks` never installs it for you. Read it first: it is [`mods/vibe/hooks/register.js`](mods/vibe/hooks/register.js), and `claude plugin validate mods/vibe` lists every call it makes (it reads two files in `~/.vibeaudio/`, runs `vibe`, and draws).
+- **A mod is code, not configuration.** It runs inside Claude Code with your permissions and is not sandboxed, which is why `--install-hooks` never installs it for you; it prints the two commands until Claude Code lists the mod as installed. Read it first: it is [`mods/vibe/hooks/register.js`](mods/vibe/hooks/register.js), and `claude plugin validate mods/vibe` lists every call it makes (it reads three files in `~/.vibeaudio/` (`config.json`, `muted`, `history.jsonl`), your Claude Code theme, the session's usage figures (only with `usage on`), runs `vibe`, and draws).
 - **`/vibe` stays.** It works on every Claude Code version and surface; the mod is the faster path where it loads. Remove the mod with `claude plugin uninstall vibeaudio-mod@vibeaudio`.
 
 ### Changing the sound later
@@ -874,7 +876,7 @@ The full order, highest first: **a flag** → **an environment variable** → **
 | `--announce <text>` | Play the chime for something that isn't an agent (CI, a deploy, a script), then exit. Add `--outcome success\|failure\|attention` or `--exit-code $?` | `success` |
 | `--stop` | Stop the background player, then exit | — |
 | `--mute [minutes]` | Silence everything for a call, then exit | `60` min (`0` = until unmuted) |
-| `--unmute` | Resume normal playback, then exit | — |
+| `--unmute` | Resume normal playback, then exit; a turn still running gets its music back at once | — |
 | `--clear-cache` | Delete all cached audio, then exit | — |
 | `--mcp` | Run as an MCP stdio server for desktop apps | — |
 | `--install-hooks` | Wire music into your agent's hooks (no wrapper needed) | — |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vibeaudio",
-  "version": "0.22.0",
+  "version": "0.24.0",
   "description": "Procedural focus music while your AI coding tools (Claude Code, Codex, Cursor, Grok, Gemini, Copilot) think — a different arrangement per project.",
   "bin": {
     "vibeaudio": "bin/vibeaudio.js",

package/src/cli.js

@@ -777,6 +777,7 @@ function installHookTargets(ids, genre, volume, reactive, dryRun = false, typed
       const slash = hooks.installSlashCommand({ dryRun });
       if (!slash.installed) console.log(`  \x1b[33m/vibe not installed: ${slash.reason} (${slash.file})\x1b[0m`);
       else console.log(`  ${"/vibe".padEnd(19)}→ ${dryRun ? "would write" : "control the music from inside Claude Code"} (${slash.file})`);
+      if (!dryRun && !hooks.modInstalled()) console.log(`  \x1b[2mOptional: /plugin marketplace add kiril6/vibeaudio, then /plugin install vibeaudio-mod@vibeaudio - instant /vibeaudio controls, a pane and a band above the prompt.\x1b[0m`);
     }
     // Codex will not run a hook it has not been told to trust, so saying
     // "done" without this would be reporting an install that isn't live yet.
@@ -1903,7 +1904,9 @@ async function run() {
 
     if (!muteChange) {
       setMuted(false);
-      console.log(`\x1b[32m🔊 Unmuted.\x1b[0m Music returns on your next prompt.\n`);
+      // A turn already running gets its music back now; only an idle machine waits for a prompt.
+      const resumed = require("./hooks").resumeAfterUnmute(genre, volume, { music, follow: typed.volume === undefined });
+      console.log(`\x1b[32m🔊 Unmuted.\x1b[0m ${resumed ? "Music is back." : "Music returns on your next prompt."}\n`);
       return;
     }
 

package/src/hooks.js

@@ -1387,6 +1387,19 @@ function hookResume(raw, genre, volume, { reactive = false, follow = false, musi
   return true;
 }
 
+/**
+ * An unmute while a turn is in flight: a mute stopped the player, and nothing
+ * else would start one until the next prompt. Only for a session that is
+ * working (a waiting one is waiting on the user, and says so with silence), and
+ * never over a daemon already playing. Not reactive: that flag lives in the hook
+ * commands, so a reactive install is plain until its next tool-driven resume.
+ */
+function resumeAfterUnmute(genre, volume, { music = true, follow = false } = {}) {
+  if (!music || daemonRunning() || working(listSessions()).length === 0) return false;
+  spawnDaemon(genre, volume, false, follow);
+  return true;
+}
+
 /**
  * The agent's session is over (quit, /clear, logout). A turn cut off by it
  * never reaches Stop. Silent: nothing finished.
@@ -1641,6 +1654,11 @@ function slashCommandFile() {
   return path.join(claudeConfigDir(), "commands", "vibe.md");
 }
 
+// The optional in-app mod (mods/vibe). Claude Code records installed plugins by name in this file.
+function modInstalled(file = path.join(claudeConfigDir(), "plugins", "installed_plugins.json")) {
+  try { return fs.readFileSync(file, "utf8").includes("vibeaudio-mod"); } catch { return false; }
+}
+
 function slashCommandText() {
   const cli = `${shellQuote(process.execPath)} ${shellQuote(CLI_ENTRY)}`;
   return `---
@@ -1720,6 +1738,7 @@ function uninstallHooks(file = null, { id = "claude" } = {}) {
 module.exports = {
   shellQuote,
   claudeConfigDir,
+  modInstalled,
   codexHome,
   geminiDir,
   qwenHome,
@@ -1742,6 +1761,7 @@ module.exports = {
   hookTool,
   hookWait,
   hookResume,
+  resumeAfterUnmute,
   isStuck,
   STUCK_WINDOW,
   agentState,