Store feature flags as Markdown files
Represents each feature flag as a Markdown file that lives with the code it controls.
Coding / product dossier
dif.sh
Open-source feature flags stored as Markdown files alongside the code they control.
Product brief
What dif.sh does.
Open source feature flags. Every flag is a markdown file that lives with the code it controls: what it does, why it exists, and what you decided, reviewed in a PR like any other change. Your coding agent installs Dif in one command, no account, and reads the context file so it knows what's live and what was already tried. A/B tests wait in the same files until you have traffic. Send events to your own analytics, or let Dif Cloud read the results and write the decision into the file.
Why we selected it
Treating flags and their decision history as reviewable files gives coding agents durable, repository-native context.
- Best for
- Agent-assisted feature flag workflows
- Category
- Coding
- Daily picks
- 1
- First selected
- 2026-09-05
Product preview saved with our daily selection
Capability scan
What it can help with.
Only capabilities supported by the product information we collected are listed here.
Keep flag context and decisions in the repository
Flag files can document what a flag does, why it exists, and decisions associated with it; they can be reviewed in a pull request like other changes.
Provide context to coding agents
Includes a context file that a coding agent can read to understand what is live and what has already been tried.
Record A/B-test decisions
Keeps A/B tests in the same files until traffic is available, and Dif Cloud can read results and write a decision into the file.
Best-fit use cases
Manage feature flags as repository-native Markdown files reviewed through pull requests.
Give a coding agent context about live flags and prior attempts.
Document the purpose and decision history of a feature flag alongside its code.
Hold an A/B test in the flag file until there is traffic, then record a decision.
FAQ
Before you open it.
How are flags represented in dif.sh?
Each flag is a Markdown file stored with the code it controls.
What information can a flag file contain?
The description says it can record what the flag does, why it exists, and what was decided.
How do coding agents use dif.sh context?
A coding agent can read the context file to learn what is live and what has already been tried.
Can flag changes be reviewed in a pull request?
Yes. The description says the files are reviewed in a PR like any other change.
What does the description say about accounts?
It states that a coding agent installs Dif in one command and that no account is required.
Selection history