Refactor interactive flows to use the AskUser tool
#104
+543
−390
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-review-recommendations feat(conductor): make review recommendations more conversational
moisgobg
changed the title
AskUser toolAskUser tool
moisgobg
force-pushed
the
feat/ask-user-tool-integration
branch
from
03f0dc5 to
276994e
Compare
added 2 commits
February 9, 2026 22:14
This change ensures users see the overview of the initialization process before the system checks for an existing state file, providing better context for the setup workflow. Resolves: #81 Change-Id: Ibb1499be24cc9cb0290eb2c5e871c9d296aeac73
Change-Id: Id1f84748d29877b8a5794bb4cd02abdbc753e11d
moisgobg
force-pushed
the
feat/ask-user-tool-integration
branch
from
276994e to
57055df
Compare
hminooei
approved these changes
Feb 9, 2026
commands/conductor/implement.toml
Outdated
| 1. Perform an exact, case-insensitive match for the provided name against the track descriptions you parsed. | ||
| 2. If a unique match is found, confirm the selection with the user: "I found track '<track_description>'. Is this correct?" | ||
| 3. If no match is found, or if the match is ambiguous, inform the user and ask for clarification. Suggest the next available track as below. | ||
| 2. If a unique match is found, confirm the selection with the user using the `ask_user` tool: |
There was a problem hiding this comment.
Not sure if this is feasible, but ideally we wanted to use something like AskUser.name to avoid issues in case the AskUser name changes.
There was a problem hiding this comment.
I think we need to request for this capability:
This is what is supported right now as Runtime Variable Support of commands:
{{args}}: Injects the arguments provided by the user.!{command}: Executes a shell command and injects the output.@{file}: Injects the content of a file.
Could you please create a ticket for gemini cli team to add the support for __tool__{} inside command.toml files. You can reference this PR as the need.
feat(review): update review process to commit fixes and update plan
fix(conductor): move pre-initialization overview before resume check
Migrate `ask_user` calls in `implement.toml`, `newTrack.toml`, `revert.toml`, `review.toml`, and `setup.toml` to the new schema: - Use the `questions` array parameter. - Format options with `label` and `description`.
moisgobg
force-pushed
the
feat/ask-user-tool-integration
branch
from
aa1f199 to
12b3b36
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To improve the user experience and ensure a consistent, structured interaction model across the Conductor extension, we have migrated all legacy text-based prompts to the integrated
AskUsertool. This transition allows for more intuitive UI elements (like single/multi-choice menus and yes/no toggles) and enables better handling of human-in-the-loop interactions during automated workflows.fixes: #105
related PR: #90