You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Excessive Informational Logging Clutters Log Files in Default Configuration #5004
OpenCode installed via curl script in a containerized setup.
Server running locally using opencode with default log settings.
Steps to Reproduce
Start the OpenCode server with opencode.
Observe the generated log file for entries during initialization.
Expected Behavior
Log files should contain only essential informational messages, avoiding redundant or low-value entries that clutter the output, particularly during routine operations such as configuration loading.
Actual Behavior
Under default log settings, the log file is populated with repetitive and verbose informational messages, such as:
INFO 2025-12-03T01:34:05 +6ms service=config path=/home/node/.config/opencode/config.json loading
INFO 2025-12-03T01:34:05 +0ms service=config path=/home/node/.config/opencode/opencode.json loading
INFO 2025-12-03T01:34:05 +1ms service=config path=/home/node/.config/opencode/opencode.jsonc loading
INFO 2025-12-03T01:34:05 +203ms service=config path=/home/node/.config/opencode/opencode.jsonc loading
These messages appear multiple times for similar configuration paths, contributing to unnecessary spam.
Impact
This verbosity reduces the usability of log files for debugging and monitoring, as relevant information becomes obscured by redundant entries, potentially complicating issue resolution in production or development environments.
Suggested Resolution
Adjust the default logging level to suppress low-priority informational messages (e.g., configuration loading details) or introduce configurable verbosity options to allow users to filter such output.
The excessive INFO logging you're experiencing during configuration loading might benefit from coordinated fixes with the existing logging system issues.
In the spirit of calling out excellent engineering and design....
I've found that the Pi Coding Agent is more robust and, for me has none of the issues that I've encountered in OC, or has an elegant way to resolve them.... I'm dropping out of OC issues:
Activity
github-actions commentedon Dec 3, 2025
This issue might be related to existing logging issues. Please check:
The excessive INFO logging you're experiencing during configuration loading might benefit from coordinated fixes with the existing logging system issues.
taqtiqa-mark commentedon Dec 3, 2025
More spam:
taqtiqa-mark commentedon Feb 12, 2026
In the spirit of calling out excellent engineering and design....
I've found that the Pi Coding Agent is more robust and, for me has none of the issues that I've encountered in OC, or has an elegant way to resolve them.... I'm dropping out of OC issues: