ReplayAutonomous app testing for teams who ship at AI-speed
Promoted
Launching today
dif.sh
Markdown feature flags your coding agent installs for you
249 followers
Markdown feature flags your coding agent installs for you
249 followers
Open source feature flags as markdown files in your repo: the flag, the reason, the decision in one file, reviewed in a PR. One command, no account, so your coding agent can finish the install. A/B tests wait in the same files until you have traffic.
You asked for the critical version. Flags in git means flipping one takes a commit, a review and a deploy, and the reason teams pay for a flag service is the kill switch at 2am without any of that. For agent facing flags it's a fine trade, for a gradual rollout or an incident it isn't. Markdown also won't fix dead flags, since nothing gets reviewed when nothing changes and the flag nobody has touched in four months is still branching in prod.
Bababot
I have used separate tools for A/B tests before so keeping the experiment inside the repo feels interesting.
I like the idea of keeping feature flags right inside the repo. Having the reason and decision in the same markdown file makes changes much easier to understand later.
This feels nicely aligned with how coding agents actually work. No separate dashboard or account to set things up is a pretty refreshing approach.
The PR review flow is what caught my attention here. Treating feature flag changes like normal code changes should make the whole process feel much more familiar.