Files
deepseek-harness/packages/feedback
_Kerman e5a5401228 Merge remote-tracking branch 'origin/master' into xtr/durable-inbox-recovery
# Conflicts:
#	docs/subsystems/session-projection.i18n.yaml
#	docs/subsystems/session-projection.md
#	docs/subsystems/session-projection.zh.md
#	packages/context/agent-instructions/tests/agent-instructions.spec.ts
#	packages/core/agent-loop/README.i18n.yaml
#	packages/core/agent-loop/README.md
#	packages/core/agent-loop/README.zh.md
#	packages/core/agent-loop/tests/cancel.spec.ts
#	packages/core/agent/README.i18n.yaml
#	packages/core/agent/README.md
#	packages/core/agent/README.zh.md
#	packages/llm/llm-retry/tests/retry.spec.ts
#	packages/session/session-projection/README.i18n.yaml
#	packages/session/session-projection/README.md
#	packages/session/session-projection/README.zh.md
2026-08-26 17:54:45 +08:00
..

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.

Dev Note

None.