Description
While using OpenCode with the oh-my-openagent plugin, I repeatedly got this warning toast inside the TUI:
⚠️ Provider Cache Missing
Model filtering disabled. RESTART OpenCode to enable full functionality.
The important part is that this happened even though providers were already authenticated and even after a full restart.
In my case the configured/authenticated providers were:
- OpenAI (oauth)
- OpenCode Go (api)
- GitHub Copilot (oauth)
At the time the warning was shown, oh-my-openagent could not see a connected-provider cache yet. Later, without changing authentication, ~/.cache/oh-my-opencode/connected-providers.json was eventually created and contained:
{
"connected": [
"opencode-go",
"openai",
"github-copilot",
"opencode"
],
"updatedAt": "2026-04-05T10:36:19.218Z"
}
So the system eventually recognized the connected providers, but not reliably during the earlier startup/session state that plugin consumers depend on.
From the plugin side, the warning is emitted when the connected-provider cache file does not exist yet. The cache is built from client.provider.list(), so this looks like an upstream timing/state problem where provider connectivity is not reliably available early enough (or not consistently persisted/observable across restarts).
Related context:
code-yeongyu/oh-my-openagent#1635 was triaged as upstream
#12698 looks related, but that issue is specifically about env vars set after initialization; this reproduction used already-authenticated oauth/api providers
Plugins
oh-my-openagent
OpenCode version
1.3.15
Steps to reproduce
- Install and configure
oh-my-openagent
- Authenticate providers (in my case: OpenAI oauth, OpenCode Go api, GitHub Copilot oauth)
- Launch
opencode
- Send a message in the TUI
- Observe the warning toast:
Provider Cache Missing
Model filtering disabled. RESTART OpenCode to enable full functionality.
- Fully restart OpenCode
- Observe that the warning can still persist across restart
- Later, in a subsequent session,
~/.cache/oh-my-opencode/connected-providers.json appears and contains the authenticated providers
Screenshot and/or share link
N/A
Operating System
Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 GNU/Linux
Terminal
xterm-256color (WSL)
Description
While using OpenCode with the
oh-my-openagentplugin, I repeatedly got this warning toast inside the TUI:The important part is that this happened even though providers were already authenticated and even after a full restart.
In my case the configured/authenticated providers were:
At the time the warning was shown,
oh-my-openagentcould not see a connected-provider cache yet. Later, without changing authentication,~/.cache/oh-my-opencode/connected-providers.jsonwas eventually created and contained:{ "connected": [ "opencode-go", "openai", "github-copilot", "opencode" ], "updatedAt": "2026-04-05T10:36:19.218Z" }So the system eventually recognized the connected providers, but not reliably during the earlier startup/session state that plugin consumers depend on.
From the plugin side, the warning is emitted when the connected-provider cache file does not exist yet. The cache is built from
client.provider.list(), so this looks like an upstream timing/state problem where provider connectivity is not reliably available early enough (or not consistently persisted/observable across restarts).Related context:
code-yeongyu/oh-my-openagent#1635was triaged as upstream#12698looks related, but that issue is specifically about env vars set after initialization; this reproduction used already-authenticated oauth/api providersPlugins
oh-my-openagent
OpenCode version
1.3.15
Steps to reproduce
oh-my-openagentopencodeProvider Cache MissingModel filtering disabled. RESTART OpenCode to enable full functionality.~/.cache/oh-my-opencode/connected-providers.jsonappears and contains the authenticated providersScreenshot and/or share link
N/A
Operating System
Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 GNU/Linux
Terminal
xterm-256color (WSL)