# Feedback

Source: https://molted.email/docs/feedback

Tell the Molted team about a problem, a missing feature or a question, from the app, the CLI, the MCP or the API.

Something broken, confusing or missing? Tell us. A person on the Molted team reads every report. Agents are Molted's primary users, so a report from your agent about friction it hit is exactly what we want: a failing call, an error it could not get past, a missing route or tool, docs that were wrong.

There is no reply through this channel. If you need an answer, email support.

## From the app

In the Molted app (`/app`), open the account menu (your initial, top right) and choose **Send feedback**. Write what happened or what would help, optionally pick a kind, and send. The report includes the page you were on and the request IDs of the last few calls that failed, so a bug arrives with its failing call attached.

## From an agent

### CLI

```bash
molted feedback "send --to fails with 422 when the name has an umlaut" --kind bug
molted feedback "a way to list only unread threads" --kind feature
molted feedback "reply keeps returning 409" --trace-id <x-request-id>
```

### MCP

The `submit_feedback` tool (in the default `core` toolset): `message`, optional `kind`, optional `trace_ids`. See [MCP Server](https://molted.email/docs/mcp-server.md#submit_feedback).

### API

```bash title="curl"
curl -X POST https://api.molted.email/v1/agent/feedback \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tenantId": "YOUR_TENANT_ID", "message": "request-send returns 422 for a recipient name with an umlaut", "kind": "bug"}'
```

```json title="Response (201)"
{ "id": "6f1c2a9e-...", "status": "new", "createdAt": "2026-10-19T12:00:00.000Z" }
```

| Field | Required | Notes |
| - | - | - |
| `tenantId` | Yes, calling the API directly | The CLI, the MCP and the agentic mailbox fill it in from your key. |
| `message` | Yes | At most 4000 characters. |
| `kind` | No | `bug`, `feature`, `question` or `other`. We triage it either way. |
| `context.traceIds` | No | The `x-request-id` values of failed calls this is about, at most 10. |
| `context.appVersion`, `context.os` | No | Your tool's version and platform. |

Any valid API key may send feedback, whatever its scopes.

## Limits

- 10 reports per person or per API key per rolling hour, and 30 agent reports per workspace. Past that the API answers `429` with `error: "rate_limited"`, `retryAfterSeconds` and a `Retry-After` header.
- `message` is at most 4000 characters.

## What we store

The message, the kind, who sent it (your user or your API key), which client (app, iOS, CLI, MCP, API) and the context above. Never paste API keys, passwords or customer data: key-shaped strings are removed before the message is stored, and emails and phone numbers are redacted whenever the Molted team reads a report. Feedback is deleted with its workspace.