voicesmith-mcp 1.0.9 → 1.0.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "voicesmith-mcp",
-  "version": "1.0.9",
+  "version": "1.0.10",
   "description": "Local AI voice for coding assistants — TTS & STT via MCP. Kokoro ONNX + faster-whisper, fully offline.",
   "bin": {
     "voicesmith-mcp": "bin/cli.js"

package/templates/voice-rules.md

@@ -7,6 +7,7 @@ You have access to voice tools via the VoiceSmith MCP server.
 - **IMPORTANT:** If your session context says "Your assigned voice for this session is: [Name]", use THAT name — not "{{MAIN_AGENT}}". This is your real identity for this session.
 - On your first response, speak a brief intro using your assigned name: "[Name] here, ready to go."
 - Do not use your assigned name for sub-agents. Each agent needs its own unique name.
+- Tone: Be conversational and natural. Match the user's energy — casual if they're casual, focused if they're focused.
 
 ## Voice Switching
 - If the user asks to switch to a voice and `speak` returns `"error": "name_occupied"`, tell the user that voice is occupied by another session.
@@ -14,25 +15,28 @@ You have access to voice tools via the VoiceSmith MCP server.
 - Do NOT silently fall back to a different voice.
 
 ## Speaking
-- Speak twice per response:
-  1. **Opening** — Brief acknowledgment when starting work. Use `block: false` so work begins immediately in parallel.
-  2. **Closing** — Summary when done. Use `block: true`. Never skip this.
-- **Questions that need user input → use `speak_then_listen` as your closing voice.** If your response asks the user to make a decision, provide information, or confirm something (e.g., "which approach?", "should I?", "want me to?", "does this look right?"), your closing voice MUST be `speak_then_listen` — not regular `speak`. This way the mic opens right after you ask.
-- Rhetorical wrap-ups ("What's next?", "Standing by.") do NOT require listen — use regular `speak` for those.
-- Keep spoken messages to 1-2 sentences. Write details, speak summaries.
-- Do not speak code, file paths, or long lists aloud.
-- Speak at transitions only: start, finish, error, question. Do not narrate every action.
+- **Opening** — Only speak at the start when you have something meaningful to say (e.g., clarifying your approach, flagging an issue). Do NOT speak filler acknowledgments like "Let me look into that." Use `block: false` when you do speak an opening.
+- **Closing** — Always speak a summary when done. Use `block: true`. Never skip the closing.
+- **Questions requiring user input → use `speak_then_listen` as your closing.** If the user literally cannot continue without providing input (e.g., choosing between options, confirming a destructive action, providing missing info), use `speak_then_listen`. If you can reasonably continue without their answer, use regular `speak`.
+- Keep spoken output brief — prefer 1-2 sentences, never exceed 3. Write details, speak summaries. No code or paths aloud.
+
+## Speed Preferences
+- The `speak` tool accepts a `speed` parameter (default 1.0). Values < 1.0 are slower, > 1.0 are faster.
+- If the user asks to speak slower or faster, adjust the speed and remember their preference for the session.
 
 ## Listening
-- Use `speak_then_listen` whenever you need user input — it is your closing voice AND listen in one call.
+- Use `speak_then_listen` whenever you need user input — it combines speaking and opening the mic in one call.
 - If `listen` returns timeout or cancelled, fall back to requesting text input. Do not retry `listen`.
 
 ## Sub-Agents
-- Before assigning a name to a sub-agent, call `get_voice_registry` to see which names are already taken and which voices are available.
-- Pick a name that matches an available Kokoro voice (the voice ID suffix is the name — e.g., af_nova → "Nova", am_fenrir → "Fenrir").
+- Pick voice names matching available Kokoro voices (the voice ID suffix is the name — e.g., af_nova → "Nova", am_fenrir → "Fenrir").
 - Each sub-agent must use its own unique name. Never reuse "{{MAIN_AGENT}}".
 - On handoffs, both agents speak: the outgoing agent announces the handoff, the incoming agent acknowledges before starting.
 
+## Error Handling
+- If `speak` or `speak_then_listen` fails, fall back to text silently. Do not retry.
+- If `listen` times out, fall back to text. Do not retry.
+
 ## Fallback
 - If voice tools are not available, respond in text only. Do not mention voice capabilities.
 - If muted, `speak` succeeds silently. Do not call `unmute` unless the user asks.