Hey, thanks for the detailed feature request, and it’s really impressive that you’ve built a full case management system as a non-developer.
A few things that might help with your current workflow:
On model quality: The models in Cursor are the same base models as on the web (Claude, GPT, etc.), but the system prompt is coding-focused, which can affect reasoning for non-coding domains. Two things to try:
- Use Max Mode (toggle in the model picker). It sends requests with extended thinking, which helps with complex reasoning tasks.
- Add a detailed
.cursorrulesfile that clearly says you’re working in a clinical or medical domain, not coding. For example: “You are assisting a clinical practitioner. Prioritize medical reasoning accuracy. Do not assume code context.” This can significantly change the model’s behavior. - You can also bring your own Anthropic API key: Cursor Settings > Models. This gives you access to all Claude models directly. More details: Bring your own API key | Cursor Docs
On multi-model debate: There’s a community-built MCP server that does exactly this: AgentChatBus. It lets multiple AI agents cross-check each other’s reasoning inside Cursor via MCP. Worth checking out for your use case. More details: Discussion: Bringing Multi-Agent Debates to Cursor via MCP (AgentChatBus)
On audio or voice: Cursor already has voice input (microphone icon in chat). It’s not the full real-time session structuring you’re describing, but it does handle voice-to-text input natively.
On rules enforcement: .cursorrules is currently the main mechanism. You can also use project-level rules: Cursor Settings (not VS Code settings) > Rules, for more structured governance. Docs: Rules | Cursor Docs
The broader feature request for non-coding expert workflows is noted. Your use case is a good example of where Cursor can expand beyond developers.
Let me know if these workarounds improve the reasoning quality.