Skip to content

“socket is not connected” on POST /session/{id}/message when project root contains .git; removing .git avoids the error (Windows 10, Bun 1.3.0, opencode 0.15.3) #3208

Closed

Description

@TangTangH

Any project with a .git folder returns “socket is not connected” on POST /session/{id}/message ; removing .git makes it succeed.

I have tried multiple attempts given in the issue dialogue, but have not been able to resolve it.

Logs with .git folder:
2025-10-16T093229.log

Logs without .git folder:
2025-10-16T093329.log

Activity

  1. github-actions commented on Oct 16, 2025

    @github-actions
    Contributor

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

    Feel free to ignore if none of these address your specific case.

  2. tmaarcxs commented on Oct 16, 2025

    @tmaarcxs

    same for me

    Edit: downgrading to 0.14.7 solves the issue temporally

  3. rekram1-node commented on Oct 16, 2025

    @rekram1-node
    Collaborator

    Ill look into that

  4. self-assigned this
    on Oct 16, 2025
  5. rekram1-node commented on Oct 17, 2025

    @rekram1-node
    Collaborator

    Seems to be due to bun 1.3, both of you are on windows right

  6. tmaarcxs commented on Oct 17, 2025

    @tmaarcxs

    Seems to be due to bun 1.3, both of you are on windows right

    Yes, I'm on windows also

  7. sollie commented on Oct 18, 2025

    @sollie

    I am also seeing this on macOS 15.7.1

  8. rekram1-node commented on Oct 18, 2025

    @rekram1-node
    Collaborator

    hm good to know...

    @sollie is it without fail always happening? Is the git project really big or something?

  9. sollie commented on Oct 18, 2025

    @sollie

    hm good to know...

    @sollie is it without fail always happening? Is the git project really big or something?

    The first repo I had it happen to had less than 10 commits across 5-10 files total in the repo.

  10. rekram1-node commented on Oct 18, 2025

    @rekram1-node
    Collaborator

    weird hm okay thanks

  11. TangTangH commented on Oct 26, 2025

    @TangTangH
    Author
    Image

    After upgrading to version 0.15.18, I got a more precise error message, which points to this location: src/file/ripgrep.ts:217:27

  12. rekram1-node commented on Oct 26, 2025

    @rekram1-node
    Collaborator

    Ahh okay that's helpful

  13. freddiehaddad commented on Oct 27, 2025

    @freddiehaddad

    Can confirm the same as the other folks. Downgrading works as a temporary solution.

  14. TangTangH commented on Nov 4, 2025

    @TangTangH
    Author

    The issue was still present in version v1.0.15, but it has been resolved after updating to v1.0.18.

  15. rekram1-node commented on Nov 4, 2025

    @rekram1-node
    Collaborator

    amazing, going to close and if anyone else has this issue on v1 lmk and we will reopen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions