every time before brainstorm asking to confirm, claude code will popup a cmd window #293

New issue

Closed

opened 2026-01-19 01:20:45 +00:00 by liugangnhm · 2 comments

liugangnhm commented

2026-01-19 01:20:45 +00:00

(Migrated from github.com)

Describe the bug

every time before brainstorm asking to confirm, claude code will popup this window

To Reproduce
Steps to reproduce the behavior:

use brainstorm command

Expected behavior
A clear and concise description of what you expected to happen.

Logs
If applicable, add logs to help explain your problem.

Additional context
Add any other context about the problem here.

**Describe the bug** every time before brainstorm asking to confirm, claude code will popup this window <img width="1223" height="639" alt="Image" src="https://github.com/user-attachments/assets/eb915f64-7a61-4adf-b5f5-d29d97d5cbd1" /> **To Reproduce** Steps to reproduce the behavior: 1. use brainstorm command **Expected behavior** A clear and concise description of what you expected to happen. **Logs** If applicable, add logs to help explain your problem. **Additional context** Add any other context about the problem here.

obra commented

2026-01-22 20:59:50 +00:00

(Migrated from github.com)

This issue may be partially related to the Windows hook execution changes, but it appears to be a different symptom.

What PR #331 fixes:

SessionStart hook failures on Windows
Blank terminal windows caused by the -l flag in the deprecated run-hook.cmd

This issue may be different:
If the cmd window appears specifically during brainstorming (not at session start), it could be related to:

The visual companion feature which opens a browser/terminal window
Skill execution triggering some Windows process

To help diagnose:

Does this cmd window appear at Claude Code startup, or only when running /superpowers:brainstorm?
Does the window have any content or title?
Are you using the visual companion feature?

If the window appears only during brainstorming and not at startup, this is likely a separate issue from what PR #331 addresses.

Could you please test with the fix from PR #331 (once merged) and report back if the issue persists?

This issue may be **partially related** to the Windows hook execution changes, but it appears to be a different symptom. **What PR #331 fixes:** - SessionStart hook failures on Windows - Blank terminal windows caused by the `-l` flag in the deprecated `run-hook.cmd` **This issue may be different:** If the cmd window appears specifically during brainstorming (not at session start), it could be related to: 1. The visual companion feature which opens a browser/terminal window 2. Skill execution triggering some Windows process **To help diagnose:** - Does this cmd window appear at Claude Code startup, or only when running `/superpowers:brainstorm`? - Does the window have any content or title? - Are you using the visual companion feature? If the window appears only during brainstorming and not at startup, this is likely a separate issue from what PR #331 addresses. Could you please test with the fix from PR #331 (once merged) and report back if the issue persists?

obra commented

2026-01-22 20:59:50 +00:00

(Migrated from github.com)

This issue may be partially related to the Windows hook execution changes, but it appears to be a different symptom.

What PR #331 fixes:

SessionStart hook failures on Windows
Blank terminal windows caused by the -l flag in the deprecated run-hook.cmd

This issue may be different:
If the cmd window appears specifically during brainstorming (not at session start), it could be related to:

The visual companion feature which opens a browser/terminal window
Skill execution triggering some Windows process

To help diagnose:

Does this cmd window appear at Claude Code startup, or only when running /superpowers:brainstorm?
Does the window have any content or title?
Are you using the visual companion feature?

If the window appears only during brainstorming and not at startup, this is likely a separate issue from what PR #331 addresses.

Could you please test with the fix from PR #331 (once merged) and report back if the issue persists?