Problem
The --verbose option currently controls the Pino logger, but several direct console.log calls in the message and GIF flows always print response fragments, transcripts, participant IDs, message text, and API results. This creates noisy production logs and can expose chat content when verbose diagnostics were not requested.
Expected behavior
Routine diagnostic output should be suppressed by default and enabled consistently with --verbose, while warnings and actionable errors remain visible.
Suggested direction
Use a small logger wrapper or the existing Pino logger for debug messages. Keep user-facing status messages and error logs at appropriate levels.
Acceptance criteria
- AI stream fragments, transcripts, participant-debug output, and raw GIF objects are not logged by default.
--verbose enables the useful diagnostic details.- Errors and warnings remain visible without verbose mode.
- Logs no longer expose more message content than necessary.
Problem
The
--verboseoption currently controls the Pino logger, but several directconsole.logcalls in the message and GIF flows always print response fragments, transcripts, participant IDs, message text, and API results. This creates noisy production logs and can expose chat content when verbose diagnostics were not requested.Expected behavior
Routine diagnostic output should be suppressed by default and enabled consistently with
--verbose, while warnings and actionable errors remain visible.Suggested direction
Use a small logger wrapper or the existing Pino logger for debug messages. Keep user-facing status messages and error logs at appropriate levels.
Acceptance criteria
--verboseenables the useful diagnostic details.