git:20260828.9fa83e4 to git:20260901.ec2655a

13 added, 3 removed. Audit A to A.

---

name: submitting-feedback

description: Submits user-approved feedback about Letta Code or the current agent to the Letta team. Load when the user is upset, frustrated, dissatisfied, reports poor agent behavior, or asks to send feedback. Works with cloud-hosted and local agents. Ask before submitting unless the user already explicitly requested submission.

---

# Submitting Feedback

When the user appears upset with the agent, acknowledge the problem and ask whether they want you to submit feedback to the Letta team. Do not submit merely because the user expressed frustration.

If the user says yes, or directly asks you to submit feedback:

- 1. Write a short factual message in the user's voice. Include what happened, what the user expected, and any useful error or behavior detail already present in the conversation. Do not add claims the user did not make.

- 2. Submit it with:

+ 1. Gather the relevant context already available in the conversation and environment. If a detail essential to understanding or reproducing the problem is missing, ask the user one focused question before submitting. Do not invent missing details.

+ 2. Write a concise, factual report in your own voice as the agent. Do not impersonate the user or make the report sound user-authored. The first line must disclose: `Agent-submitted feedback on behalf of the user.`

+ Include:

+ - Your agent name.

+ - Who you are working with (the user's name or role, if known; otherwise say `user not identified`).

+ - The task or goal underway when the problem occurred and enough surrounding context to understand why it mattered.

+ - What actually happened, what the user expected, and the impact on the task.

+ - Concrete evidence already available, such as exact error text, the failed command or action, relevant paths or links, and reliable reproduction steps. Distinguish what the user reported from what you observed or inferred.

+ Prefer specific nouns and observable behavior over generic judgments. Do not submit context-free summaries such as “the feature is broken,” “the UX should be improved,” or polished product-language filler. Keep unknowns explicit rather than guessing.

+ 3. Submit it with:

```bash

letta feedback --message '<feedback>'

```

- 3. Tell the user whether submission succeeded. If it failed, report the safe CLI error and do not claim the team received it.

+ 4. Tell the user whether submission succeeded. If it failed, report the safe CLI error and do not claim the team received it.

Do not include secrets, credentials, unrelated conversation content, or private file contents. The command adds the current agent and conversation identifiers so the team can find the relevant run.