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
The models command with the --standalone flag shows no models and exits with the code 0 #41071
The models command has a --standalone flag. The help text says that this flag starts a private server in place of the background service.
The command with this flag shows no models. The command writes no data to stdout. The command writes no data to stderr. The command exits with the code 0.
The same command without the flag shows 455 models.
The fault occurs for all providers. The fault occurs for the default providers and also for the custom providers.
The user gets no error message. Thus the user cannot see the cause of the fault.
Environment
opencode version: 0.0.0-next-16974 (next channel)
Operating system: macOS 25.5.0
Architecture: arm64
Installation method: npm
How to repeat the fault
Install opencode from the next channel.
Make sure that a minimum of one provider is available.
Run this command: opencode models
Count the lines of the output.
Run this command: opencode models --standalone
Count the lines of the output.
Result
Step 3 shows 455 models.
Step 5 shows 0 models. The exit code is 0. There is no error message.
Addressed by #41783. The server’s first model.list call now waits on the bounded plugin/catalog readiness barrier before reading models, so a cold standalone server cannot return HTTP 200 with an empty intermediate catalog. The regression starts a fresh server with a custom model, immediately requests /api/model, and verifies the model is present; timeout uses the existing explicit service-unavailable error. Closing as resolved on the v2 branch.
Activity
opencode-agent commentedon Aug 11, 2026
Addressed by #41783. The server’s first
model.listcall now waits on the bounded plugin/catalog readiness barrier before reading models, so a cold standalone server cannot return HTTP 200 with an empty intermediate catalog. The regression starts a fresh server with a custom model, immediately requests/api/model, and verifies the model is present; timeout uses the existing explicit service-unavailable error. Closing as resolved on the v2 branch.fix(opencode-local): fall back to the running shared service when --s…