Originally created by @erazortt on GitHub (Aug 16, 2025).
Check Existing Issues
I have searched the existing issues and discussions.
Problem Description
Even when BYPASS_MODEL_ACCESS_CONTROL=true the Task Model selection (both Local and External) expects explicitly setting the models Visibility to Public.
Desired Solution you'd like
The Task Model selection should allow any model without explicit setting when BYPASS_MODEL_ACCESS_CONTROL=true.
Alternatives Considered
No response
Additional Context
No response
Originally created by @erazortt on GitHub (Aug 16, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Even when BYPASS_MODEL_ACCESS_CONTROL=true the Task Model selection (both Local and External) expects explicitly setting the models Visibility to Public.
### Desired Solution you'd like
The Task Model selection should allow any model without explicit setting when BYPASS_MODEL_ACCESS_CONTROL=true.
### Alternatives Considered
_No response_
### Additional Context
_No response_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @erazortt on GitHub (Aug 16, 2025).
Check Existing Issues
Problem Description
Even when BYPASS_MODEL_ACCESS_CONTROL=true the Task Model selection (both Local and External) expects explicitly setting the models Visibility to Public.
Desired Solution you'd like
The Task Model selection should allow any model without explicit setting when BYPASS_MODEL_ACCESS_CONTROL=true.
Alternatives Considered
No response
Additional Context
No response
@tjbck commented on GitHub (Aug 16, 2025):
This is purely UI/UX, and it should work as intended.