Summary
complyctl --help exposes a completion subcommand and global flags -d/--debug and
-w/--workspace that the getting-started never mentions. The page reads as the command list
while silently omitting part of the surface.
Affected
- Page:
content/docs/getting-started/_index.md
- Reference:
complyctl --help
Detail
complyctl --help ships completion, plus global flags -d/--debug and -w/--workspace,
none of which the page mentions. These are discoverable and mostly cobra built-ins, so this
is minor — but a reader treating the page as the canonical command list will not learn they
exist.
Suggested fix
Mention the global flags (-w/--workspace, -d/--debug) near the workspace and
troubleshooting material, and note completion where shell setup is discussed. A short
"full command reference: see complyctl --help" pointer would also cover this. (See the
related issue on the undocumented COMPLYTIME_* environment variables.)
Related: #63
Issue created with the help of Claude Opus 4.6
Summary
complyctl --helpexposes acompletionsubcommand and global flags-d/--debugand-w/--workspacethat the getting-started never mentions. The page reads as the command listwhile silently omitting part of the surface.
Affected
content/docs/getting-started/_index.mdcomplyctl --helpDetail
complyctl --helpshipscompletion, plus global flags-d/--debugand-w/--workspace,none of which the page mentions. These are discoverable and mostly cobra built-ins, so this
is minor — but a reader treating the page as the canonical command list will not learn they
exist.
Suggested fix
Mention the global flags (
-w/--workspace,-d/--debug) near the workspace andtroubleshooting material, and note
completionwhere shell setup is discussed. A short"full command reference: see
complyctl --help" pointer would also cover this. (See therelated issue on the undocumented
COMPLYTIME_*environment variables.)Related: #63
Issue created with the help of Claude Opus 4.6