Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Console windows (conhost.exe) spam on Windows when Desktop app spawns child processes

Closed
#126 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
electron, powershell

Research direction

Start at the Electron child_process.spawn entry points that launch cmd.exe, powershell.exe, or rtk.exe, then reproduce the process chain on Windows 10/11. Verify that command execution no longer creates visible conhost.exe windows while the child processes still run, using Task Manager or the WMI event listener described in the report.

Written by the indexing model from the issue text.

Description

bug
GUI version

v0.1.43

Operating system

Windows

Reproduction steps
  1. Install and launch Command Code Desktop (version 0.1.43) on Windows 10/11.
  2. Leave the application running in the background (or even close it, if residual processes remain).
  3. Watch Task Manager or the screen: conhost.exe windows appear and disappear constantly.
  4. To confirm the origin, a WMI event listener (e.g. Register-WmiEvent in PowerShell) can be used to capture the process chain.
Expected behavior

Command Code Desktop should spawn child processes (such as cmd.exe, powershell.exe, rtk.exe) without displaying a console window. This is achievable by passing the CREATE_NO_WINDOW flag (0x08000000) to CreateProcess, or the equivalent windowsHide: true in Electron's child_process.spawn.

Actual behavior

Every time the application (or a residual process) executes a command, a new console window is allocated and displayed. The captured process chain is:

Command Code.exe (GUI, no console) → cmd.exe /d /s /c "powershell.exe -EncodedCommand ..." → conhost.exe (window)

This repeats dozens of times per minute.

Screenshots, recordings, or sanitized logs

commandcode-wmi-2026-09-29.log

Related: the same class of bug has been reported for Claude Code (#70200,
#64163, #35797), Codex (#48876), and Cursor. It's a known Windows-wide
pattern in GUI-hosted CLI agents.

Safety check
  • I removed credentials and private project information from this report.
Dominant language
Shell
Stars
85
Forks
5
Avg merge
2h 46m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CommandCodeAI/desktop

All issues in CommandCodeAI/desktop

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.