> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Application AI Settings
> Per-application control of the Ankra AI lanes that run on its repository - which lanes run, on which model, and within which branch scope and daily budget.
Every [application](/concepts/applications) carries an **Ankra AI** panel that decides which AI lanes run on that application's repository. Open the application, then **⋯** → **Settings** → **Ankra AI**.
Each lane follows your organisation's source-control defaults until this application overrides it. The panel is a view onto the same per-repository settings the review lanes read when an event arrives, so what you set here and what your organisation's [source-control connection](/platform/ai-connections) sets can never disagree.
The panel needs an application linked to a GitHub repository with the [Ankra GitHub App](/integrations/github) installed on that repository's owner. Without one it renders the reason instead of the lanes: the application has no repository yet, the App is not installed for the owner (install it under **Organisation settings** → **Integrations**), or the application is on a provider the lanes cannot mint a repository token for - AI lanes are available for GitHub App repositories today.
## The lanes
| Lane | What it does | Runs when | Default |
| ----------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | ------- |
| **Pull request review** | Reviews the diff and posts a verdict with its findings as one comment that updates in place | A pull request is opened or updated | On |
| **Code review** | A deeper pass over the branch itself, with no pull request involved | A push to a branch in scope | Off |
| **Actions review** | Reads the failed job logs of a red pipeline and explains what broke | A workflow run fails | Off |
| **Org skills review** | Checks the change against your organisation's [skills](/platform/ai-skills) and conventions | Alongside the pull request review, in the same comment | Off |
| **Demo URL** | Deploys a [preview environment](/guides/pr-preview-environments) per pull request and comments its public URL | A pull request is opened or updated | On |
The two lanes that answer an event you already caused are on for a repository nobody has configured. The lanes that would otherwise start spending on every push and every red pipeline are opt-in.
**Code review** and **Actions review** are labelled **Not available yet** and their switches are disabled. Their cards describe what the lanes will do; nothing runs. On **Pull request review**, the **When it finds something** choice is stored but not acted on yet - that lane comments today whichever option you pick, and the card says so.
## Inherit or override
Every card is labelled either **Inherited** - it follows your organisation's default for this connection - or **Overridden**, meaning this repository pins its own value. Edits stage locally until you press **Save AI settings**, and only the lanes you touched are sent. A lane you never touch keeps inheriting, which is what lets an organisation admin go on steering every application that has not opted out.
Overriding a lane pins the whole lane: the values on the card when you save become this repository's settings for it, and later changes to the organisation default stop reaching that lane. Two controls undo it:
* **Reset to organisation default** on a card returns that one lane to the organisation, and says which way the organisation has it (on or off).
* **Follow organisation for everything**, at the top of the panel, drops this repository's override entirely so every lane inherits again.
## What you can set per lane
| Control | Lanes | What it does |
| ---------------------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Model** | Every lane except Demo URL | Which model from your organisation's catalogue the lane runs on. **Ankra default** lets Ankra choose. The catalogue's **Auto** routing is deliberately not offered here: a lane that changed model between runs would make its findings impossible to compare. |
| **When it finds something** | Pull request review, Code review, Actions review | **Comment only** reports and stops. **Propose a fix** also opens a pull request with a suggested change - automatic source-control events run read-only, so the fix is a separate run that proposes a change for you to review, never an in-place edit. |
| **Target branches** / **Branches** | Pull request review, Code review | Comma-separated branch patterns with `*` and `?` wildcards. Leave it empty to put every branch in scope. |
| **Ignore paths** | Pull request review, Code review, Org skills review | Comma-separated globs, matched against each changed file's path after the change. Matching files leave the diff *before* the character budget is measured, so a lockfile or a generated bundle can no longer crowd the real change out of a review. `**` crosses directory separators, `*` and `?` do not, and a pattern with no wildcard also matches everything beneath it - `vendor` covers `vendor/lib/thing.go`. |
| **Skip draft pull requests** | Pull request review | On by default. Draft pull requests are reviewed once they are marked ready. |
| **Max runs per day** | Every lane except Demo URL | A cap on the lane's automatic runs for this repository, counted since midnight UTC. Leave it blank for no cap. |
| **Max input characters** | Every lane except Demo URL | The most characters of diff one run may read. Leave it blank to use the built-in 120,000-character budget. |
**Demo URL** has no settings of its own here - it is on or off. What a preview deploys comes from the application's demo defaults; see [environment variables and a throwaway database](/concepts/applications#environment-variables-and-a-throwaway-database). Turning the lane off stops the automatic pull-request previews for this repository without touching manually launched [preview demos](/concepts/applications#preview-demos).
Mentioning Ankra in a pull request comment always gets an answer: a mention reply is a direct request from a human, so it is never filtered by branch scope, draft state, or the daily run budget.
## Settings are per repository, not per application
These settings are keyed by the repository, not by the application. Two applications connected to the same repository share one set of lane settings - turning a lane off on one turns it off for the other, and each application's panel renders the other's edits as its own. The preview lane also fires once per matching application, so such a repository collects one preview comment per application on every pull request. Keep one application per repository until per-application keying ships.
## Related
* [Applications](/concepts/applications) - connecting a repository, components, demos, and registries
* [PR preview environments](/guides/pr-preview-environments) - what the Demo URL lane deploys, and its status comment
* [AI Skills](/platform/ai-skills) - the skills the Org skills review lane checks a change against
* [AI Connections](/platform/ai-connections) - the organisation's source-control connection these lanes inherit from
* [`ankra application pull-request-reviews`](/reference/cli/application) - read the reviews a lane has posted, from the CLI