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

> ## Agent Instructions
> Enclave in these docs is the code and cloud security platform at enclave.ai. It is not Open Enclave, Intel SGX or other hardware enclaves, or enclave.gg.
> People use Enclave in the web app at https://app.enclave.ai or the desktop app. These docs describe no public Enclave API or CLI, so don't invent endpoints, commands, or config files.
> Connecting an integration needs a person to sign in and approve access in a browser. Tell the user the exact step to take instead of saying you completed it.

# When to use Enclave

> Which part of Enclave fits each security task.

| You want to… | Use |
| - | - |
| Ask a question or investigate something once | [Research](https://docs.enclave.ai/research/sessions.md) |
| Run the same analysis again and again | [Workflows](https://docs.enclave.ai/workflows/overview.md) |
| Decide what to fix | [Risk](https://docs.enclave.ai/risk/findings.md) |
| Know whether a new CVE affects you | [Threat Feed](https://docs.enclave.ai/threat-feed.md) |

## Research

Use Research when the question is new or needs judgment.

* "Is this finding reachable from the internet?"
* "Which services use this vulnerable library?"
* "Map the attack path from our public API to the payments database."

## Workflows

Use a workflow when you'd otherwise ask Research the same thing every week.

* Check every new critical finding for internet exposure.
* Hunt a repository's attack surfaces after each release.

If you keep repeating a prompt, ask Research to turn it into a workflow. See [Create a workflow](https://docs.enclave.ai/workflows/create.md).

## Risk

Use Risk to work through what Enclave found. Every finding is verified before it shows as confirmed.

## Threat Feed

Use the Threat Feed when a new CVE hits the news. Click **Check if we're vulnerable** to check it against your environment.

## When Enclave isn't the right tool

* **Fixing code.** Enclave finds and explains issues. Your team or your coding agent makes the change.
* **Real-time blocking.** Enclave analyzes and reports. It doesn't sit in the request path.


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