L
Hive
--quiet and --verbose flags are not documented in --help
GitHub issue · Open
Source
tuist/tuist #8782
Updated
Jun 11, 2026
Domains
CLI
Why is this needed?
--quiet and --verbose flags are not documented in --help output.
--quiet is especially important for ai agents as it suppresses details that are usually irrelevant when installing dependencies or building code, but agents won’t discover it on their own if it’s not documented.
Steps to address the need
It seems like these flags are handled differently than regular ArgumentParser flags, so I’m not sure exactly what the path forward is here.
Investigate, reproduce, or fix this item in an isolated repository. Each Flight preserves its outcome and agent session.
New Flights are paused
Configure model inference, GitHub, and a sandbox provider to start another Flight. Existing results remain available below.
No Flights yet
Start a Flight and preserve its objective, outcome, and session here.
L
D
dosubot[bot]
Nov 27, 2025
Hi @robmaceachern! I’m Dosu and I’m helping the tuist team.
You’re right—--quiet and --verbose are not documented in Tuist’s --help output because they are handled outside of ArgumentParser. The CLI strips these flags from the argument list before parsing, so ArgumentParser never sees them and can’t include them in the generated help text. Instead, Tuist checks for these flags directly in CommandLine.arguments, sets environment variables, and configures logging accordingly. This means they work, but users (and AI agents) won’t discover them via --help unless they’re registered as proper flags or manually added to the help output.
To document these flags in --help, you’d need to either register them with ArgumentParser as global options or explicitly append their descriptions to the help text before filtering them out. This is a common challenge for global flags handled outside the parser in Swift CLI tools.
Reference
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.
