> For the complete documentation index, see [llms.txt](https://docs.khotan.com/llms.txt). A markdown version of any page is available at its `index.md` URL.

# 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 <customer>. 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:
- `--kind` — feature_request, direction, docs_gap, bug, or other. (required, body)
- `--title` — One line, up to 200 characters. (required, body)
- `--proposal` — What should be added or changed, up to 4,000 characters. (required, body)
- `--situation` — What you were doing: the task, its goal, and what you tried. Up to 4,000 characters. (required, body)
- `--reason` — Why you are sending it: what you had to do instead, and what the change would let you or your user do. Up to 4,000 characters. (required, body)
- `--origin` — user when a person asked you to send it, or agent when you decided to. (required, body)
- `--workaround` — What you did instead, up to 4,000 characters. (optional, body)
- `--impact` — blocked, workaround, or nice_to_have. (optional, body)
- `--area` — api, cli, mcp, slack_agent, dashboard, templates, skills, docs, or other. (optional, body)
- `--capability-ids` — Up to 10 Khotan action ids this is about, such as context.create. A requested action may not exist yet. (optional, body)
- `--thread-id` — Your own conversation or session id, such as a Cursor chat id. (optional, body)
- `--model` — The model you are running as. (optional, body)
- `--client` — The agent product you run in, such as cursor or claude-code. (optional, body)

Examples:
- `khotan feedback submit --kind feature_request --origin agent --title "Append a section to DESIGN.md" --proposal "..." --situation "..." --reason "..."`

<!-- generated from khotan catalog v2026-10-30 (adapter 0.10.0); do not edit by hand -->