Feedback

Use the khotan CLI to operate Khotan feedback to the Khotan team. Add --json for machine-readable output; results go to stdout, diagnostics to stderr.

Commands

khotan feedback submit

Usage: khotan feedback submit --kind <string> --title <string> --proposal <string> --situation <string> --reason <string> --origin <string> [--workaround <string>] [--impact <string>] [--area <string>] [--capability-ids <a,b>] [--thread-id <string>] [--model <string>] [--client <string>]

Send the Khotan team a feature request, a product direction, a docs gap, or a bug. Any authenticated caller can send it, read-only members and the code sandbox included, because it changes nothing on the platform. Send one when Khotan lacks something you needed, when you see a better way for Khotan, its templates, skills, or design docs to work, when the docs did not answer your question, or when a person asks you to. Send it even when a workaround got the job done. Cover one topic in each submission. Explain the situation (your task, its goal, and what you tried) and your reason (what you had to do instead, and what the change would let you or your user do). Set origin to user when a person asked you to send it, and agent when you decided to. Replace names, emails, credentials, and customer data with placeholders such as . Submitting does not end your task: carry on with it afterwards. Example: kind feature_request, title "Append a section to DESIGN.md", proposal "An action that appends a section to a repository's DESIGN.md", situation "A user asked me to document empty states; I had no append action", reason "I rewrote the whole file, which risks losing their edits", origin agent.

Arguments & options:

Examples: