CommandCodeAI / CommandCodeAI/desktop

[Bug]: Installer shows some unexpected logging after already finishing

Open
#1 1 comment 0 reactions 1 assignee View on GitHub

@aliarain is already working on this.

Since Sep 7, 2026.

bug
Dominant language
Shell
Stars
80
Forks
2
PR merge metrics
No merged PRs in 30d

Description

GUI version

0.1.1

Operating system

macOS (Apple silicon)

Reproduction steps

I am on Windows, but can't select that OS in the issue template dropdown....

When installing with the script and directly launching the application from the installer, I get some weird output.

Expected behavior

No output afterwards.

Actual behavior
PS C:\Users\username\Desktop> irm https://raw.githubusercontent.com/CommandCodeAI/gui/main/install.ps1 | iex
Downloading Command Code 0.1.1 for Windows...
Verified SHA-256: 7fc7869da3e27d830c863dd62fdecda2dccaa27f44fc1a06aab7915f8a7e4dbf
WARNUNG: This preview is not yet Authenticode signed.
Continue with the official verified installer? [y/N]: y
Command Code 0.1.1 installed successfully.

PS C:\Users\username\Desktop> Checking for update
Generated new staging user ID: <redacted_id>
Error: Error: net::ERR_NAME_NOT_RESOLVED
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:123516)
    at SimpleURLLoaderWrapper.emit (node:events:518:28)
11:56:57.668 > [updater] error: Error: net::ERR_NAME_NOT_RESOLVED
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:123516)
    at SimpleURLLoaderWrapper.emit (node:events:518:28)
11:56:57.669 > [updater] check failed: Error: net::ERR_NAME_NOT_RESOLVED
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js^C/browser_init:2:123516)

What is weird is that this output happens after (!) the install command seems to have finished.

I ran under Windows 11 with the Terminal app.

Screenshots, recordings, or sanitized logs

No response

Safety check
  • I removed credentials and private project information from this report.

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.