How unit-mesh/autodev-vscode works
Project Type & Purpose
• This is a full-stack VSCode extension (“AutoDev for VSCode”) comprising:
• A Node/TypeScript extension backend running in the VSCode Extension Host
• A React-based webview UI (“gui-sidebar”) served by the extension
• Multiple core subsystems (code-search, code-context, prompt management, AI agent flows)
• Integration with external LLM and embedding services (OpenAI, Ollama, local ONNX)
• Persistence layers for indexing/search (SQLite, LanceDB, optionally ElasticSearch)
• Purpose: provide AI-powered coding assistance (chat mode, code completion, auto-doc, refactoring, RAG search, CI generation, test generation, etc.)
Key Architectural Layers & Modules
• VSCode Host Layer
• VSCode Editor UI & API
• Extension Host (Node.js)
• Webview UI Layer (“gui-sidebar”)
• React Components, Redux store, Webview messaging bridge
• Extension Core Layer (src/)
• Activation & command registration (extension.ts, commands/)
• Action subsystem (src/action): ActionCreators, ActionExecutors, code-action providers
• Agent subsystem (src/agent): built-in flows, catalyser, custom agent connectors
• Code-Context subsystem (src/code-context): Tree-Sitter parsing, relevant-code providers, structurer/test-gen providers
• Code-Search subsystem (src/code-search): chunking, indexing, embedding, retrieval, reranking, semantic/TfIdf search, scope graph
• Prompt Management (src/prompt-manage): template loading, overrides, custom/team prompts, execution tasks
• Toolchain Context (src/toolchain-context): detect languages, frameworks, build tools, dependency inspectors
• Configuration & Services (src/base/common): configurationService, instantiation, logging, lifecycle, webview helper
• Domain & Utility modules: query expansion, team terms, git parsing, markdown processing
• Persistence & External Services
• Local DB (SQLite via SqliteDb), LanceDB, optional ElasticSearch
• LLM & Embedding APIs (OpenAI, Ollama, Anthropic, local ONNX via onnxruntime-node)
Relationships & Data Flows
• User triggers UI command (keyboard shortcut, sidebar button)
• VSCode forwards to Extension Host → CommandService → ActionCreator
• ActionCreator builds TemplateContext via PromptManager and potentially ToolchainContext
• Extension invokes Code-Search and/or Code-Context services to gather code snippets/context
• PromptManager constructs prompt → passed to LLM provider (external API or local inferencing)
• LLM response returned → ActionExecutor applies edits/refactoring/generation via VSCode API
• For webview flows: React UI sends message → Extension Host handles via webviewViewProvider → processes similarly → sends back result → React renders
Architectural Patterns
• Modular “Service” & “Provider” pattern: each domain (code-search, code-context, toolchain) has manager/service + provider implementations
• Dependency Injection via instantiationService (in src/base/common/instantiation)
• Template Method & Strategy for search strategies (Hyde, TfIdf, semantic) and chunkers
• Adapter layers for LLM providers, embedding providers, and build tool providers
Detail & Clarity
• Optionally, annotate key interfaces (e.g., ICodeContextProvider, IEmbeddingsProvider)