stop

Release the active voice session and stop the audio server when no other sessions are active.

2|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/cpoepke/claude-talk --skill stop-cpoepke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stop
Source: https://github.com/cpoepke/claude-talk/tree/main/skills/stop
Command: npx skills add https://github.com/cpoepke/claude-talk --skill stop-cpoepke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gracefully shutting down the active voice session can be error-prone and confusing for users. This Skill ensures the current voice chat session is released and the audio server is stopped when no other sessions remain.

Core Features & Use Cases

  • Graceful session release: stops the active voice session and, if it's the last one, shuts down the audio server.
  • User confirmation: communicates that the voice chat has stopped to the user.
  • Safe defaults: avoids accidental server shutdown when other sessions are active.

Quick Start

Run the stop command to gracefully release the current voice session and stop the audio server if no other sessions are active.

Frequently Asked Questions about stop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gracefully stop a voice chat session?

To gracefully stop a voice chat session, you can use a command that releases the active voice session and stops the audio server if no other sessions are active. It then confirms the termination to the user.

What happens to the audio server when I end a voice chat?

When you end a voice chat, the audio server is safely stopped only if no other voice sessions are currently active. This prevents accidental server shutdown while other sessions are still running.

How do I terminate a Claude Talk session safely?

To terminate a Claude Talk session safely, you apply a stop command during the ongoing session. This releases the current virtual environment and provides user-facing confirmation of the shutdown.

Do I need an active virtual environment to stop an audio server?

Yes, you need an active virtual environment to complete the workflow. The process requires an active session, a session release command, and user-facing confirmation to properly stop the audio server.

Why does shutting down a voice session fail or cause errors?

Shutting down a voice session can be error-prone if attempted manually without safe defaults. Using a dedicated stop command ensures the active session is released properly and prevents accidental shutdown of shared audio servers.

Can I stop the audio server without affecting other active sessions?

Yes, the stop mechanism includes safe defaults to avoid accidental server shutdown. It checks for other active sessions and only stops the audio server when the current voice chat is the last one remaining.