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

# Findings commands

> List the problems a fix item covers, and record whether the fix resolved each one.

These commands read the problems a fix item covers, and record whether its change fixes each one. A fix item is a work item made from an issue filed for a problem. Its build runs these commands, and you can run them yourself. See [Record a fix result](https://docs.outerlayer.ai/findings.md#record-a-fix-result).

To record a finding, see [`outerlayer emit finding`](https://docs.outerlayer.ai/reference/cli-emit#outerlayer-emit-finding).

Every command on this page takes these options:

| Option | Default | What it does |
| - | - | - |
| `--json` | off | Machine-readable output. |
| `--url <url>` | see [Credential resolution](https://docs.outerlayer.ai/reference/cli.md#credential-resolution) | Gateway base URL. |
| `--app-id <id>` | see [Credential resolution](https://docs.outerlayer.ai/reference/cli.md#credential-resolution) | Factory id. |

Each command exits 0 on success. It exits 1, with the reason on stderr, when it refuses or the input is not valid. A command connects the repository to a factory on its own when exactly one factory fits. See [Automatic connection](https://docs.outerlayer.ai/reference/cli-cloud.md#automatic-connection).

## outerlayer findings show

List the problems a fix item covers, with each problem's id, its reports and its result.

It needs the `work.read` permission. Keys made with the Agent and Runner presets hold it.

```bash theme={"system"}
outerlayer findings show [--item <number>] [--json]
```

| Flag | Default | What it does |
| - | - | - |
| `--item <number>` | the session's item | The work item, by its number on the factory. Required outside a session started on a work item. |

```bash theme={"system"}
outerlayer findings show --item 412
```

It prints each problem with its title, id, file, reports and result:

```text theme={"system"}
Item #412 covers 1 problem:

The lint script exits 0 when a step is skipped
  id: 0b6f3e1a-1111-4222-8333-444455556666
  file: scripts/lint.sh
  reports (2):
    - The lint script exits 0 when a step is skipped (scripts/lint.sh, 1a2b3c4)
    - Lint passes when a step is skipped (scripts/lint.sh)
  result: no result yet
```

With `--json`, the output is `{ "problems": [ ... ] }`. Each problem has `id`, `title`, `file`, `issueKey`, `result` and `reports`. `result` is `null` until a build records one. Then it has `result` (`fixed` or `not_fixed`), `note` and `recordedAt`. Each report has `findingId`, `title`, `file`, `headSha`, `itemKey`, `minutesLost` and `reportedAt`.

## outerlayer findings result

Record the build's result for one problem.

It needs the `evidence.insert` permission. Keys made with the Agent and Runner presets hold it.

```bash theme={"system"}
outerlayer findings result <problem> --fixed|--not-fixed --note "<text>"
                                     [--item <number>] [--json]
```

`<problem>` is the problem's id: the full UUID that `findings show` prints.

| Flag | Default | What it does |
| - | - | - |
| `--fixed` | none | The change resolves the problem. Pass this or `--not-fixed`. |
| `--not-fixed` | none | The change does not resolve the problem. Pass this or `--fixed`. |
| `--note "<text>"` | required | One sentence that says what you did or why the problem remains. |
| `--item <number>` | the session's item | The work item, by its number on the factory. Required outside a session started on a work item. |

Pass exactly one of `--fixed` and `--not-fixed`. A second result for the same problem replaces the first.

The command refuses a problem that the item does not cover. An item stops covering its problems when its fix merges or its issue closes.

```bash theme={"system"}
outerlayer findings result 0b6f3e1a-1111-4222-8333-444455556666 --fixed --note "Added the missing variable to the lint script."
```

With `--json`, the output has `problemId`, `result`, `note` and `item`.

A problem counts as fixed only when the build reports it fixed and its pull request merges. See [When a problem needs a fix again](https://docs.outerlayer.ai/findings.md#when-a-problem-needs-a-fix-again).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.