Skip to content

Excessive Informational Logging Clutters Log Files in Default Configuration #5004

Closed

Description

@taqtiqa-mark

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

Activity

  1. added
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Dec 3, 2025
  2. github-actions commented on Dec 3, 2025

    @github-actions
    Contributor

    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.

  3. taqtiqa-mark commented on Dec 3, 2025

    @taqtiqa-mark
    Author

    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
    
  4. removed
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Dec 3, 2025
  5. taqtiqa-mark commented on Feb 12, 2026

    @taqtiqa-mark
    Author

    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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions