How DecisionOps Fits Into Development
Compare the dashboard path and IDE path, and see where GitHub checks and governance fit across both.
DecisionOps is designed to meet teams where they already work.
Some workflows begin in the dashboard. Others begin in the IDE. Both end in the same decision record, the same governance model, and the same organizational memory.
The web app and IDE workflows are complementary. The web app is where teams set up the workspace and govern the decision system. The IDE path is where developers use that system while coding.
What The Web App Does Best
The web app is the best place to finish onboarding, create or switch workspaces, organize projects and repositories, invite members, create API keys, connect GitHub, review monitoring data, configure rules, and inspect decision history with full context.
What The IDE Path Does Best
The IDE path is the fastest way to bring decisions into active delivery work. A connected MCP client can search prior decisions, create a structured draft from the current problem, validate the draft against organization constraints, and publish it. That is especially useful when the user is already in the repository and wants to capture a choice before it gets lost.
Typical Handoffs
A common flow is to onboard in the web app, connect an IDE from /integrations/agents, complete the first OAuth consent handoff, and then do future search and drafting from the editor. Another common flow is to publish from the IDE and then open the decision detail page in the web app for richer review, revision history, or suggestions.
Not every task belongs in both places. GitHub installation, member management, API key lifecycle, and rules configuration are still web-first tasks. Search, draft, validate, and publish are where the IDE path shines.