Usability: verbosity handling and execution-policy

[combsbj]

Subject: Usability issues — verbosity handling and execution policy

Summary

• Issue A (verbosity): The assistant repeatedly ignored explicit user instructions to produce concise/minimal outputs and continued producing verbose progress reports.
• Issue B (execution policy): The assistant executed environment-specific commands (for example git) without verifying applicability to the current workspace.

Impact

• Both behaviors reduce trust and efficiency: verbosity wastes review time; unverified environment actions can fail or cause side effects.

Repro steps (high level)

1. Ask for concise output (e.g., "Stop the verbose explanations and just produce the finished product.").
2. Observe assistant continues verbose multi-step outputs.
3. Observe assistant attempting environment actions without confirming context (e.g., running git commit in a folder that isn't a git repo).

User preference / consent

• The user does consent to automatic execution when applicable and verified. They prefer:
  • Automatic execution of relevant commands that progress toward the final outcome.
  • No execution of non-applicable commands (the assistant must verify applicability first).
  • No unprompted execution of commands outside the requested scope.

Requested fixes

• Honor an explicit session-level verbosity preference until revoked.
• Require the assistant to verify applicability before running environment commands, and obtain confirmation when unsure.
• Provide a strict "minimal mode" that returns only essential results (file edits or a one-line confirmation).

[chrmarti]

Please update to the latest version and check if the problem is still there.