Skip to content

docs: note that config-disabled models can still be alias targets #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vmvarela merged 1 commit into from
Oct 7, 2026
Merged

docs: note that config-disabled models can still be alias targets #43

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,6 +191,9 @@ was detected. Changing an alias's match or filter rules resets its baseline.
- Only the `latest` strategy exists. The plugin can't rank by price or quality.
- Aliases are provider-isolated and never chain.
- The plugin only reads OpenCode's catalog; it never fetches external model lists.
- Models hidden with `disabled: true` in your OpenCode provider config can still be selected
by an alias ([#42](https://github.com/vmvarela/opencode-model-aliases/issues/42)). Use
`exclude` to keep a model out of an alias.

## Development

Expand Down
Loading