Skip to content

fix(tui): rename OpenAI-Compatible provider to "llama.cpp / vLLM" - #383

Merged
Aaronontheweb merged 1 commit into
devfrom
claude-wt-openai-compat
Mar 22, 2026
Merged

fix(tui): rename OpenAI-Compatible provider to "llama.cpp / vLLM"#383
Aaronontheweb merged 1 commit into
devfrom
claude-wt-openai-compat

Conversation

@Aaronontheweb

Copy link
Copy Markdown
Collaborator

Summary

  • Renames the openai-compatible provider's DisplayName from "OpenAI-Compatible" to "llama.cpp / vLLM" to better describe the actual servers it supports (llama.cpp, llama-server, vLLM, Lemonade)
  • Wires DisplayName through ProviderDisplayItem so all TUI views (provider manager, init wizard, OAuth flows) show the friendly name instead of the raw type key
  • Column header changed from "Type" to "Provider" in the provider list view

No changes to config format, CLI commands, or internal TypeKey — this is purely a display rename.

Test plan

  • All 24 ProviderManager TUI tests pass
  • All 47 InitWizard TUI tests pass
  • Visual check: netclaw provider list shows "llama.cpp / vLLM" instead of "openai-compatible"
  • Visual check: netclaw init provider selection shows display names

…LLM"

The openai-compatible provider type covers llama.cpp, llama-server, vLLM,
and Lemonade — not to be confused with the separate Ollama provider. Update
the DisplayName and wire it through to all user-facing TUI labels in the
provider manager, init wizard, and OAuth flows. The TypeKey remains
"openai-compatible" for config and CLI compatibility.
@Aaronontheweb
Aaronontheweb merged commit fc04a64 into dev Mar 22, 2026
3 checks passed
@Aaronontheweb
Aaronontheweb deleted the claude-wt-openai-compat branch March 22, 2026 21:20
@Aaronontheweb Aaronontheweb mentioned this pull request Mar 25, 2026
4 tasks
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.

1 participant