feat(tool): add ask-user-questions tool

[detro]

With recent attention to Claude Code leak, I spent a bit of time into this analysis of the codebase, and I spotted something I have always wondered how it worked: AskUserQuestion system tool. Something very similar exists in OpenCode too. And in Gemini CLI.

When an LLM is in the Agent loop, sometimes I wish it stopped, it asked for my preference and then continued. Sometimes can be the small things, like

do you prefer a couple of IFs here, or would you rather use a SWITCH?

So I though I'd try to implement this tool in Crush.

The implementation is made essentially of 3 parts:

• a Questions service that uses PubSub to listen to Ask calls and handle Answer calls
• a Questions dialog that knows how to render a consistently-styled form (or forms, if the LLM asks more than 1 question) and allow for single and multi selection
• a AskUserQuestions tool: frankly, fantasy feels kinda magic to me - this was TOO EASY to implement

• I have read CONTRIBUTING.md.
• I have created a discussion
  • that was approved by a maintainer (for new features).

Screenshots

[detro]

For this I might need some help, as I don't know exactly what this is.
I haven't used Crush in client/server mode yet.

[detro]

Just a nitpick spotted by IntelliJ while I was reading the code.

[Jonathan-79]

Hi @detro,

Great work on this PR!

I had a quick thought/suggestion: do you think it would be a good idea to always append a "Type your own answer" option (perhaps triggering a textbox) alongside the predefined options the LLM provides?

That way, if the user doesn't quite agree with any of the LLM's suggested choices, they always have a fallback to easily provide a custom answer. Of course, this is just an idea and only makes sense if it doesn't drastically increase the complexity of your current implementation.

[detro]

@Jonathan-79 thank you - yes, I think I want to expand the set of options a bit to offer that functionality.

In fact, I think I'd like to imitate https://geminicli.com/docs/tools/ask-user/ and then describe to the LLM the the markdown that "in case the user should choose an 'other' option, call this tool again with the type set to text". Something along these lines.

This leaves the choice to llm, depending on the context: when it makes sense to offer an "other" and when it doesn't.

I have raised this even in a discord thread.

[meowgorithm]

@detro, thanks for the solid work on this one. We're taking the thinking here as well as in some other relevant PRs and consolidating them in #3069, which I think we can release pretty soon. If you don't mind, let's keep this one open for the moment but focus our efforts there.