Setting the file. One moment.
Skill 55 · Launchdarkly Release Autopilot Onboarding
Subchapter 55.2
references/auto-cleanup.mdMarkdown2 KBView on GitHub
Auto-cleanup runs Vega on a schedule to find flags that are ready for code removal and open pull requests that remove their code. It is set per project, in the Automated flag cleanup section of the project’s Settings > Automations page. On an MCP server with get-automations-cleanup and update-automations-cleanup, the launchdarkly-automations-cleanup-settings skill can read and change it later; onboarding still has the user turn it on in the browser.
For each project, give the user /projects/{projectKey}/settings/automations on their LaunchDarkly instance (for example https://app.launchdarkly.com, or their EU or federal URL). If the link opens the general project settings page instead, the account does not have the Automations page yet: they use /projects/{projectKey}/settings/lifecycle, or /projects/{projectKey}/settings/vega if that page has no “Automated flag cleanup” section. In the “Automated flag cleanup” section they:
AGENTS.md.Cleanup jobs run with the permissions of the member who saved the settings. If that member loses access, someone else must save the settings again.
Record the result as reported by the user. Onboarding does not verify it.