gemini-cli-extensions / gemini-cli-extensions/conductor
Always asks an empty questions, followed by "User submitted without answering questions"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
After running setup, and track, I got many output messages "Ask User" but there was no question inside, and then it immediately moved to "User submitted without answering questions". As a result, the created artifacts aren't as tailored to the task at hand. I tried restarting, reinstalling, changing models, etc. but nothing seems to work. Is this expected? Any suggestions to fix it?
Thank you!!
Example:
✦ I'll now guide you through a series of questions to build a comprehensive specification (spec.md) for this track.
This will help clarify the exact scope and verification strategy for forking the dependency.
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Ask User │
│ │
│ User submitted without answering questions. │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Ask User │
│ │
│ User submitted without answering questions. │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ Now I will create an implementation plan (plan.md) based on the specification.
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ✓ Ask User │
│ │
│ User submitted without answering questions. │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
✦ I'll now check existing tracks and create the necessary files for the new track.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior by running the setup and track commands and compare the repeated empty “Ask User” prompts with the expected question flow. Trace the Ask User interaction entry point and inspect how submitted question content is passed through; done means questions are displayed and the user can answer them before spec.md and plan.md are created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100