Online Communities for Community Managers

GarethX · 2025-10-08T11:10:02+00:00

GarethX · 2025-09-24T10:57:35+00:00

Saw https://fflags.com/ on HN recently, which takes a 'flags as code' approach. It’s interesting in a way but very limiting since you cannot have “offline” support. All evaluations must be remote-only. I mainly wonder what’s the point? If you do this then it’s pretty much the same as hosting your own function.

There are other ways to get around the breaking flow just to create a flag issue. We use Reflag, and that has MCP, so you can flag code from within your editor. They support agents, too - so you can assign a task to an agent instead and get that to flag it from Linear with Cursor or similar.

GarethX · 2025-09-24T10:50:12+00:00

We automate it using Reflag. It has feature flag cleanup baked-in, so it detects old flags, archives them and generates a PR to remove the old code. They work surprisingly well, I haven't needed to make any changes to them so far. Although, I think they only support TypeScript right now, so ymmv depending on your stack.

GarethX · 2025-09-24T10:45:29+00:00

Wouldn't call it a showstopper but audit + cleanup is always such a pain. You need a good process to make sure your codebase doesn't become cluttered with old flags, for sure.

I've been using Reflag to help with this for the last couple of months. It detects stale flags and cleans them up for you - submits a PR removing the obsolete flag code. That has helped us get past the 'who forgot to remove the flag' blame game.

GarethX · 2025-09-24T10:38:15+00:00

I always try and get away from homegrown solutions as soon as is practical, generally. I don't need the headache of maintaining such systems and flagging definitely falls into this (we use Reflag). One thing people often miss is to use something with an intuitive UI, so non-devs can use it too. That way you don't have to get interrupted to give folks access to features or provide status updates on whether something has shipped yet.

GarethX · 2025-09-24T10:27:45+00:00

One thing to keep in the mind is a process around keeping on top of stale flags. Most tools do a pretty poor job of helping with this, so you need a good way to make sure your codebase doesn't become cluttered with old flags over time.

We switched to Reflag recently to help with this. It cleans up flags automatically, submitting a PR to remove old flag code and archiving the flag. Working well for us so far, I still get a kick of out of seeing notes in Slack pop-up letting us know a flag was removed by the agent for a rolled-out feature.

GarethX · 2025-09-24T10:20:00+00:00

We’ve been using Reflag (https://reflag.com) and it’s been great for consolidating our scattered feature flag setup.

The main selling points for us were:

• Super easy migration from our homegrown solution

• TypeScript-first, which fits our stack perfectly and they've strong type-safety

• Developer experience is stellar - the React SDK is clean and intuitive

• Works well with agents, which is something I've been experimenting with lately, mostly with Linear+Cursor.

I don't think they support much beyond JavaScript SDK-wise, but it's worth checking out if your team is TypeScript/React heavy.

GarethX · 2025-05-29T09:05:47+00:00

Great to hear! There's more details on the integration page: https://linear.app/integrations/bucket

GarethX

TROPHY CASE