It would be nice to extend the kernels CLI with a command to describe a kernel from a local path or a Hub ID, e.g. kernels info <name>.
This came out of a broader discussion on improving the kernels CLI experience (partly motivated by making kernels more amenable to agentic workflows, similar to kernel-builder PR #636).
Context on related ideas:
- Checking variant compatibility for a given machine — already supported via
kernels versions <repo> (which lists each variant and why it is/isn't compatible). A --json flag could be added for machine-readable output, though it's unclear how much that helps LLMs.
- Describing a kernel — not yet available;
kernels info <name> would fill this gap by surfacing metadata/description for a kernel given a local path or Hub ID.
Requested by Sayak Paul - Slack thread - Agent trace
It would be nice to extend the
kernelsCLI with a command to describe a kernel from a local path or a Hub ID, e.g.kernels info <name>.This came out of a broader discussion on improving the
kernelsCLI experience (partly motivated by making kernels more amenable to agentic workflows, similar to kernel-builder PR #636).Context on related ideas:
kernels versions <repo>(which lists each variant and why it is/isn't compatible). A--jsonflag could be added for machine-readable output, though it's unclear how much that helps LLMs.kernels info <name>would fill this gap by surfacing metadata/description for a kernel given a local path or Hub ID.Requested by Sayak Paul - Slack thread - Agent trace