LaunchDarkly Automations Auto-cleanup Settings
You're using a skill that reads and changes a project's auto-cleanup settings, from the "Automated flag cleanup" section of the project's Settings > Automations page. Auto-cleanup opens pull requests in the user's GitHub repositories on a schedule. Treat every write as production automation with a blast radius.
Prerequisites
This skill requires the remotely hosted LaunchDarkly MCP server.
Required MCP tools:
get-automationswithsection: "cleanup"andprojectKey: the project's cleanupsettings, theupcomingrun (enabled,flagKeys,nextRunAtin Unix milliseconds), andautomationsPage, the link to the project's Automations page.update-automationswithprojectKeyand acleanupobject: change one or more settings. Omitted fields keep their stored values. Sendcleanupon its own, withoutaccountWide,repo, orarchival.
Optional: get-projects to pick the project, get-automations to suggest the repositories already mapped to the project.
If get-automations has no section argument, or rejects section, the server has not picked up cleanup and archival yet. Ask the user to reconnect the LaunchDarkly MCP server once. If it still has none, guide the browser steps in references/browser-steps.md instead. Do not invent REST calls.
What the settings mean
| Field | Meaning |
|---|---|
schedule |
disabled (off), daily, weekly, or monthly |
repositories |
GitHub repositories (owner/name) cleanup opens pull requests in |
maxJobsPerRun |
The most cleanup pull requests one run opens |
flagStates |
Which flags runs pick up: readyToArchive (the default), readyForCodeRemoval, live |
customContext |
Extra instructions for the cleanup agent, such as where flags are defined. The agent also follows the repository's AGENTS.md |
retryAttempted |
true retries flags that already had a cleanup pull request |
configuredByMemberId |
The member whose permissions cleanup jobs use. Read-only: it becomes whoever saves the settings |
Core Principles
- Confirm before every write. State the current and proposed values, wait for a yes that names the change in this turn, then write. A yes from an earlier turn, or a vague "go ahead", is not enough.
- Saving changes who cleanup runs as. Every cleanup save with
update-automationsmakes the calling member the one whose permissions cleanup jobs use. Say so in the proposal whenconfiguredByMemberIdis someone else. - Lists replace.
repositoriesandflagStatesreplace the whole stored list. To add one repository, read the current list and send it with the new one. To remove one, send the list without it. - Least privilege. Only add repositories the user named. Never add every repository on the GitHub App install. Keep
flagStatesatreadyToArchiveunless the user asks for more:livepicks up flags that are still serving. - Turning it on starts pull requests. Any schedule other than
disabledmakes LaunchDarkly open pull requests in the listed repositories, starting with the next run. A schedule with no repositories opens none.
Workflows
Read the settings
get-automations with section: "cleanup" and projectKey. Report the schedule, repositories, job limit, flag states, and who cleanup runs as. If upcoming.enabled is true, say when the next run is (nextRunAt) and which flags it will pick up (upcoming.flagKeys).
Turn it on or change it
Read the settings:
get-automationswithsection: "cleanup".Ask for anything the change needs and the user did not give: the schedule, and at least one repository when none is stored. Suggest the repositories mapped to the project in
get-automations. Only the user's answer goes in.Propose the change, for example:
Automated flag cleanup is off for project
default. Turn it on weekly inacme/web, with at most 10 pull requests per run? LaunchDarkly will start opening pull requests that remove the code for flags that are ready to archive. Cleanup jobs will run with your permissions.After the user confirms, call
update-automationswithprojectKey,confirm: true, and acleanupobject holding only the confirmed fields.The response lists
changedand thesettingsas read back. If it reports a mismatch on read-back, show the user the current values fromget-automationswithsection: "cleanup"and do not retry blindly.
Turn it off
Propose it ("Turn off automated flag cleanup for project default? No new cleanup pull requests will open; open ones stay open."), then update-automations with projectKey, cleanup: { "schedule": "disabled" }, and confirm: true.
Why didn't cleanup open a pull request?
Read-only. Call get-automations with section: "cleanup" and check in this order. Stop at the first answer.
settings.scheduleisdisabled: cleanup is off.settings.repositoriesis empty: there is nowhere to open pull requests.upcoming.enabledis false while the schedule is on: no member is set to run cleanup, or that member is no longer on the account. Someone with access must save the settings again, which makes them the member cleanup runs as.- The flag is not in
upcoming.flagKeys: its state is not inflagStates, the run limit (maxJobsPerRun) is full, or it already had a cleanup pull request andretryAttemptedis false. - The flag is in
upcoming.flagKeys: it is waiting for the next run atnextRunAt.
If none of these explain it, point the user at the cleanup history in the "Automated flag cleanup" section of automationsPage. Do not change settings to try something.
Errors
- 403: the member lacks permission to update the project's lifecycle settings, or to view the project. Say which, and stop.
- No
sectionargument: see Prerequisites.
Out of scope
- Running a cleanup now, and reviewing cleanup history: both are in the "Automated flag cleanup" section of the Automations page.
- Removing one flag's code by hand: use
launchdarkly-flag-cleanup. - Auto-archival: use
launchdarkly-automations-archival-settings. - Auto-flagging and auto-releasing: use
launchdarkly-release-autopilot-settings.
References
- references/browser-steps.md: the same settings in the browser, for servers without these tools
- Automated flag cleanup docs