Steps to Reproduce:
Launch vscode from git bash.
$ code .
Open the terminal run some commands to fill the windows.
Then try to clear the windows. CTRL + L or clear.
ps: If I launch vscode from the system everything works fine.
I have git bash in the terminal window inside vscode
Reproduces without extensions: No
Can you provide a screenshot of what happens after you run clear?
@Tyriar There you go.

Hello, any updates on this? I have the same problem.
@rprichard any idea why clear would not be clearing the terminal?
This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.
Same issue. Only launch vscode via code <some-folder> in git bash will trigger this bug. same command in cmd works fine.
same exact issue here 馃槱 if i launch vscode from git-bash it won't clear the terminal 馃槶馃槶
would love to stay inside vscode integrated terminal for work but not having clear is really annoying... is this slated to get worked?
@nateous try ctrl/cmd+k (windows/mac) or trigger the "Terminal: Clear" command through the command palette (F1).
@Tyriar thanks, ctrl+k works.
Tracking this in https://github.com/Microsoft/vscode/issues/45693
In the meantime ctrl+k (WIndows), cmd+k (macOS) will still clear the terminal properly, you can also run the command through the command palette. If the keybinding is not working for you see the FAQ on https://code.visualstudio.com/docs/editor/integrated-terminal#_common-questions about fixing the issue.
I have this issue everyday... it's actually the one and only issue i have with vscode.
When i first open a folder with vscode, the git bash terminal does not clear itself when i use the "clear" command. Using ctrl+k (i'm using windows 10) does not fix the issue since it clears the terminal but once i start typing, the previous state of the terminal overlaps whatever i was trying to type.
I'm facing the same bug which @PauloGasparSv told
Most helpful comment
Same issue. Only launch vscode via
code <some-folder>in git bash will trigger this bug. same command in cmd works fine.