You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Separate CLI help scope from help format: --recursive controls one-level vs recursive expansion, --output controls plain/json/yaml/markdown rendering, and the two are independent (so --help --recursive --output markdown is a recursive Markdown export)
Make plain --help one-level by default for human readers, with 'sub --help' scoping to that subcommand; agents and doc generation opt into the full surface with --help --recursive
Add a pre-clap help handler that scans argv before parsing so --help combined with --recursive/--output is honored instead of being short-circuited by clap's built-in help, while a bare --recursive without --help falls through to the application's own parser
Add structured JSON and YAML help output as command-tree schemas, alongside plain and markdown, with markdown kept help-only and not a general business output format
Replace the dedicated --help-markdown flag with --help --recursive --output markdown; keep cli_render_help and cli_render_help_markdown as recursive wrappers
Implement the orthogonal scope/format help model consistently across Rust, Go, Python, and TypeScript with matching examples, tests, READMEs, skill, and spec