#Logfile with Docker

1 messages Β· Page 1 of 1 (latest)

polar ore
#

Hey! Quick question about logging: Is there a way to disable agent responses and tool call summaries (the πŸ› οΈ/πŸ“–/πŸ”Œ icons with output) from appearing in the Docker logs?

I've set logging.consoleLevel: "silent" but the agent/tool summaries still appear in stdout/stderr, which gets logged by Docker. This floods the logs and causes unnecessary SSD writes.

Is there a hidden config option or should we filter at the Docker level with grep? Thanks! 🦞

near galleonBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> βœ… Mark Solution

uneven meteorBOT
# polar ore Hey! Quick question about logging: Is there a way to disable agent responses and...

Based on my investigation of the codebase, here's what I found:

The short answer: There's no hidden config option to disable agent responses and tool summaries. The logging.consoleLevel: "silent" setting only controls the structured logging output (stdout/stderr via the logging system), but tool summaries (πŸ› οΈ/πŸ“–/πŸ”Œ) and agent responses go through the message delivery system, not the logging system.

Why they still appear:

  • Tool summaries are formatted by formatToolAggregate() in src/auto-reply/tool-meta.ts
  • They're sent via the onToolResult callback β†’ dispatcher.sendToolResult() β†’ deliver() function
  • This bypasses the logging system entirely, so consoleLevel: "silent" has no effect

Your options:

  1. Filter at Docker level with docker logs <container> 2>&1 | grep -v "πŸ› οΈ\|🧠\|πŸ“–\|πŸ”Œ" - this is the practical solution today
  2. Request a feature - A new config like logging.suppressToolOutput: true would need to be implemented to control this at the source

Relevant docs: