> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pullfrog.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Issue enrichment
> Duplicate checks, related context, and implementation plans on every new issue, plus automatic labels.
Pullfrog reads every new issue, checks it against the issues you already have, and replies with context or a plan. Enrichment is on by default. Configure it in the repository console under **Automations → Enrich issues**.
## Enrich new issues
Enrichment checks for duplicates, surfaces related issues, and investigates concrete bugs and feature requests. For an actionable request from a collaborator with write access, it posts a concise implementation plan. Other issues get an analysis or a request for the missing information. In Enrich mode, Pullfrog does not change code.
The **Mode** setting on the card chooses what a new issue triggers:
| Mode | Behavior |
| - | - |
| **Enrich** | Run the default enrichment prompt, or your own prompt in its place |
| **Plan** | Analyze the issue and post an implementation plan |
| **Build** | Implement the issue and open a PR |
Each run uses the repository's configured model. On public repositories, **Include issues from non-collaborators** controls whether issues from outside contributors are enriched; it is on by default and gives those contributors no other trigger.
To let authors decide when to involve Pullfrog, turn off **Enrich issues** and turn on **Post an initial comment with Quick Links instead**. Each new issue then gets **Build this** and **Make a plan** buttons.
### Customize the prompt
In Enrich mode, the **Enrichment prompt** field replaces the default prompt. Click **View default prompt**, then **Copy prompt**, paste it into the field, and edit it. Clear the field to go back to the default. In Plan and Build modes, the field is labeled **Custom instructions** and adds to the mode's built-in prompt.
### Implement from an issue
An enrichment reply carries an **Implement a fix** button, and a plan comment carries **Implement plan**. Either one starts a run that reads the issue discussion, implements the work, and opens a PR. Both buttons require you to sign in to Pullfrog with write access to the repository.
## Issue indexing
Issue indexing is a paid-plan feature. See [Billing](/billing).
Without a paid plan, enrichment searches the repository's issues by keyword. A paid plan adds retrieval from Pullfrog's background index of your issues. Pullfrog inspects the likely matches before it calls an issue a duplicate, and links a confirmed duplicate instead of writing another plan. Neither search guarantees that every duplicate is found.
Pullfrog never closes or labels an issue on similarity alone. That decision stays with a maintainer.
Pullfrog builds the index for every set-up repository on every plan, including a backfill of existing issues, so the index is complete on the day you upgrade.
Indexing reads issue titles, bodies, and comments, and may read a bounded amount of repository source when an issue references specific files. It never writes to your repository.
## Auto-label issues
The **Label issues** card under **Automations** labels each new issue from its title and body, using only labels that already exist in the repository. It is off by default. Its **Custom instructions** field shapes the choice, for example "Prefer specific labels over generic ones. Use at most 3 labels."
## Plan instructions
The **Custom instructions** field on the **Plan** card under **Automations** guides how Pullfrog writes implementation plans. It applies when enrichment runs in Plan mode, when someone clicks **Make a plan**, and when an `@pullfrog` mention asks for a plan. The plans that Enrich mode posts follow the enrichment prompt instead.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.