executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
cli-and-serverOperate speech-to-speech from the Python CLI, choosing serve, local, or talk safely and tuning server binding, audio, endpointing, live transcription, session capacity, and the command-level LLM proxy.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the task is to start or connect to the Python package, choose a command profile, expose the Realtime server, or diagnose command-level capacity and endpointing behavior.
speech-to-speech serve.speech-to-speech talk --url <full-endpoint>.speech-to-speech local; it is forced to loopback and accepts local audio
flags, not a public host.serve, talk, or local; use the command-specific
flags rather than mixing server and client options.serve on 127.0.0.1 unless a trusted network or an authenticated
gateway is already in place. Read server runtime
before using --host 0.0.0.0 or --enable_llm_proxy.--num_pipelines to the
number of concurrent sessions and watch for session_limit_reached.scripts/check_cli_profiles.py. It does not
download models or start a server.talk owns the full Realtime URL and audio-client options; it does not accept
server host/port, backend selectors, or pipeline flags.serve owns host/port and pipeline flags; it does not accept talk's
--url or local's --local_audio_* flags.local owns the loopback port and --local_audio_* flags; it rejects
--host and always connects to
ws://127.0.0.1:<port>/v1/realtime internally.--mode realtime and --mode local are temporary aliases
with a deprecation warning. Other old mode values are rejected; migrate to
the three-command family.Detailed flags, profiles, security notes, endpointing behavior, and failure handling are bundled in: