FIX: If you are seeing {"error":"Web UI is temporarily unavailable."} after upgrading like me #1480
Richard-Sees
started this conversation in
General
Replies: 1 comment
|
There is more information I want to add if you're trying to get opencode to pull mimo. * it's important to understand that both opencode web and mimo serve will COMPETE for port 4096.
potential launch option if you are on linux: #!/bin/bash
pwa then points to: http://127.0.0.1:4097 for the set opencode web...you can update to whatever port is available if 4097 is taken. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Users upgrading from v0.1.0 (or earlier) expect mimo serve to continue launching the web UI. Instead, they receive {"error":"Web UI is temporarily unavailable."} with no indication that the web interface has moved to opencode web. This makes it appear as though the application is broken when it's actually a workflow/documentation change. Consider:
Mentioning the new command in the 503 response.
Printing a console message such as:
The Web UI has moved.
Launch it with:
opencode web
Calling this out prominently in the release notes and migration guide.
If this was already listed elsewhere, let me know - but I spent upwards of an hour trying to find it listed somewhere, and even having the help of other AI. Remember everyone, this is a fork of opencode - so this makes sense now. But on the positive side - looks like we can easily see the opencode free models now also without editing the config.
All reactions