---
name: bijection-flags
description: "Evaluate and integrate the Flags component with Bijection."
---

# Flags

Application feature flags

- Package: @bijectionhq/flags
- Category: Database & Backend
- Status: Preview
- License: MIT
- Bijection source (repository access required): https://github.com/bijectionhq/flags/tree/83c58d7a4ff3f5ce5f6af806141b19cc056eaf8d
- Upstream: https://github.com/vllnt/convex-flags/tree/6315125c6f63244bfdcf06cb5c3beae8a0b959ef
- Documentation: https://docs.bijection.com/components/using
- Directory: https://bijection.com/components/flags

## Get the source

Bijection repository access is required. Request access at https://bijection.com/contact.

```sh
git clone https://github.com/bijectionhq/flags.git
cd flags
git checkout 83c58d7a4ff3f5ce5f6af806141b19cc056eaf8d
```

## Before using this component

Read the package README at the recorded revision for setup, dependencies, and API examples. Upstream documentation describes the original package and may differ from the Bijection adaptation. This is a source candidate for evaluation. Catalog inclusion does not establish npm availability or runtime qualification. Check compatibility with your SDK and deployment before adoption. External providers run their own compute.

## Integration workflow

1. Read the source README and package manifest at the recorded revision.
2. Confirm the required SDK, dependency availability, and runtime compatibility.
3. Follow the component's documented setup and configuration. Never invent an npm install command from a catalog package name.
4. Keep credentials in the project's existing secret store.
5. Follow the project's execution rules for verification and report what was actually checked.

## Original upstream skill

The following guidance describes @vllnt/convex-flags. Its installation commands and APIs refer to the upstream package. Evaluate compatibility with the Bijection source separately.


> Agents: read this skill fully before writing code that uses Feature Flags. Follow the installation and configuration steps exactly.

# Feature Flags

## Instructions

@vllnt/convex-flags separates a feature’s release decision from the code that implements it. Store boolean flags or variants and evaluate them against context supplied by your backend.

Define flags, targeting rules, weighted rollouts, and per-subject overrides. Evaluate flags in Convex queries and expose reactive results to clients. update changes selected fields; archive and restore support reversible retirement. Optional React hooks wrap host query references.

Your application ships the feature code, authenticates context, and gates management actions. A flag is not an access-control or payment-entitlement system. Percentage release control does not calculate experiment outcomes; measure those separately.

Maintained by [bntvllnt](https://bntvllnt.com) at [VLLNT](https://vllnt.com). Find the author on [GitHub](https://github.com/bntvllnt) and [X](https://x.com/bntvllnt).

### Installation

```bash
npm install @vllnt/convex-flags
```

Current npm version: `@vllnt/convex-flags@0.1.0`

## Use cases

- Mobile apps: expose already-shipped functionality to a controlled audience.
- SaaS releases: start with a small percentage of workspaces and expand gradually.
- Games: enable events or select host-defined configurations.
- AI tools: switch an existing model or prompt configuration, or disable a feature during an incident.

## How it works

Define flags, targeting rules, weighted rollouts, and per-subject overrides. Evaluate flags in Convex queries and expose reactive results to clients. update changes selected fields; archive and restore support reversible retirement. Optional React hooks wrap host query references.

Your application ships the feature code, authenticates context, and gates management actions. A flag is not an access-control or payment-entitlement system. Percentage release control does not calculate experiment outcomes; measure those separately.

## When NOT to use

- When a simpler built-in solution exists for your specific use case
- If you are not using Convex as your backend
- When the functionality provided by Feature Flags is not needed

## Resources

- [npm package](https://www.npmjs.com/package/%40vllnt%2Fconvex-flags)
- [GitHub repository](https://github.com/vllnt/convex-flags)
- [Live demo](https://vllnt.com/)
- [Convex Components Directory](https://www.convex.dev/components/vllnt/convex-flags)
- [Convex documentation](https://docs.convex.dev)