[Question/Discussion] Are there plans or an architectural roadmap for an Agentic IDE view?

[mkrishna793]

[Question/Discussion] Are there plans or an architectural roadmap for an Agentic IDE view?

Problem Statement

We are designing an AI-native, agentic IDE that requires both a traditional Editor View and a highly interactive Agentic View (AI workspace/chat/agent control panel). However, hard-forking VS Code or VS Codium introduces a massive maintenance burden, requiring constant upstream merges and updates that can stall feature development.

I am interested in how this project plans to handle agentic workflows moving forward, specifically regarding the separation of the Editor View and the Agentic View.

Before diving deep into any development, I wanted to ask the maintainers/owners: Do you already have a specific plan, architectural design, or roadmap for building this out?

Key Challenges to Consider:

1. The Forking vs. Maintenance Dilemma: If we build an open-source IDE by hard-forking VS Code or VS Codium, tracking and merging their upstream changes constantly (daily or weekly) will become a massive maintenance nightmare for this project.
2. UI Separation: How do you envision separating the standard code editor view from the interactive AI/agentic panels? Are you leaning toward a custom distribution, or keeping it entirely as a deeply integrated extension/webview?

I would love to know if the team has already brainstormed any ideas, or if there is an existing design document we can review. If nothing is set in stone yet, I'm happy to help start a discussion on how we can push this forward sustainably!

Discussion Points & Feedback Needed

1. Are there existing open-source frameworks (like VSCodium components or Eclipse Theia) that allow cleaner UI injections without touching the core repository?
2. What are the performance bottlenecks to watch out for when passing large codebases/context windows between the editor window and the agentic webview?
3. What automation tools do you recommend for tracking and auto-merging upstream IDE updates?

Thanks,
Krishna

[SNTL84]

Important

Practitioner's perspective — I build agentic AI systems professionally. This exact architectural tension is one I've solved in production.

---

🤖 The Agentic IDE Architecture Problem — A Field-Tested Solution

The core insight most people miss: This isn't a forking problem — it's a runtime boundary problem.

---

📐 The Mental Model That Actually Works

┌──────────────────────────────────────────────────┐
│                   VELOCITY IDE                   │
├─────────────────────────┬────────────────────────┤
│   EDITOR VIEW (upstream)│     AGENTIC VIEW        │
│  VS Code / Theia core   │  (your IP, your logic)  │
│  → minimal patches only │  → WebView / sidecar    │
├─────────────────────────┴────────────────────────┤
│          ORCHESTRATION LAYER  (the real product)  │
│  message bus │ tool calls │ agent state │ context │
└──────────────────────────────────────────────────┘

Rule: Upstream merges only ever touch the left panel. Your agentic logic — your actual product moat — lives independently in the Orchestration Layer and is portable across any editor surface.

---

⚡ Answering Your 3 Questions Directly

#	Question	Practitioner Answer
1	Fork vs Extension?	Use Eclipse Theia as your base — it exposes clean DI containers for UI injection. Never patch core, only contribute via its plugin API. Zero hard-fork needed.
2	Context window bottleneck?	The bottleneck is uncontrolled context growth, not transfer speed. Use tree-sitter AST parsing to pass only semantically ranked code slices — 90% smaller payloads, same output quality.
3	Auto-merge upstream?	Shadow branch strategy — a CI job watches upstream release tags and opens a draft PR to your fork automatically. Merge burden becomes visible and reviewable, never a silent explosion.

---

🔥 The Principle That Ties It Together

"Don't fork the editor. Fork the workflow. The editor is a commodity. The agentic orchestration layer is the moat."

This is exactly how I architect automation systems — decouple the surface from the intelligence layer so your agentic logic can evolve without being held hostage by upstream maintenance cycles.

---

Note

I build Agentic AI Workflow systems — lead automation, full-stack pipelines, and AI-native business tooling.
If Velocity moves toward an open plugin or workflow integration layer, I'd love to contribute or collaborate.

💻 GitHub: github.com/SNTL84
🌐 Web: desidevloper.com
💼 LinkedIn: linkedin.com/in/sntl2784
📸 Instagram: @desibiztrade
🔴 YouTube: @SNTL84
💬 WhatsApp: wa.me/919727413309

---

Automate what's costing you time. — SNTL84

[mkrishna793]

Thanks so much..