Read Shell errors

[thawkins]

Describe the bug

When using copilot-cli I see a lot of errors like this

Read shell output
Invalid session ID: 72222222-2222-2222-2222-222222222222. Please supply a valid session ID to read output from.

Affected version

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

Additional context

No response

[williammartin]

Please provide the version.

[thawkins]

10 mins ago in 0.0.369

✓ Grep "device_console"
└ 9 files found

✗ Read shell output
Invalid session ID: 0. Please supply a valid session ID to read output from.

✓ Read crates/gcodekit5-ui/resources/markdown/machine_control.md
└ 39 lines read

[MRayermannMSFT]

For any folks who are seeing issues with the bash tool consistently not being able to run commands, please do the following:

1. Install latest Copilot, copilot update
2. Run copilot --log-interactive-shells
3. Do the a prompt like "run echo hello using your powershell tool", you can use a 0x model if wish to preserve your PRUs
4. Make sure model at least tries to echo hello, and confirm that it works/doesn't work
5. Regardless if it works or does not work, use /session
6. Open parent directory of the Session: file in your file browser/explorer
7. Look for a shell-logs/ folder
8. There should be a single file in it, open it, double check it for anything you don't want to share publicly
9. Drag and drop the file here if it looks good to share

Thanks!

[alavanta]

For any folks who are seeing issues with the bash tool consistently not being able to run commands, please do the following:

1. Install latest Copilot, copilot update
2. Run copilot --log-interactive-shells
3. Do the a prompt like "run echo hello using your powershell tool", you can use a 0x model if wish to preserve your PRUs
4. Make sure model at least tries to echo hello, and confirm that it works/doesn't work
5. Regardless if it works or does not work, use /session
6. Open parent directory of the Session: file in your file browser/explorer
7. Look for a shell-logs/ folder
8. There should be a single file in it, open it, double check it for anything you don't want to share publicly
9. Drag and drop the file here if it looks good to share

Thanks!

I followed the steps and attached the shell logs

Environment

• macOS
• Default shell: zsh
• Copilot CLI spawns bash --norc --noprofile
• Bash version: macOS default 3.2.57

Prompt used

echo hello using your zsh tool

What happened

The model tried to run echo hello, but the shell tool couldn't read the output and returned:

Invalid shell ID: 0. Please supply a valid shell ID to read output from.

It then retried and I saw the same error again with shell ID 1. After that, the output hello eventually appeared.

So the command seems to run, but the shell session becomes invalid while the tool is trying to read the output.

Looking at the shell logs

It looks like the command stream might be getting corrupted. For example I see echo showing up as:

e�ho BEGIN___COMMAND_OUTPUT_MARKER

Which bash interprets as:

eho

and that leads to:

bash: eho: command not found

After that the shell initialization times out and the process exits, which might explain why the tool reports no active shell sessions.

Shell logs

shell-0-1772808557282 copy.log