Skip to content

fix(v2): show default models with the current date - #2

Closed
jogesr wants to merge 1 commit into
Noser-Engineering:mainfrom
jogesr:feat/desktop-default-aliases
Closed

jogesr wants to merge 1 commit into
Noser-Engineering:mainfrom
jogesr:feat/desktop-default-aliases

Conversation

@jogesr

@jogesr jogesr commented Oct 14, 2026

Copy link
Copy Markdown
Member

Summary

Make coding, thinking and fast visible by default in OpenCode Desktop 2.0.29, and allow loading the plugin from its local repository directory.

The timestamp is a targeted visibility workaround, not the models’ actual release date. Explicit user visibility choices still take precedence.

Evidence

  • Before: Desktop hid all three aliases because released: 0 was interpreted as 1970. Local directory loading skipped the plugin because no root-level entrypoint existed.
    After: The running Desktop API reports the local plugin as active and all three aliases with current timestamps and separate families. Their visibility was confirmed manually in Desktop 2.0.29.
  • Regression tests failed before the fixes and passed afterward.
  • npm run check: typecheck, all 210 tests and build passed.
  • git diff --cached --check: passed.

Merge Danger

Door: two-way

No dependency changes or migrations. The visibility workaround can be reverted without changing stored user preferences.

Blast Radius: limited

Only the three exact aliases in the V2 adapter and local directory loading change. Other models, provider configuration and the V1 adapter remain unchanged.

@tobiasritscher

Copy link
Copy Markdown
Collaborator

Danke für die Analyse! Gelöst in 0.8.0 auf anderem Weg: Statt fest einprogrammierter Aliase mit Date.now() liest das Plugin jetzt model_info.released und model_info.family aus /v1/model/info. So steuert der Proxy-Admin in der LiteLLM-Config, welche Modelle Desktop 2 anzeigt. Neuron ist entsprechend konfiguriert.

Das lokale Laden über server.js ist ein separates Thema. Gerne als eigene PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants