The + button and a typed / open one menu with an Add section (File, Goal, Plan, Feedback) and a Commands section (Compact, Permission, Model, Export) in usage order; rows carry a glyph, a localized title and description, and the command name as an alias where the localized title differs. Built-in Host rows get their face from the ui-commands dictionaries when the catalog description is the canonical English text. A menu pick fills the locale's claim token (/计划 ) while the submission executes the catalog name, and a typed localized token resolves on Space and Enter in every locale. The File row is a new action contribution kind that opens the composer's file picker through the scoped slash/input-pick-files event; the paperclip button is removed and the + button reads "Add files or run commands".
description, kind
| description | kind |
|---|---|
| The feedback package group: user feedback on sessions and assistant messages, for users and maintainers choosing, composing, or debugging feedback capture. | package-group |
feedback/ — recorded human feedback
English | 中文
Summary
The feedback group collects human opinions about the harness's work: users can submit a free-text remark about a whole session, and rate or annotate individual assistant messages. Neither kind of feedback reaches the model — these are signals about the output, never input to it. Users record a session remark with the /feedback command; product surfaces read and change per-message ratings through the messageFeedback service. The two packages are independent: session remarks and per-message ratings do not interact. This page maps the group; the package READMEs and the feedback subsystem page own the per-package contracts.
Table of Contents
Packages
| Package | Role |
|---|---|
command-feedback |
A /feedback command that records a free-text session remark with one command, without a model turn |
message-feedback |
Per-message ratings and notes, served to product surfaces through the messageFeedback service |
Session remarks are a one-way signal: recording one is safe at any point in a conversation and never changes what the model sees. With a feedback-gated sharing policy, recording a session remark is what releases the session for sharing.
Per-message ratings and notes are stored with the session, survive restarts, and never appear in model history or telemetry.
Related documentation
- Feedback subsystem — the message-feedback types, service contract, and Web consumer.
- Session telemetry subsystem — the sharing policy disclosed by the
/feedbackacknowledgement. - Anonymous user identity — the per-harness-home id embedded in the feedback acknowledgement.
Dev Note
None.