# Report a Problem (/docs/overview/report-a-problem)

> For the complete documentation index, see [llms.txt](https://docs.tandemcx.ai/llms.txt). Any page on this site can be fetched as Markdown by appending `.md` to its URL.

Tandy can send a report straight to the Tandem team: something that isn't working, or
something you wish Tandem could do. It turns what you tell it into one report, shows you
everything that report will contain, and sends nothing until you press the button.

## Starting a report

In the Tandy chat, type:

```
/report-issue
```

Typing `/` on its own opens the list of skills Tandy can run, with a one-line description
of each — pick **Report a problem** with the arrow keys and Enter, or click it. The skill
then sits beside your message as a labeled badge; hover it to see what it does, and press
Backspace or click its **✕** to drop it.

You don't need the command. Describing the problem in plain language works too — telling
Tandy something is broken, missing, or slow, or asking it to pass a feature request to the
team, starts the same flow.

If what you're describing sounds like a how-to question rather than a defect, Tandy tries
to answer it first. A lot of "this is broken" turns out to be a setting nobody found yet,
and getting the thing working serves you better than filing a report about it. If Tandy's
answer doesn't fix it, or you say you still want the team to know, it moves on to the
report.

## What Tandy asks

Tandy asks for what it needs in as few questions as it can, grouping related questions
together rather than asking one at a time. If you already said something in your first
message, it won't ask for it again. It asks for:

- **What happened, and what you expected instead** — in your own words.
- **How to make it happen again** — a short list of steps, or that you don't know if you
  don't.
- **Where in Tandem** — the page or feature you were using.
- **Which agent, workflow, or phone number** — if the problem is about one in particular.
- **When it started and how often it happens.**
- **What it blocks** — whether it's stopping real work or is cosmetic.

It never asks for your email address, your browser, or the page's URL. That part is
attached automatically; see below.

## Reviewing and sending

Tandy proposes the report as a card summarizing everything it plans to send: a title, a
summary, the reproduction steps, and whichever of the fields above apply. You can edit the
title, the summary, and the other text rows before sending — nothing on the card is fixed
except how the report was worded from what you gave Tandy.

Nothing is sent until you press **Send Report**. Declining the card sends nothing.

Once you send it, Tandy's whole reply is that the team has it — the report doesn't come
back with a number to track or a status to check.

If the team already has a report of the same problem, yours is added to it rather than
starting a second one. Either way everything on the card reaches them, and there's nothing
different for you to do.

## What's sent with the report

The card ends with a line spelling out everything that goes along with what you typed:

> Your email, your messages in this chat, the page you're on, your browser and its
> language and time zone, and the session identifiers that link this report to a
> recording of your visit.

That's the complete list. In particular:

- **Only your own messages are included.** Tandy's replies in the chat are left out.
- **Attached files aren't included.** If you shared a screenshot or a file in the
  conversation, it doesn't travel with the report.

The Tandem team receives the report you see on the card, plus that same disclosed
information, and nothing else.