anomalyco / anomalyco/opencode
[Bug] OpenCode Web shows "No folders found" although projects are returned by the backend API
@Hona is already working on this.
Since Jul 30, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
When running opencode web, the Web UI starts successfully and is accessible in the browser.
However, the home page and the Open Project dialog both show "No folders found", even though the backend already returns all projects correctly.
The issue appears to be on the Web UI side because:
/projectreturns all existing projects (17 projects in my case)/sessionreturns existing sessions- All requests return HTTP 200
- The UI still shows an empty project list
Server log also prints:
Failed to initialize fff
Failed to init file picker: Can not run certain FFF features in a file system root or home directories. Consider smaller per-project directories.
### Additional information
The backend appears to work correctly.
`GET /project` returns existing projects, for example:
```json
[
{
"worktree": "/Users/.../Documents/GitHub/openclaw"
},
{
"worktree": "/Users/.../Documents/GitHub/unified-agentic-os"
}
]
The local database also contains projects:
SELECT COUNT(*) FROM project;
17
The issue seems to be that the Web UI does not render the projects even though they are successfully returned by the backend.
Plugins
None
OpenCode version
1.18.9
Steps to reproduce
- Start OpenCode Web
opencode web
-
Open the Web UI in the browser.
-
Observe that the home page and the Open Project dialog display "No folders found".
-
Open DevTools → Network.
-
Observe that the
projectrequest returns HTTP 200 and contains all existing projects, but none are rendered in the UI.
Screenshot and/or share link
Operating System
macOS Sequoia 15.x (Intel)
Terminal
iTerm2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.