You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
auth login <url> should confirm before running auth.command #22191
Same as #10939, but a bot asked us to submit this again
opencode auth login <url> fetches <url>/.well-known/opencode and runs the returned auth.command immediately.
Opencode should ask before running a remotely provided command or before using the remotely provided config at all (I suppose similar issue exists i.e. with configured MCPs)
The well-known config config block does get merged into user config which can contain other fields, need to see about that but would be unrelated to this issue, for this issue that is the fix
Looking at the options, I don't think it's realistic to identify all dangerous ones and keep the list up-to-date. I'd much prefer to approve the entire remote config before it is applied in any way.
Should it show the full received config and prompt for approval?
That currently seems like the best option to me. Should be reasonably simple to implement, and I'd say I'd like to know about some config being applied even to non-security related options.
Sorry for being a bit snarky previously, I understand that OpenCode security model basically trusts the provider (although I'm really not a fan of that)
Activity
ygxio commentedon Apr 15, 2026
have raised a PR for this @rekram1-node would you mind giving a review
exyi commentedon Apr 15, 2026
Are we sure no other part of the remote config is equivalent to unapproved code execution?
ygxio commentedon Apr 15, 2026
The well-known config config block does get merged into user config which can contain other fields, need to see about that but would be unrelated to this issue, for this issue that is the fix
exyi commentedon Apr 15, 2026
Looking at the options, I don't think it's realistic to identify all dangerous ones and keep the list up-to-date. I'd much prefer to approve the entire remote config before it is applied in any way.
ygxio commentedon Apr 15, 2026
@exyi what would be your recommendation?
Should it show the full received config and prompt for approval?
Right now it shows only the auth.command
And asks for approval
exyi commentedon Apr 15, 2026
That currently seems like the best option to me. Should be reasonably simple to implement, and I'd say I'd like to know about some config being applied even to non-security related options.
Sorry for being a bit snarky previously, I understand that OpenCode security model basically trusts the provider (although I'm really not a fan of that)
ygxio commentedon Apr 16, 2026
Can show the full config for approval
But configs can be large right
Might not want to fill my terminal up with a large config
github-actions commentedon Jul 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.