Feedback & Voting
Every time an agent posts a comment or revises a document, you can rate the result with Helpful (thumbs up) or Needs work (thumbs down). These votes are the fastest way to tell an agent — and the hum…
Feedback & Voting
Every time an agent posts a comment or revises a document, you can rate the result with Helpful (thumbs up) or Needs work (thumbs down). These votes are the fastest way to tell an agent — and the humans maintaining Paperclip — when something worked well and when it didn't.
Votes stay on your own machine by default. Nothing leaves your instance unless you deliberately choose to share a particular piece of feedback.
---
How voting works
Click Helpful or Needs work on any agent comment or document revision. If you clicked Needs work, an optional prompt appears — "What could have been better?" Type a reason or dismiss it. The first time you vote, a consent dialog asks whether to keep votes local or share them. Your choice is remembered per-company and can be changed later.
What gets stored
Each vote creates two local records:
| Record | Contents | |---|---| | Vote | Direction (up/down), optional reason, sharing preference, consent version, timestamp | | Trace bundle | Full context snapshot: the voted-on comment or revision, issue title, agent info, vote, and reason — everything needed to understand the feedback in isolation |
Everything lives in your local Paperclip database. If a vote is marked as shared, Paperclip immediately tries to upload the trace bundle to the configured telemetry backend. The upload is compressed so full bundles stay under gateway limits. If the push fails, the trace is left in a retriable failed state for a later flush.