Opencode will not launch if you set Agent permissions as True/False instead of Allow/Deny #7810

Activity

1. ManningWorks

   added

   bugSomething isn't workingSomething isn't working

   on Jan 11, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 11, 2026
3. github-actions

   added

   windows

   on Jan 11, 2026
4. github-actions commented on Jan 11, 2026

   

   github-actionsBot

   on Jan 11, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • ConfigInvalidError on Windows due to unrecognized keys in opencode.json #7483: ConfigInvalidError on Windows due to unrecognized keys - Similar config validation error preventing launch
   • [BUG] Schema.ref 'QuestionInfo' was set alongside unsupported fields in v1.1.x #7791: Schema.ref 'QuestionInfo' validation error in v1.1.x - Related schema validation issue causing startup failures

   Both issues describe ConfigInvalidError exceptions that prevent OpenCode from launching due to invalid configuration. Your issue involves invalid permission format (true/false instead of allow/deny), which appears to be a schema validation problem similar to these reported cases.

   Feel free to ignore if your issue involves a distinctly different aspect or if these don't match your specific error.
5. itstrivial commented on Jan 11, 2026

   

   itstrivial

   on Jan 11, 2026

   Last edited by itstrivial

   More actions

   My PR fixes the crash for true/false, but error messages for other invalid config values still don't display clearly.

   One potential solution would be to enhance the worker thread error handlers in packages/opencode/src/cli/cmd/tui/worker.ts to format errors using FormatError() and display them via console.error():

   process.on("unhandledRejection", (e) => {
     const formatted = FormatError(e)
     Log.Default.error("rejection", {
       e: e instanceof Error ? e.name : e,
       formatted,
     })
     if (formatted) console.error(formatted)
   })
   
   process.on("uncaughtException", (e) => {
     const formatted = FormatError(e)
     Log.Default.error("exception", {
       e: e instanceof Error ? e.name : e,
       formatted,
     })
     if (formatted) console.error(formatted)
   })
   

   However, I'm not sure if maintainers would prefer this approach, so I did not implement it.

   👍React with 👍1Reacted by Luke Manning
6. ManningWorks commented on Jan 11, 2026

   

   ManningWorks

   on Jan 11, 2026

   Author

   More actions

   I am personally fine with either:

   1. Your Fix
   2. Better outputs to help diagnosis

   If we can get both, great. If we can get your PR fix, great.

   👍React with 👍1Reacted by Harald
7. thdxr commented on Mar 25, 2026

   

   thdxr

   on Mar 25, 2026

   Member

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
8. thdxr

   removed

   bugSomething isn't workingSomething isn't working

   windows

   on May 3, 2026
9. rekram1-node

   closed this as not plannedon May 22, 2026