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
Missing md formating after upgrade to v1.0.x #3751
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.
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.
Reacted by somera, Doug Chasman, estenv and Antón Valladares
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.
Activity
github-actions commentedon Nov 2, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
Regboy744 commentedon Nov 2, 2025
same problem happening with me
kommander commentedon Nov 2, 2025
Can you open the console with alt+d and see if there are any TSWorker errors?
somera commentedon Nov 2, 2025
@kommander I don't see any errors (GitBash or PowerShell).
kommander commentedon Nov 2, 2025
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.
somera commentedon Nov 2, 2025
I see this
at the beginning.
somera commentedon Nov 2, 2025
Here is the log:
_console_1762105353194.log
kommander commentedon Nov 2, 2025
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.
somera commentedon Nov 6, 2025
@kommander any updates here?
thdxr commentedon Nov 6, 2025
we're fixing some general perf issues this week will be looking closer at windows next week
somera commentedon Nov 16, 2025
Any update here?
rekram1-node commentedon Nov 17, 2025
@somera yea we have a fix for this in dev shipping today
somera commentedon Nov 18, 2025
I updated to 1.0.72 and I see no changes in git bash and PowerShell
somera commentedon Nov 18, 2025
And when I exit opencode (in git bash) I see strange output:
rekram1-node commentedon Nov 18, 2025
For whatever reason it worked pre build but not post will fix
somera commentedon Nov 18, 2025
@rekram1-node any idea why I see this in git bash after ending opencode? And I don't see this in v0.15.31.
rekram1-node commentedon Nov 19, 2025
im not entirely sure the root cause but the escape ansi codes are leaking through
somera commentedon Nov 19, 2025
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):
(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 mode35– button / event code (which mouse button, which modifiers, etc.)74– X position (column number) of the mouse18– Y position (row number) of the mouseM– mouse button pressed / moved (mwould mean “released”)These sequences appear when some program has enabled xterm mouse tracking (for example
vim,tmux,lesswith 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.somera commentedon Nov 30, 2025
When can we expect a solution?
rekram1-node commentedon Nov 30, 2025
ill look into it im hoping its a trivial bug
rekram1-node commentedon Dec 4, 2025
Should be fixed on 1.0.130
somera commentedon Dec 4, 2025
@rekram1-node formating works now.
But there is the problem, when I
/exitopencode in the git bash on windows I see this (as I wrote above, this are a mouse events)This was not in
v0.15.x. I need to close and open my git bash.rekram1-node commentedon Dec 4, 2025
Yeah we will fix that too
somera commentedon Dec 4, 2025
Do you need a new issue for this?
rekram1-node commentedon Dec 4, 2025
I think there is one already let me see
rekram1-node commentedon Dec 4, 2025
maybe not