anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #7349] fix(app): show custom models without valid release_date in web UI mod… #12363

New Issue
Closed
opened 2026-02-16 18:17:16 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:17:16 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/7349

State: closed
Merged: Yes

Summary

Fix custom models not appearing in the web UI model selector.

Problem

Users who configure custom models (e.g., DeepSeek, OpenRouter, Aliyun) in their opencode.json can see and use all models in the TUI, but only a subset appears in the web UI. This inconsistency creates confusion and limits the web UI's usefulness.

Root Cause

The web UI model visibility logic filters models based on whether they belong to a "latest" set, which relies on release_date metadata. Custom models typically don't have a valid release_date, causing them to be filtered out by default.

Solution

Update the visible() function in packages/app/src/context/local.tsx to show models without a valid release_date by default. This ensures custom models are visible in the web UI while preserving the existing behavior for official models with proper metadata.

Before: Models without release_date → hidden by default
After: Models without release_date → shown by default

Testing

  • Configured custom models now appear in web UI model selector
  • Official models with release_date maintain their existing visibility behavior
  • User visibility preferences (show/hide) still take precedence

Fixes #6798

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/7349 **State:** closed **Merged:** Yes --- ## Summary Fix custom models not appearing in the web UI model selector. ## Problem Users who configure custom models (e.g., DeepSeek, OpenRouter, Aliyun) in their `opencode.json` can see and use all models in the TUI, but only a subset appears in the web UI. This inconsistency creates confusion and limits the web UI's usefulness. ## Root Cause The web UI model visibility logic filters models based on whether they belong to a "latest" set, which relies on `release_date` metadata. Custom models typically don't have a valid `release_date`, causing them to be filtered out by default. ## Solution Update the `visible()` function in `packages/app/src/context/local.tsx` to show models without a valid `release_date` by default. This ensures custom models are visible in the web UI while preserving the existing behavior for official models with proper metadata. **Before:** Models without `release_date` → hidden by default **After:** Models without `release_date` → shown by default ## Testing - Configured custom models now appear in web UI model selector - Official models with `release_date` maintain their existing visibility behavior - User visibility preferences (`show`/`hide`) still take precedence Fixes #6798
yindo added the pull-request label 2026-02-16 18:17:16 -05:00
yindo closed this issue 2026-02-16 18:17:16 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#12363
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?