OpenCode
How Flow loads its plugin into OpenCode and what each dot means.
There is nothing to set up. Run opencode in a Flow terminal and the dot follows the session.
What Flow passes
OpenCode has no hooks, but it loads plugins, and it adds the plugins named in the OPENCODE_CONFIG_CONTENT environment variable to the ones in your config. Flow starts opencode with that variable naming a plugin inside the Flow app. The plugin listens to OpenCode’s events and reports them to Flow with flw event.
Flow does not read or write ~/.config/opencode. Your own plugins still load.
Your own OPENCODE_CONFIG_CONTENT
If you already set OPENCODE_CONFIG_CONTENT, Flow keeps your JSON and adds its plugin to your plugin list. If Flow cannot read your value, it starts OpenCode with your value alone and no Flow plugin, and OpenCode reports the problem.
What each dot means
| Dot | OpenCode |
|---|---|
| Blue, pulsing | The session is busy, or a tool is running |
| Yellow | OpenCode is asking for permission or asking you a question |
| Green | The session went idle while you were looking elsewhere |
The notification for a yellow dot says “Needs permission” for a permission request and “Waiting for your input” for a question. The notification for a green dot shows OpenCode’s last response. A session error shows up as a notification with the error message.
Subagent sessions do not change the dot.