The IDE for decisions · open beta

With AI, everyone is their own mixture of experts.Decide is built for all of them.

It's an IDE for the decisions behind your software. Check what's already settled, talk the call through with an agent, and capture it in seconds, without breaking flow. Each decision becomes shared context the whole team can build on, so anyone can pick up anything.

Free during early access. No opinions about who picks up what.

ecide
DECISION · onboarding-home-page current

New users land on one real welcome, not a guided tour.

A product and design call, written in plain language and kept beside the code it shapes. Anyone on the team can read the why.

governs web/src/pages/Welcome.tsx
Checked against your store
Relevant decisions 3
Possible conflict 1
Uncovered gaps 2

Decide governs its own development. Eighty-three decisions across product, design, and engineering live in this repo, open to everyone who works on it.

Fig. 01While you build

An inner loop for decisions.

Deciding shouldn't mean leaving your editor for a meeting, or a doc that never gets written. Decide runs the tight, fast loop you already know, for the calls you make as you build.

01 — Check

Check what's decided

Ask the store before you write code. Relevant calls, conflicts, and open gaps come back in seconds.

02 — Explore

Explore with an agent

Talk the option through against what's already true. The PM reaching into CSS and the engineer shaping UX both get a way in.

03 — Capture

Capture the call

Lock in the decision and its reasoning as you work, written in the moment instead of reconstructed later.

Fig. 02 — One open home

Everyone's decisions, in one place.

Everyone is a mixture of experts. Decide keeps product, design, and engineering calls side by side, and everyone on the team can read all of them. No private lanes, no reasoning trapped in one person's head or one team's channel.

When the why is in the open, picking up work outside your usual lane stops being a leap of faith. It works the same in the hosted web app or with decide on the command line.

acme/checkout · decision store
Sessions ride in a signed cookie internal/auth current
One real welcome for new users web/src/pages current
Surfaces stay soft, never a sharp dev tool web/src/theme current
Meter billing on usage events internal/billing provisional

Fig. 03 — With your team

The inner loop flows outward.

Every decision you capture becomes shared context. Open a pull request and Decide checks it against the store: what it honors, what it conflicts with, and where it is quietly deciding something new. The drift gets caught before it ships.

Impact analysis links a change back to the decisions it touches, so a tweak to the look and feel and a change to the billing logic each show their blast radius.

PR #128 · Add usage-based billing
4 honored 1 conflict 2 gaps
Honors signed-cookie-sessionstoken handling unchanged ok
Conflicts with flat-rate-pricingthe meter replaces the flat tier review
No decision covers refund prorationnew ground, worth recording gap

Fig. 04 — Why Decide

Your job title says who you report to. It shouldn't decide what you get to build.
The Decide premise

Open beta

A home for everyone who builds.

We're opening Decide to teams who want to bring deciding into the loop and let people work where they're strongest.

For teams who build on GitHub. Your decisions stay in your repo.