Response sometimes is too short

[younesbram]

Describe the feature or problem you'd like to solve

Depth of response should b e a little bit deeper

Proposed solution

I do understand that tokens matter and that too long of a prompt is a bad user experience. However sometiems it feels like the LLM is legit forced to only have a certain amount of words so it skips adjectives and like connecting words and expects me to understand everything from such a short explanation, and I end up asking it , explain deeper anyways.

Example prompts or workflows

Connected to GitHub MCP Server

 ● Map keys must be unique; Terraform will overwrite duplicates—there is no way to
   “add another” with the same key. Use a list of objects and synthesize unique
   keys (e.g. append index or extracted ci number) and/or add validation to catch
   accidental duplicates.

Additional context

No response

[younesbram]

If you give users the feature to CONTROL the prompt, it would be awesome. I feel like I could anyways with the user message prompt injection but like make it an actual feature you know

[RyanHecht]

Hey, thanks for this feedback! We recently made a change to make the responses more concise, but I understand wanting more verbose output! You're right, user control would be the best way to implement this