是否考虑将插件发布到jetBrains插件市场

[hem951740-max]

Problem (one or two sentences)

是否考虑将插件发布到jetBrains插件市场

Context (who is affected and when)

是否考虑将插件发布到jetBrains插件市场

Desired behavior (conceptual, not technical)

是否考虑将插件发布到jetBrains插件市场

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote]

Thank you for your interest in having Roo Code available for JetBrains IDEs! I'd like to understand your needs better to provide the most helpful response.

Currently, Roo Code is built specifically as a VS Code extension, leveraging VS Code's extension APIs and architecture. Creating a JetBrains plugin would require:

1. Building a completely new plugin from scratch using JetBrains' plugin SDK
2. Reimplementing the UI using JetBrains' UI framework (instead of VS Code's webview)
3. Adapting all the VS Code-specific integrations to work with IntelliJ's APIs
4. Maintaining two separate codebases going forward

Before proposing any technical approach, could you help clarify:

• Are you looking for the full Roo Code experience in JetBrains IDEs, or would a subset of features be sufficient?
• Which JetBrains IDE(s) are you primarily interested in (IntelliJ IDEA, WebStorm, PyCharm, etc.)?
• Are there specific features of Roo Code that are most important to you?
• Would you be open to using VS Code for AI-assisted coding, or is JetBrains IDE support essential for your workflow?

This information will help determine whether this is feasible and what approach would best serve your needs.

Please tag @roomote in your response with the answers, and I'll be happy to explore potential solutions!

[hem951740-max]

@roomote 我希望在roocode也能提供jetbrains版本，我希望能够获取到完整功能，目前我常用的jetbrains工具是IntelliJ IDEA、WebStorm，其中我更关注的roocode中可自定义接入模型的功能；相较vscode我更喜欢jetbrans的操作页面，不仅仅是页面风格，主要是idea对java支持更友好，对git的操作可视化和便捷化。

[roomote]

Thank you for providing those details! I understand you would like:

• Full Roo Code functionality in JetBrains IDEs
• Primary focus on IntelliJ IDEA and WebStorm
• Custom model integration feature is most important
• Better Java and Git support that JetBrains provides

I've seen your comment and will explore what can be done. While creating a full JetBrains plugin involves significant architectural considerations, I'll investigate potential approaches and document the findings. I'll open a PR to share progress and gather feedback.

[roomote]

I've completed an initial analysis of JetBrains plugin support and created a comprehensive technical design document.

What I've Created

📄 Technical Design Document: docs/jetbrains-plugin-support.md

The document includes:

• Current Architecture Analysis: How Roo Code is built today
• Three Implementation Approaches: With pros/cons for each
• Recommended Approach: Native JetBrains plugin with hybrid UI
• Technical Challenges: And proposed solutions
• Development Roadmap: 8-11 months for full feature parity
• Phased Implementation:
  • Phase 1 (MVP): 3-4 months - includes custom model integration
  • Phase 2 (Feature Parity): 3-4 months
  • Phase 3 (Polish): 2-3 months
• Resource Requirements: Team composition and infrastructure needs
• Risk Mitigation: Strategies for managing challenges

Key Findings

✅ Feasible: Building JetBrains support is technically possible
⚠️ Significant Investment: Requires 8-11 months with dedicated team
🎯 Custom Models First: Your top priority feature can be delivered in Phase 1 (MVP)
🔧 Native Plugin Recommended: Better experience than workarounds

Next Steps

The draft PR is ready for community review: #10042

I'm looking for feedback on:

• Does this approach make sense?
• Are the priorities right (custom models in Phase 1)?
• Is the timeline realistic?
• Are there alternative strategies to consider?

Your input will help shape the potential implementation of this feature. Feedback welcome!