Summary
Running trio analyze as an end user currently prints a <think>...</think> block with internal reasoning in normal CLI output.
Reproduction
trio analyze ~/Downloads/photo.jpg -q "What's here?"
Actual behavior
The command succeeds, but the output includes internal reasoning wrapped in <think>...</think>.
Expected behavior
For a user-facing CLI command, the default output should contain only:
- model/loading status
- analysis status
- final answer
Internal reasoning should not be printed unless explicitly requested via a debug/verbose mode.
Impact
The command works, but the UX is noisy and confusing for end users. It makes the CLI feel like a debugging surface rather than a polished product command.
Summary
Running
trio analyzeas an end user currently prints a<think>...</think>block with internal reasoning in normal CLI output.Reproduction
Actual behavior
The command succeeds, but the output includes internal reasoning wrapped in
<think>...</think>.Expected behavior
For a user-facing CLI command, the default output should contain only:
Internal reasoning should not be printed unless explicitly requested via a debug/verbose mode.
Impact
The command works, but the UX is noisy and confusing for end users. It makes the CLI feel like a debugging surface rather than a polished product command.