> ## Documentation Index > Fetch the complete documentation index at: https://docs.withgauge.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For API and SDK launches, integration testing, and ongoing coding-agent checks, start with Gauge Agents: > - [Gauge Agents overview](https://docs.withgauge.com/agents/index.md) > - [Gauge Agents quickstart](https://docs.withgauge.com/agents/quickstart.md) > - [Create and inspect an eval](https://docs.withgauge.com/agents/guides/create-an-eval-and-run-an-experiment.md) > - [Agent Experience: diagnose integration failures](https://docs.withgauge.com/agents/concepts/agent-experience.md) > - [Agent Preference: measure product selection](https://docs.withgauge.com/agents/concepts/agent-preference.md) > - [GitHub PR checks](https://docs.withgauge.com/agents/guides/github-pr-checks.md) > For AI search visibility and AEO, start with [Gauge Chat](https://docs.withgauge.com/introduction/welcome.md). # Manage issues > Mark issues fixed or muted, and rerun past sessions to check that a fix works. Each [issue](https://docs.withgauge.com/agents/concepts/issues.md) has a status. Use the status to track which issues you fixed and which do not apply to you. Rerun past sessions to check if an issue is gone before you mark it fixed. ## Issue status | Status | Meaning | | - | - | | Open | Agents still hit this issue. All new issues are open. | | Fixed | You shipped a change for the issue. Gauge reopens it when a later run shows it again. | | Muted | The issue does not apply to you, or it is by design. It never reopens. | The **Issues** tab shows open issues. Use the **Open**, **Fixed**, and **Muted** control at the top right to see the others. Each option shows its count. ## Mark an issue fixed Mark an issue fixed after you ship a change for it. 1. Open the **Issues** tab of Agent Experience or Agent Preference. 2. Open the **Actions** menu on the issue. 3. Click **Mark fixed**. The issue moves to **Fixed** and shows who marked it fixed and when. ### When a fixed issue comes back Gauge reopens a fixed issue when a run that started after the fix shows the issue again. The issue moves to **Open** and gets a **Came back** badge. Runs that started before the fix do not reopen it. ## Mute an issue Mute an issue when it is not relevant, or when it comes from a product decision you do not plan to change. Open the **Actions** menu on the issue and click **Mute**. A muted issue still collects findings, so the same problem does not come back as a new issue. To make it open again, click **Unmute**. ## Reopen an issue To move a fixed issue back to **Open**, open the **Actions** menu and click **Reopen**. ## Check if an issue is gone A recheck runs past sessions of the issue again with your current product, docs, and Skills. Gauge analyzes the reruns and shows how many still have the issue. On an open issue, the action is **Recheck**. On a fixed issue, the action is **Verify fix**. Both run the same reruns. **1. Choose the runs** Open the **Actions** menu on the issue and click **Recheck** or **Verify fix**. Gauge lists the past runs that showed the issue. It lists the latest run for each prompt, agent, and model, with the runs that showed the issue most often first. Each row shows the agent, the model, the number of sessions that showed the issue, and when Gauge last saw it. Gauge selects 3 runs by default. You can select up to 10. **2. Start the reruns** Confirm to start the reruns. Each rerun uses the task, agent, model, repository, and settings of its original run. Reruns use credits like any run. The issue shows a **Rechecking** or **Verifying** badge while the reruns run. **3. Read the result** The result shows in the issue details when Gauge has analyzed every rerun. | Result | Meaning | | - | - | | 0 of n runs | No rerun showed the issue. The issue gets a **Looks fixed** badge. | | n of m runs | Some reruns still showed the issue. | | No result | Gauge could not analyze any rerun. | Each rerun links to its run page. A check icon shows that the rerun did not show the issue. An X shows that it did. **4. Mark the issue fixed** A recheck never changes the status of an issue. If the issue looks fixed, click **Mark fixed** in the result. If you verify a fixed issue and a rerun still shows it, the issue reopens. ### Limits * You cannot recheck a muted issue. Unmute it first. * An issue can have one recheck at a time. * Repositories that the runs use must be ready. * A check that does not finish in 24 hours shows the result for the reruns that Gauge analyzed. ## Manage issues from the CLI > [!NOTE] > > These CLI commands use hosted Gauge. The CLI uses the local backend by > default, so set hosted once after you sign in, or add `--hosted` to each > command. See [Choose a backend](https://docs.withgauge.com/agents/guides/cli.md#choose-a-backend). > > ```bash theme={null} > gauge config set backend hosted > ``` ```bash theme={null} gauge issues list --status fixed # or open, muted, all gauge issues fix # mark fixed gauge issues mute # mute gauge issues reopen # back to open; also unmutes ``` `gauge issues recheck` (alias `verify`) shows the runs it will repeat. It starts the reruns only when you add `--confirm`: ```bash theme={null} gauge issues recheck # preview the default runs gauge issues recheck --confirm # start the reruns gauge issues recheck --run --confirm # choose the runs ``` `gauge issues get ` shows the result when the reruns are analyzed. For a coding agent, run `gauge instructions issues`. ## Manage issues with the API All requests use the [API authentication](https://docs.withgauge.com/agents/guides/api-authentication.md) of other Gauge Agents endpoints. | Request | Purpose | | - | - | | `GET /api/v1/orgs/{org}/issues` | List issues. Use `kind=problems` or `kind=reasons`, and `status=open`, `fixed`, `muted`, or `all`. | | `GET /api/v1/orgs/{org}/issues/{id}` | Get one issue with its status, latest check, and findings. | | `PATCH /api/v1/orgs/{org}/issues/{id}` | Set the status: `{"status": "FIXED"}`, `"MUTED"`, or `"OPEN"`. | | `GET /api/v1/orgs/{org}/issues/{id}/recheck` | List the past runs a recheck can repeat. `recommended` marks the default runs. | | `POST /api/v1/orgs/{org}/issues/{id}/recheck` | Start a recheck. Send `{"runIds": [...]}` to choose the runs, or no body for the default. | ```bash theme={null} curl --request PATCH \ --url https://agents.withgauge.com/api/v1/orgs/acme/issues/$ISSUE_ID \ --header "Authorization: Bearer $GAUGE_API_TOKEN" \ --header "Content-Type: application/json" \ --data '{"status": "FIXED"}' ``` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.