anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Excessive Informational Logging Clutters Log Files in Default Configuration #3268

New Issue
Closed
opened 2026-02-16 17:39:25 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:39:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @taqtiqa-mark on GitHub (Dec 2, 2025).

Description

Environment

  • OpenCode installed via curl script in a containerized setup.
  • Server running locally using opencode with default log settings.

Steps to Reproduce

  1. Start the OpenCode server with opencode.
  2. 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.

OpenCode version

v1.0.128

Steps to reproduce

See above

Screenshot and/or share link

NA

Operating System

Linux (Debian Testing)

Terminal

Alacritty+Zellij

Originally created by @taqtiqa-mark on GitHub (Dec 2, 2025). ## Description ### Environment - OpenCode installed via curl script in a containerized setup. - Server running locally using `opencode` with default log settings. ### Steps to Reproduce 1. Start the OpenCode server with `opencode`. 1. 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. ### OpenCode version v1.0.128 ### Steps to reproduce See above ### Screenshot and/or share link NA ### Operating System Linux (Debian Testing) ### Terminal Alacritty+Zellij
yindo added the bug label 2026-02-16 17:39:25 -05:00
yindo closed this issue 2026-02-16 17:39:25 -05:00
yindo commented 2026-02-16 17:39:26 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 2, 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.

@github-actions[bot] commented on GitHub (Dec 2, 2025): This issue might be related to existing logging issues. Please check: - #4999: [Log File Deleted When Multiple IDE Instances Are Attached to OpenCode Server](https://github.com/sst/opencode/issues/4999) - While this addresses a different problem (log file deletion), it's part of the broader logging system that also generates the verbose output reported here. The excessive INFO logging you're experiencing during configuration loading might benefit from coordinated fixes with the existing logging system issues.
yindo commented 2026-02-16 17:39:26 -05:00
Author
Owner
Copy Link
Copy Source

@taqtiqa-mark commented on GitHub (Dec 2, 2025):

More spam:

INFO  2025-12-03T02:03:23 +2ms service=bus type=message.updated publishing
INFO  2025-12-03T02:03:32 +8981ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +8ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +28ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +2ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +1ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +84ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +4ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +6ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +2ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:32 +6ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +221ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +10ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +2ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +0ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +0ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +23ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +7ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +77ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +7ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +2ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +4ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +14ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +63ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +40ms service=bus type=message.part.updated publishing
INFO  2025-12-03T02:03:33 +41ms service=bus type=message.part.updated publishing
@taqtiqa-mark commented on GitHub (Dec 2, 2025): More spam: ``` INFO 2025-12-03T02:03:23 +2ms service=bus type=message.updated publishing INFO 2025-12-03T02:03:32 +8981ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +8ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +28ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +2ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +1ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +84ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +4ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +6ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +2ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:32 +6ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +221ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +10ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +2ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +0ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +0ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +23ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +7ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +1ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +77ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +7ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +2ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +4ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +14ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +63ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +40ms service=bus type=message.part.updated publishing INFO 2025-12-03T02:03:33 +41ms service=bus type=message.part.updated publishing ```
yindo commented 2026-02-16 17:39:26 -05:00
Author
Owner
Copy Link
Copy Source

@taqtiqa-mark commented on GitHub (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:

@taqtiqa-mark commented on GitHub (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: - [Pi Coding Agent](https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent) - [Overview](https://mariozechner.at/posts/2025-11-30-pi-coding-agent/) - [Example development session](https://www.youtube.com/watch?v=ANQ1IYsFM2s)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#3268
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?