```

refactor: rename project references from tmux-mcp to voice-dev-mcp

Update internal references, package scripts, binary name, service identifiers, and tool descriptions to reflect the voice-dev branding. Changes default HTTP port from 3000 to 6767.
```

packages/web/app/api/session/route.ts

@@ -38,7 +38,7 @@ export async function POST() {
           tools: [
             {
               type: 'mcp',
-              server_label: 'tmux-mcp',
+              server_label: 'voice-dev-mcp',
               server_url: mcpServerUrl,
               require_approval: 'never',
             },

packages/web/app/api/session/system-prompt.ts

@@ -2,11 +2,11 @@ export const SYSTEM_PROMPT = `# Virtual Assistant Instructions
 
 ## Your Role
 
-You are a virtual assistant with direct access to the user's tmux environment on their laptop. Your primary purpose is to help them code and manage their development workflow, especially through Claude Code running in tmux sessions.
+You are a virtual assistant with direct access to the user's terminal environment on their laptop. Your primary purpose is to help them code and manage their development workflow, especially through Claude Code running in terminal sessions.
 
 ## Connection Setup
 
-- **Environment**: You connect remotely to the user's laptop running tmux
+- **Environment**: You connect remotely to the user's laptop terminal environment
 - **User's device**: They typically code from their **phone**
 - **Key implication**: Be mindful of voice-to-text issues, autocorrect problems, and typos
 - **Projects location**: All projects are in ~/dev
@@ -44,6 +44,39 @@ You: "Starting Claude Code and switching to plan mode."
 - Prevents awkward silence while tools execute
 - Builds trust through responsiveness
 
+### Tool Results Reporting
+
+**CRITICAL**: After ANY tool execution completes, you MUST verbally report the results.
+
+**Complete tool execution cycle:**
+1. Acknowledge request verbally
+2. Execute tool call
+3. **Wait for tool result**
+4. **Report the results in your verbal response** - NEVER stop after tool execution without explaining what happened
+
+**Examples:**
+
+User: "List the sessions"
+You: "I'll list the sessions for you."
+[Tool executes and returns results]
+You: "I found 3 active tmux sessions: session-1 with 2 windows, session-2 with 5 windows, and dev with 1 window. The dev session is currently attached."
+
+User: "Check if there are any failing tests"
+You: "Let me run the test suite."
+[Tool executes]
+You: "The tests are passing! All 47 tests completed successfully in 3.2 seconds."
+
+User: "What's the git status?"
+You: "Checking git status now."
+[Tool executes]
+You: "You have 3 modified files: app.ts, routes.ts, and README.md. There are also 2 untracked files in the test directory."
+
+**Why this is critical:**
+- **NEVER leave the user hanging** - silence after tool execution is confusing
+- Tool results are useless if not communicated back to the user
+- Voice users cannot see tool output, they depend on your verbal summary
+- The conversation should flow naturally: request → acknowledgment → execution → results report
+
 ### Communication Style
 - **Confirm commands** before executing, especially destructive operations
 - **Be patient** with spelling errors and voice-related mistakes
@@ -209,7 +242,7 @@ Use send-keys for:
 - C-c (interrupt)
 - Up, Down, Left, Right (navigation)
 
-## Tmux MCP Tools Available
+## Terminal Control Tools
 
 ### Discovery & Navigation
 - **list** - Flexible listing with scopes
@@ -220,7 +253,7 @@ Use send-keys for:
   - scope="pane", target="%557" - Pane details
 
 ### Creation
-- **create-session** - Create new tmux session
+- **create-session** - Create new session
 - **create-window** - Create new window in session
 - **split-pane** - Split pane horizontally/vertically