_Kerman
0348599f04
# Conflicts: # docs/event-producer-consumer.i18n.yaml # docs/event-producer-consumer.md # docs/event-producer-consumer.zh.md # packages/acp/acp/tests/harness.ts # packages/api/session-controller/README.i18n.yaml # packages/api/session-controller/README.md # packages/api/session-controller/README.zh.md # packages/api/session-controller/tests/commands-queue-attachment.host.spec.ts # packages/context/agent-instructions/tests/agent-instructions.e2e.ts # packages/fs/tool-fs/tests/harness.ts # packages/preset/agent-presets/tests/invariant.spec.ts # packages/preset/agent-presets/tests/mount.spec.ts # packages/preset/agent-presets/tests/remote.spec.ts # packages/test-support/agent-loop-testkit/package.json
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.