ShellFailed with exit code 1 when OpenCode tries to "ask" for permissions (Windows) #4880

Activity

1. JosXa

   added

   bugSomething isn't workingSomething isn't working

   on Nov 28, 2025
2. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Nov 28, 2025
3. github-actions commented on Nov 28, 2025

   

   github-actionsBot

   on Nov 28, 2025 – with GitHub Actions

   Contributor

   More actions

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

   • [Windows] interactive call breaking tui #3763: [Windows] interactive call breaking tui - describes Windows terminal issues with interactive bash calls that expect user input, similar to the permission asking flow

   Feel free to ignore if this doesn't address your specific case.
4. rekram1-node commented on Nov 28, 2025

   

   rekram1-node

   on Nov 28, 2025

   Contributor

   More actions

   Isn't this an OS level permission. Not an opencode bug? Seems like opencode the executable on your machine doesnt have permission to read that file at all.

   So you'd need to edit your actual settings at a lower level than opencode settings
5. rekram1-node

   removed

   bugSomething isn't workingSomething isn't working

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Nov 28, 2025
6. rekram1-node

   self-assigned this

   on Nov 28, 2025
7. JosXa commented on Nov 28, 2025

   

   JosXa

   on Nov 28, 2025

   Last edited by JosXa

   ContributorAuthor

   More actions

   This should prove it?

   

   https://opencode.ai/s/HklH4yiK
8. rekram1-node commented on Nov 28, 2025

   

   rekram1-node

   on Nov 28, 2025

   Contributor

   More actions

   But like I said, if you are getting errors when opencode tries to execute things or read files. Thats at your OS level, it doesnt really matter the permission in the config if your os is rejecting it right
9. rekram1-node commented on Nov 28, 2025

   

   rekram1-node

   on Nov 28, 2025

   Contributor

   More actions

   What do you see if you try to do:

   type "!" into prompt input box to go into shell mode

   then type "git status"

   Then hit enter
10. JosXa commented on Nov 28, 2025

    

    JosXa

    on Nov 28, 2025

    Last edited by JosXa

    ContributorAuthor

    More actions

    Oh, so you're saying the "ask" just runs some shell script to prompt for confirmation?
    Bear in mind that I have no idea what it's supposed to look like since it never worked.

    Neither has ! command, but that might indeed be on me:

     $ git status                                                                         ┃Microsoft Windows [Version 10.0.26220.7271]     
    ┃  (c) Microsoft Corporation. All rights           
    ┃  reserved.                                       
    ┃  Not enough memory resources are available       
    ┃  to process this command.                        
    ┃
    

    Getting this despite having set $SHELL to pwsh.exe, so no idea what's going on. Will try to debug. Obviously not getting this error anywhere else.
11. rekram1-node commented on Nov 28, 2025

    

    rekram1-node

    on Nov 28, 2025

    Contributor

    More actions

    Oh, so you're saying the "ask" just runs some shell script to prompt for confirmation?
    Bear in mind that I have no idea what it's supposed to look like since it never worked.

    No im saying that "ask" will force the user to approve things before they are ran. However the errors you are getting have nothing to do with opencode permissions and everything to do with your OS and your setup.

    I guess here the issue is you dont have enough RAM
12. JosXa commented on Nov 28, 2025

    

    JosXa

    on Nov 28, 2025

    ContributorAuthor

    More actions

    Heh yeah if only it was that easy, got a cool 40GB left over :(
13. JosXa commented on Nov 29, 2025

    

    JosXa

    on Nov 29, 2025

    ContributorAuthor

    More actions

    Interestingly, I'm hitting the exact same issue on a newly installed Linux machine now, where ! command works fine. I don't see how my config could possibly be causing this. Would it help if I gave some additional context from there?
14. rekram1-node commented on Nov 29, 2025

    

    rekram1-node

    on Nov 29, 2025

    Contributor

    More actions

    I mean probably? It doesn't seem like it has anything to do with your opencode config to me
15. thdxr

    closed this as completedon Mar 25, 2026