One command
Add LaunchDarkly to any Ashlr Stack project with a single command. Stack runs the auth flow, verifies the credential, and writes every secret slot into Phantom.
stack add launchdarkly
Or describe what you're building and let Claude pick it up via stack recommend:
stack recommend "I need a featureflags provider"Auth flow
Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom.
How-to: Find your SDK key in LaunchDarkly → Environments and create an API token at LaunchDarkly → Account settings → Authorization.
Secret slots
stack add launchdarkly writes these 2 secret
slots into your Phantom vault:
LAUNCHDARKLY_SDK_KEYLAUNCHDARKLY_API_TOKEN
The values never leave Phantom in plaintext. Your .env file references slot
names, and stack exec -- <cmd> swaps them in at process-spawn time via
Phantom's local proxy.
FAQ
Do I need a LaunchDarkly account to use it with Stack?
Yes — Stack provisions LaunchDarkly on your behalf, but it authenticates as you. Paste a long-lived API key once. Stack verifies it against the provider's API before writing to Phantom. If you don't have a credential yet, create one at https://app.launchdarkly.com and paste it once.
Where does Stack store my LaunchDarkly credentials?
In Phantom Secrets, an E2E-encrypted local vault. Stack writes the secret slot names (LAUNCHDARKLY_SDK_KEY, LAUNCHDARKLY_API_TOKEN) into .stack.toml — the actual values live only in Phantom and never touch disk in plaintext.
Can I rotate or revoke this integration later?
Yes. Run `stack remove launchdarkly` to pull the LaunchDarkly service back out (Phantom secrets deleted, MCP entry removed, .stack.toml cleaned up). Rotate the underlying LaunchDarkly credentials in their dashboard — https://app.launchdarkly.com — and Stack's next `doctor --fix` will pick up the new values.