Repository navigation
[Bug]: Muse Ember 1.0 doesn't work even though it works using standard terminal while having Muse Code sub #34409
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
Not sure
Steps to reproduce
- Choose "Ember 1.0" model while having active Muse Code sub
- Send prompt
- Get error "model
muse-ember-1.0does not exist or you lack access [request_id=f1ac6410-69f9-470a-8e86-e7a9e7491851]" - Other Muse models work fine. Ember model works normally when used via terminal of course
Expected behavior
Response from model
Actual behavior
Error "Provider error model muse-ember-1.0 does not exist or you lack access [request_id=f1ac6410-69f9-470a-8e86-e7a9e7491851]"
Impact
Blocks work completely
Version or commit
0.1.10-nightly.20261111.4529
Environment
Windows
Logs or stack traces
Screenshots, recordings, or supporting files
Workaround
No response
Reacted by Frederik Madsen
Activity
Exotic209093 commentedon Nov 12, 2026
The same error on
muse-ember-1.0was traced in #33561 (now discussion #33562). With Muse Code's contributor mode on (contributor_mode_enabled: truein Muse'ssettings.json), themuse servehost that T3 Code starts requestsmuse-ember-1.0-contributor, a deployment that doesn't exist, and the 404 comes back as "does not exist or you lack access" naming the base model.muse execand the TUI use the base deployment, which is why Ember works in your terminal.@DeveloperCasper: do you have contributor mode on? If so, turning it off should make Ember work in T3 Code, and this is the same issue as #33562.
DeveloperCasper commentedon Nov 12, 2026
@Exotic209093 yeah I had contributor mode on, I switched it off and Ember worked in T3 Code, thank you for the help ❤️