Internal issue with insertion point

[Wiggleslost]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Copilot in GitHub

Body

I am having issues with Penguin where the cursor that appears like the cursor in Copilot that is in the before writing a text letter is showing up at the end of the text in Penguin after typing normal commands for the program in SteamCMD

I have had to update Microsoft Windows multiple times with the most recent update causing the update to restart the computer about 3 times until the screen came back to appearing normal

I have not ran Copilot earlier today, was difficult finding the discussion board for Copilot as the account in here was only showing discussions that I have previously made, hope remote will help separate the main public from the coding public that remote will help the main public whereas CLI will help the coding public, a closer step for the main public one day having a word to turn to like remote, makes them feel in control

I wanted to write this as I am getting further into depths of coding that I am doing more than I have knowledge of accomplishing, some of the coding principles scare me because I have no real knowledge of the inside of a board except past experience that is making me learn how to code, while growing up, I always watching others press the coding buttons while I am now pressing the buttons more and more everyday

I have to press the letter "q" now in order for the server to go back to being able to write a letter in penguin, the new information is foreign to me as I have never seen SteamCMD appear like the blocky insertion point of what is called the cursor at the end of completed command that usually reverts back to my username with the server name NGS

[ChHussain]

It sounds like what you’re experiencing is a terminal behavior issue rather than anything related to Copilot.

The key detail is that you need to press q before you can type again. That typically means your terminal has entered a pager mode (most commonly less). In this mode, the output of a command is being displayed in a scrollable view, and normal input is paused until you exit. Pressing q exits that view and returns you to the shell prompt.

The “block-style cursor” you’re seeing is also normal in this context—it’s just a different cursor style used by the terminal or pager, not related to Copilot.

This can sometimes start happening after updates (Windows or WSL/Penguin) because of changes to environment settings or how output is handled.

A few things you can try:

• After running your command, press q to confirm it exits back to normal prompt (this verifies it’s a pager).
• Run export PAGER=cat in your terminal to disable paging behavior.
• If the terminal feels stuck or glitchy, run reset to restore it.

Based on your description, nothing sounds broken—just a different mode being triggered during command output.

If you can share the exact SteamCMD command you’re running, it would help pinpoint exactly what’s invoking the pager.

[Gecko51]

Echoing what ChHussain said, this isn't a Copilot issue, it's a terminal behavior thing. The block cursor showing up at the end of your command output and requiring "q" to get back to a prompt is the signature of a pager (less or more) taking over the terminal. Pressing q exits the pager and drops you back at the shell.

A couple of SteamCMD-specific angles that might help pin it down:

SteamCMD itself doesn't usually invoke a pager, but if you're running it through a wrapper script, a shell alias, or in Git Bash / MSYS2 / WSL on Windows, the wrapper can pipe output through less by default. Run which steamcmd (on Linux/WSL) or type steamcmd (on Windows) and see if it's a plain binary or a script.

If you're actually inside SteamCMD's interactive shell (the prompt that starts with Steam>), the block cursor is normal there. That's SteamCMD's own prompt. Typing quit exits it and you're back in your OS shell.

If you're on Windows and the whole thing broke after those Windows updates, it might be the terminal emulator itself glitching, not SteamCMD. Try opening Windows Terminal fresh, or fall back to plain cmd.exe, and run steamcmd from there. Sometimes a Windows update resets terminal defaults and the host terminal starts interpreting control sequences differently.

If you can share the exact command you run right before the block cursor appears, and whether you're on Windows cmd, PowerShell, Windows Terminal, WSL, or Git Bash, it narrows this down fast.