Skip to content

Run in terminal request stuck due to bad quoting stuck in line continuation #254426

Description

@PulseHabour

Does this issue occur when all extensions are disabled?: N/A

  • VS Code Version: 1.102.0-insider (Universal)
  • OS Version: Darwin arm64 24.5.0
  • GHCP Chat: 0.29.2025070403 - Agent - Claude Sonnet 4

Steps to Reproduce:

  1. GHCP Chat runs a multi-line command in the terminal
  2. Terminal is still waiting for command to be entered, stuck on dqoute>
  3. GHCP Chat eternally waits as still waiting for a response from the command, throbber is still there

Example command:

user@mac ./ % BASE_MESSAGE="🚀 VS Code extension updated"
dquote> FULL_MESSAGE="$BASE_MESSAGE\n\n**Changes since last version:**\n$COMMIT_LIST"
dquote> echo "Message length: ${#FULL_MESSAGE}"
dquote> echo "Message:"
dquote> echo "$FULL_MESSAGE"
dquote> 

Slight workaround:
Send a message of dqoute>, GHCP Chat will recognise the terminal is hanging, and will continue.
Or attempt to manually EOL the terminal to enter command.

Unsure if this is the model itself, or GHCP Chat, as it can adapt if aware.

Activity

  1. added
    bugIssue identified by VS Code Team member as probable bug
    chat-terminalThe run in terminal tool in chat
    on Jul 23, 2025
  2. changed the title [-]Github Copilot Chat stuck in terminal[/-] [+]Run in terminal request stuck due to bad quoting stuck in line continuation[/+] on Jul 23, 2025
  3. cdeil commented on Sep 4, 2025

    @cdeil

    Daniel Imms (@Tyriar) - for me getting stuck on dquote is the most common case for GHCA to get stuck in the past months.

    Any chance to get that fixed?


    Here's the latest case where it happened today.

    Hope it helps to pinpoint the issue.

    cdeil@Mac android % patrol test && echo "Tests passed!" || if [[ -f "build/app/reports/androidTests/connected/index.html" ]]; then echo "Tests executed, check results"; else echo "Test execution failed
    "; fi
    cmdand dquote> 
    
    ### Solution 3: Check Test Results Programmatically
    You can parse the test results file to determine the actual test status: 
    🛠️ run_in_terminal (toolu_vrtx_015ATa2LD2wh3aPX7vAXgZAL) {
      "command": "patrol test && echo \"Tests passed!\" || if [[ -f \"build/app/reports/androidTests/connected/index.html\" ]]; then echo \"Tests executed, check results\"; else echo \"Test execution failed\"; fi",
      "explanation": "Testing a command to distinguish between test failures and execution failures",
      "isBackground": false
    }
    
    Image
  4. ghirardinicola commented on Jan 15, 2026

    @ghirardinicola

    Same for me. Using long parms Is impossible. Did not found a workaround year

    Daniel Imms (@Tyriar) - for me getting stuck on dquote is the most common case for GHCA to get stuck in the past months.

    Any chance to get that fixed?


    Here's the latest case where it happened today.

    Hope it helps to pinpoint the issue.

    cdeil@Mac android % patrol test && echo "Tests passed!" || if [[ -f "build/app/reports/androidTests/connected/index.html" ]]; then echo "Tests executed, check results"; else echo "Test execution failed
    "; fi
    cmdand dquote> 
    
    ### Solution 3: Check Test Results Programmatically
    You can parse the test results file to determine the actual test status: 
    🛠️ run_in_terminal (toolu_vrtx_015ATa2LD2wh3aPX7vAXgZAL) {
      "command": "patrol test && echo \"Tests passed!\" || if [[ -f \"build/app/reports/androidTests/connected/index.html\" ]]; then echo \"Tests executed, check results\"; else echo \"Test execution failed\"; fi",
      "explanation": "Testing a command to distinguish between test failures and execution failures",
      "isBackground": false
    }
    
    Image
  5. meganrogge commented on Mar 25, 2026

    @meganrogge
    Collaborator

    I believe this is already fixed, can you see if you can reproduce in the Insiders build?

  6. locked and limited conversation to collaborators on May 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugIssue identified by VS Code Team member as probable bugchat-terminalThe run in terminal tool in chat

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions