Skip to content

Missing md formating after upgrade to v1.0.x #3751

Closed

Description

@somera

Description

Since upgrade to 1.0.x the output is not readable.

in 0.15.x

Image

in 1.0.x

Image

OpenCode version

1.0.11

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

GitBash

Activity

  1. added
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Nov 2, 2025
  2. github-actions commented on Nov 2, 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.

  3. Regboy744 commented on Nov 2, 2025

    @Regboy744

    same problem happening with me

  4. kommander commented on Nov 2, 2025

    @kommander
    Contributor

    Can you open the console with alt+d and see if there are any TSWorker errors?

  5. somera commented on Nov 2, 2025

    @somera
    Author

    @kommander I don't see any errors (GitBash or PowerShell).

    Image
  6. kommander commented on Nov 2, 2025

    @kommander
    Contributor

    When you press alt+d to open the console and then directly press ctrl+s, it should store the logs to a file in the cwd. Can you share that? There should be something about TSWorker loading parsers and queries.

  7. somera commented on Nov 2, 2025

    @somera
    Author

    I see this

    Image

    at the beginning.

  8. somera commented on Nov 2, 2025

    @somera
    Author
  9. kommander commented on Nov 2, 2025

    @kommander
    Contributor

    Cool, I see the issue. Need to figure out how to solve it and why it doesn't work on windows. Probably because of the hardcore path with slashes. Will be fixed.

  10. somera commented on Nov 6, 2025

    @somera
    Author

    @kommander any updates here?

  11. thdxr commented on Nov 6, 2025

    @thdxr
    Member

    we're fixing some general perf issues this week will be looking closer at windows next week

  12. somera commented on Nov 16, 2025

    @somera
    Author

    Any update here?

  13. rekram1-node commented on Nov 17, 2025

    @rekram1-node
    Collaborator

    @somera yea we have a fix for this in dev shipping today

  14. somera commented on Nov 18, 2025

    @somera
    Author

    I updated to 1.0.72 and I see no changes in git bash and PowerShell

    Image
  15. somera commented on Nov 18, 2025

    @somera
    Author

    And when I exit opencode (in git bash) I see strange output:

    Image
  16. rekram1-node commented on Nov 18, 2025

    @rekram1-node
    Collaborator

    For whatever reason it worked pre build but not post will fix

  17. somera commented on Nov 18, 2025

    @somera
    Author

    And when I exit opencode (in git bash) I see strange output:

    Image

    @rekram1-node any idea why I see this in git bash after ending opencode? And I don't see this in v0.15.31.

  18. rekram1-node commented on Nov 19, 2025

    @rekram1-node
    Collaborator

    im not entirely sure the root cause but the escape ansi codes are leaking through

  19. somera commented on Nov 19, 2025

    @somera
    Author

    im not entirely sure the root cause but the escape ansi codes are leaking through

    ChatGPT say this ...

    What you see in the screenshot is not some secret code from your script, but the raw mouse event data from your terminal.

    Those chunks actually look like this (the beginning is just hidden / not printed nicely):

    ESC [ < 35 ; 74 ; 18 M
    ESC [ < 35 ; 75 ; 17 M
    ESC [ < 17 ; 35 ; 76 M
    ...
    

    (You usually don’t see the ESC[<, but it’s there.)

    Meaning of the parts:

    • ESC[< – “start of a mouse event” in xterm / SGR mouse mode
    • 35 – button / event code (which mouse button, which modifiers, etc.)
    • 74 – X position (column number) of the mouse
    • 18 – Y position (row number) of the mouse
    • M – mouse button pressed / moved (m would mean “released”)

    These sequences appear when some program has enabled xterm mouse tracking (for example vim, tmux, less with mouse support, etc.) and, instead of handling them internally, the raw bytes end up printed into the terminal or captured by your script.

    So in short:
    👉 It’s just the terminal reporting mouse clicks/movements as text codes. It’s not an error in itself, just noisy output. If it bothers you, stop the program (Ctrl+C) or start a fresh terminal.

  20. somera commented on Nov 30, 2025

    @somera
    Author

    For whatever reason it worked pre build but not post will fix

    When can we expect a solution?

  21. rekram1-node commented on Nov 30, 2025

    @rekram1-node
    Collaborator

    ill look into it im hoping its a trivial bug

  22. rekram1-node commented on Dec 4, 2025

    @rekram1-node
    Collaborator

    Should be fixed on 1.0.130

  23. somera commented on Dec 4, 2025

    @somera
    Author

    @rekram1-node formating works now.

    But there is the problem, when I /exit opencode in the git bash on windows I see this (as I wrote above, this are a mouse events)

    Image

    This was not in v0.15.x. I need to close and open my git bash.

  24. rekram1-node commented on Dec 4, 2025

    @rekram1-node
    Collaborator

    Yeah we will fix that too

  25. somera commented on Dec 4, 2025

    @somera
    Author

    Do you need a new issue for this?

  26. rekram1-node commented on Dec 4, 2025

    @rekram1-node
    Collaborator

    I think there is one already let me see

  27. rekram1-node commented on Dec 4, 2025

    @rekram1-node
    Collaborator

    maybe not

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 workingopentuiThis relates to changes in v1.0, now that opencode uses opentui

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions