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.
The IDE for decisions · open beta
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.
A product and design call, written in plain language and kept beside the code it shapes. Anyone on the team can read the why.
Decide governs its own development. Eighty-three decisions across product, design, and engineering live in this repo, open to everyone who works on it.
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.
Ask the store before you write code. Relevant calls, conflicts, and open gaps come back in seconds.
Talk the option through against what's already true. The PM reaching into CSS and the engineer shaping UX both get a way in.
Lock in the decision and its reasoning as you work, written in the moment instead of reconstructed later.
Fig. 02 — One open home
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.
Fig. 03 — With your team
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.
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
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.