Summary
Please make command help more complete, especially for subcommands that rely on global options or JSON payload fields.
Current friction
Running:
linear issues list --help
currently shows only:
Usage: linear issues list [options]
List issues
Options:
-h, --help display help for command
But in practice, global flags like --json, --team, --limit, and --cursor affect the command. Those are visible at the root help level, but not where users naturally look while working with a specific subcommand.
Requested improvements
- Show inherited global flags in subcommand help.
- For
create / update, show accepted --input fields or link directly to the relevant docs section.
- For list commands, show supported filters and pagination flags together.
- Consider examples in each resource command's help.
Why this matters
The CLI may support more than the command-specific help suggests. During real use, issues list --help made it look like no filtering or pagination options existed, which sent us into source inspection and trial/error.
Better help output would make the CLI easier for both humans and agents to use correctly.
Summary
Please make command help more complete, especially for subcommands that rely on global options or JSON payload fields.
Current friction
Running:
currently shows only:
But in practice, global flags like
--json,--team,--limit, and--cursoraffect the command. Those are visible at the root help level, but not where users naturally look while working with a specific subcommand.Requested improvements
create/update, show accepted--inputfields or link directly to the relevant docs section.Why this matters
The CLI may support more than the command-specific help suggests. During real use,
issues list --helpmade it look like no filtering or pagination options existed, which sent us into source inspection and trial/error.Better help output would make the CLI easier for both humans and agents to use correctly.