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
Reduce log noise: models.dev refresh logs at INFO level during startup #10506
Both issues describe the same problem: INFO-level logs cluttering output during startup. You may want to check that issue for additional context or related solutions.
Feel free to ignore if your specific case is different.
As I see it, this is happening because the ModelsDev.refresh() is called on module initialization which is before Log.init() in packages/opencode/src/index.ts. The default log level, before Log.init() is called, is INFO, so those debug() calls will actually not be logged. This defeats the purpose of them being there and I think a more general fix is required.
Maybe moving the initial refresh() call into a its own init() function would be a better approach:
in packages/opencode/src/provider/models.ts wrap the initial call in:
To clarify this is not just a problem of amount of logs, this is preventing the use of opencode at least on macos, as it crashes the terminal ui entirely.
@padapada09 A temporary solution is to go to the release section and download an older version, such as 1.1.30, then run it once to initialize some configurations. After that, you can use version 1.1.36 without any issues.
Activity
github-actions commentedon Jan 25, 2026
This issue might be a duplicate of existing issues. Please check:
Both issues describe the same problem: INFO-level logs cluttering output during startup. You may want to check that issue for additional context or related solutions.
Feel free to ignore if your specific case is different.
yanosh-k commentedon Jan 25, 2026
As I see it, this is happening because the
ModelsDev.refresh()is called on module initialization which is beforeLog.init()inpackages/opencode/src/index.ts. The default log level, beforeLog.init()is called, isINFO, so those debug() calls will actually not be logged. This defeats the purpose of them being there and I think a more general fix is required.Maybe moving the initial
refresh()call into a its owninit()function would be a better approach:in
packages/opencode/src/provider/models.tswrap the initial call in:then in
packages/opencode/src/index.ts, load the module andinit()it after theLoghas been initialized in the cli middleware:ModelsDev.init()fix(core): only fail startup on actual errors
padapada09 commentedon Jan 25, 2026
I'm having this issue on a clean install on macos 26 with version 1.1.35. Haven't found a workaround yet.
padapada09 commentedon Jan 25, 2026
To clarify this is not just a problem of amount of logs, this is preventing the use of opencode at least on macos, as it crashes the terminal ui entirely.
yanosh-k commentedon Jan 25, 2026
I think a temp workaround would be to just suppress stderr, when launching opencode:
opencode 2>/dev/nullpadapada09 commentedon Jan 25, 2026
@yanosh-k I just tried it, it did not show the info log, but it also crash showing me a blank screen.
fix(core): only fail startup on actual errors (#202)
FischLu commentedon Jan 25, 2026
I tested it, and on macOS with opencode 1.1.36 this method doesn't work; nothing is displayed on the screen, and opencode won't start.
FischLu commentedon Jan 25, 2026
@padapada09 A temporary solution is to go to the release section and download an older version, such as 1.1.30, then run it once to initialize some configurations. After that, you can use version 1.1.36 without any issues.
vanyauhalin commentedon Jan 25, 2026
I am hittin this INFO message on every command. For example:
The
--log-levelflag does not help:alloyapple commentedon Jan 25, 2026
When I open opencode, it show following message:
INFO 2026-01-25T22:31:08 +55ms service=models.dev file={} refreshing INFO 2026-01-25T22:31:09 +52ms service=models.dev file={} refreshingrekram1-node commentedon Jan 26, 2026
this is fixed in next release