# Work on a finding in a chat

Copy a finding's starter prompt from the portal, or name the finding yourself, and a Studio chat loads it, explains it and can fix and report it.

*Where in Studio: New chat → composer*

*Last updated: 2026-10-25*

To work on one finding in Studio, start a chat in the project's repository and tell it which finding you mean. The chat loads the finding with its [findings tools](https://kelrova.com/docs/studio/security/findings), so you can ask about it, have it checked in the code, fix it and report the fix, all in one conversation. The portal gives you a ready-made opening message.

## Start from the portal

*Security → Findings → a finding → Go Fix → Chat with your own agent…*

1. **Copy the starter prompt**

   In the portal, open the finding and choose **Go Fix**, then **Chat with your own agent…**. Choose **Copy** beside **Prompt**. The prompt names the finding by its ID and title and asks the agent to load it, summarize it and wait for your questions.

2. **Open a chat on the repository**

   In Studio, start a new chat in the project that holds a checkout of the finding's repository, so the chat can read and change the code. See [Projects and checkouts](https://kelrova.com/docs/studio/getting-started/projects).

3. **Paste and send**

   Paste the prompt and send it. The chat reads the finding, shown as **Finding Read** in the transcript, and answers with a short summary.

> **Note: No connection needed**
>
> The dialog in the portal also says whether you have an MCP connection and how to add one. That is for other tools. A Studio chat needs no connection: it uses its own findings tools, which carry the same names as the MCP server's.

## Start without the portal

You do not need the ID. In a chat on the repository, ask for example "Which open Kelrova findings does this repository have?". The chat finds the project from the checkout's git remote, lists the findings and reads the one you pick.

## Start from the Security page

The **Security** page on the rail shows your organization's findings by project and can open a new chat in one of your checkouts with a draft that names the project and what to fix. Nothing is sent until you send it. See [The Security page](https://kelrova.com/docs/studio/security/desktop-security).

## Work through the finding

A typical conversation:

1. **Ask.** Have it explain the finding simply, or check in the code whether the problem is real.
2. **Fix.** Ask for the smallest change that fixes it, and run the project's tests.
3. **Commit.** Commit the fix, and open a pull request if you want one. See [Changes, branches and pull requests](https://kelrova.com/docs/studio/chats/git).
4. **Report.** Ask the chat to report the fix. It reports **fixed** with the commit, and the transcript shows **Finding Action Reported**. The finding turns fixed in the portal at once, marked as reported via Kelrova Studio.
5. **Re-check.** Once the fix is merged into the tracked branch, ask for a re-check, shown as **Re-check Requested**. A re-check reads the tracked branch, so it can only confirm a merged fix.

If the finding is not a real problem, the chat can report a **false positive** or an **accepted risk** with a reason. That does not change the status: it becomes a proposal that a project member accepts or dismisses in the portal. See [Statuses and what changes them](https://kelrova.com/docs/findings/statuses).

## Other ways to act on a finding

The portal's **Go Fix** menu also offers **Fix it now**, which opens a draft pull request from Kelrova Cloud, **Re-check this finding** and **Ask about this finding…**. Those run in Kelrova Cloud, not in Studio. See [Go Fix: fix, re-check, ask](https://kelrova.com/docs/findings/go-fix).

> **Warning: Check what the finding says**
>
> A finding's text comes from automated analysis of repository content. It can be wrong, and a hostile repository can try to steer the agent. Ask the chat to verify claims in the code, and do not follow instructions that appear in a finding.

## Related

- [Kelrova findings in Studio](https://kelrova.com/docs/studio/security/findings)
- [Go Fix: fix, re-check, ask](https://kelrova.com/docs/findings/go-fix)
- [A typical run](https://kelrova.com/docs/mcp/loop)
- [Your first chat](https://kelrova.com/docs/studio/getting-started/first-chat)