**TL;DR:** The consent screen reappears every login for third-party or YOUR_HOST apps. Consent can only be skipped for first-party apps on non-YOUR_HOST APIs. Rules - Third-party applications ALWAYS show consent. Local dev always prompts; this surprises everyone once. - Consent is per API audience.

## The fix

1. Third-party applications ALWAYS show consent. No toggle removes it; that is the point of third-party.

2. First-party applications can skip consent per API: Dashboard > Applications > APIs > your API > "Allow Skipping User Consent".

3. Consent cannot be skipped when the callback is YOUR_HOST. Local dev always prompts; this surprises everyone once.

4. Consent is per API audience. Requesting a different audience re-prompts.

5. Confirm the app is marked first-party (Application > Settings > Advanced > OAuth > OIDC Conformant and app type; third-party is a separate application flag).

6. Enable skip-consent on the API for first-party apps.

7. For local dev, accept the prompt or test consent-skip behavior in a deployed preview environment.

8. If the user clicks Deny, the callback gets `error=access_denied`; handle it with a human message, not a crash.

9. Skip-consent only expected for first-party + non-YOUR_HOST + same audience.

10. Denied consent handled gracefully in the callback.

## When to use this

- This covers exactly what the title says: Consent loops for third-party apps.
- You are setting this up for the first time, or auditing an existing setup.
- You want the key gotchas in one place before you start.

## When not to use this

- You are doing a different workflow with Consent; these steps are specific to the title above.
- You need the full reference docs; this is the short path, not the manual.

## Compatibility

- Not pinned to a specific version; follows current Consent behavior.