Skip to content

Terminal cursor is sometimes positioned near the beginning of the prompt instead of at the end #324914

Open

Description

@Mario-Cop
  • Steps to Reproduce:
  1. Open VS Code.
  2. Open a new integrated terminal.
  3. Observe the cursor position.
  • Expected Result:
    The cursor should be positioned at the end of the prompt, after the current working directory, ready for input.

  • Actual Result:
    Occasionally, the cursor is positioned near the beginning of the prompt instead of at the end. Any text that is typed is inserted at that incorrect cursor position, causing the command to appear in the wrong place within the prompt.

  • Attached:
    Screen recording demonstrating the issue.
    My settings.json file.

  • VS Code Version:
    Version: 1.127.0 (user setup)
    Commit: 4fe60c8
    Date: 2026-06-30T10:52:33+02:00
    Electron: 42.2.0
    ElectronBuildId: 14159160
    Chromium: 148.0.7778.97
    Node.js: 24.15.0
    V8: 14.8.178.14-electron.0
    OS: Windows_NT x64 10.0.26100

  • VS Code Extensions:
    angular.ng-template@22.0.1
    anthropic.claude-code@2.1.204
    bradlc.vscode-tailwindcss@0.14.29
    codezombiech.gitignore@0.10.0
    dbaeumer.vscode-eslint@3.0.24
    esbenp.prettier-vscode@12.4.0
    johnpapa.angular2@18.0.2
    ms-vscode.vscode-speech@0.16.0

  • OS Version:
    Windows 11 Pro 24H2 Version 10.0.26100.7171

Activity

  1. Mario-Cop commented on Jul 8, 2026

    @Mario-Cop
    Author

    Heads up:
    A comment was posted immediately after I opened this issue, offering a ZIP file (terminal_fix.zip) as a fix. This appears suspicious, as it was posted so quickly that it may have been generated automatically in response to new issues.

    I recommend not downloading or running files from unsolicited comments.

    Please wait for guidance from the VS Code maintainers or trusted contributors instead.

  2. gjsjohnmurray commented on Jul 8, 2026

    @gjsjohnmurray
    Contributor

    Mario Čop (@Mario-Cop)

    Indeed, several very recent issues in this repo have received similarly structured replies from different but brand new GH accounts, each linking to an attachment claimed to fix the issue.

    The team seems to be aware of this incident and has been deleting the suspect comments from other issues.

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

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions