Problem
When using --daemon mode across multiple calls, it's easy to lose track of whether the daemon is currently active or not. The only indication is the absence of "Starting TTS server..." on subsequent calls, which is easy to miss.
Suggestion
Add a subtle indicator in the output showing daemon state, e.g.:
speak v0.1.0 (daemon: active)
Generating audio for 27 characters...
Or at minimum, show it when the daemon is already running:
speak v0.1.0
Generating audio for 27 characters...
→ Using running daemon
Context
This came up during agent usage where multiple speak calls are made in sequence. Without clear state indication, it's ambiguous whether:
- The daemon failed to start
- The daemon was already running
- The daemon died between calls
A clear indicator would help with debugging and general awareness of system state.
Problem
When using
--daemonmode across multiple calls, it's easy to lose track of whether the daemon is currently active or not. The only indication is the absence of "Starting TTS server..." on subsequent calls, which is easy to miss.Suggestion
Add a subtle indicator in the output showing daemon state, e.g.:
Or at minimum, show it when the daemon is already running:
Context
This came up during agent usage where multiple speak calls are made in sequence. Without clear state indication, it's ambiguous whether:
A clear indicator would help with debugging and general awareness of system state.