IDE Workflow Example
See how an IDE agent can retrieve an existing decision and steer implementation before a conflicting change is introduced.
A common MCP workflow starts with an implementation request, not a documentation request.
Example
Developer prompt:
Create a REST API using Express
DecisionOps MCP response:
- Existing decision: use Hono instead of Express
- Suggested action: build the API with Hono, or create a new decision if the team intends to change the standard
Why This Matters
This is the difference between documentation that is merely searchable and guidance that can actively influence implementation before drift lands in the codebase.
Next steps:
Recording Decisions During Coding
Draft, validate, and publish decisions from the IDE workflow without leaving the coding context.
IDE Troubleshooting
Use this page when the platform-specific setup looks right but DecisionOps still is not behaving correctly in your IDE. Most problems fall into one of five buckets: the IDE cannot discover the MCP server, the auth flow repeats, the grant exists but calls still fail, the workspace context is wrong, or the user has less permission than expected.