> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paperzilla.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How do feedback signals work in the CLI?

> CLI feedback is attached to a project recommendation, not to the canonical paper.

export const AiAgents = ({path}) => <Tip>
    <b>AI agents</b>: This page is available as <a href={path + '.md'}>markdown</a>. See also the <a href="/llms.txt">docs index</a> and <a href="/llms-full.txt">full docs</a>.
  </Tip>;

<AiAgents path="/answers/how-do-feedback-signals-work-in-the-cli" />

Feedback in the CLI is project-specific.

That means you leave feedback on a recommendation in one project, not on the canonical paper itself.

Use:

```bash theme={null}
pz feedback <project-paper-id> upvote
pz feedback <project-paper-id> upvote --json
pz feedback <project-paper-id> star
pz feedback <project-paper-id> downvote --reason not_relevant
pz feedback clear <project-paper-id>
pz feedback clear <project-paper-id> --json
```

`clear` is a subcommand, so the valid syntax is `pz feedback clear <project-paper-id>`.

`pz feedback ... --json` returns the feedback object. `pz feedback clear ... --json` returns a small confirmation envelope because the clear endpoint returns no body.

The feedback values map to the same ideas as the app:

* `upvote` = useful
* `star` = very useful
* `downvote` = not for me

Optional downvote reasons:

* `not_relevant`
* `low_quality`

This matters because the same canonical paper can appear in multiple projects. One project may treat it as highly relevant, while another may treat it as a poor fit.

Use [CLI](/guides/cli) for the full command reference, and [Why should I rate papers in the feed?](/answers/why-rate-papers-in-feed) for the product reason behind these signals.