Skip to content

feat: add vscode-desktop-core module #278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 17 commits into from
Aug 11, 2025

Conversation

phorcys420
Copy link
Member

@phorcys420 phorcys420 commented Jul 31, 2025

This PR introduces a new vscode-desktop-core module that acts similarly as AgentAPI does for other modules as an effort to centralize the logic.

This will help with avoiding maintaining multiple modules that do the same thing. I will follow shortly with a PR for a vscode-web-core module to centralize the logic for vscode-web and code-server as we've had issues where both would behave differently due to forgetting to update one or the other.

This will also help make the amount of effort lower if we ever need to implement a module for another vendor (or if a community member does).

Modules update in #279

@phorcys420 phorcys420 marked this pull request as ready for review August 1, 2025 15:31
@phorcys420 phorcys420 self-assigned this Aug 1, 2025
@phorcys420 phorcys420 requested a review from matifali August 2, 2025 15:45
matifali
matifali previously approved these changes Aug 3, 2025
Copy link
Member

@matifali matifali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot @phorcys420. This will significantly enhance the DevEX for module development and maintenance.

@phorcys420 phorcys420 enabled auto-merge (squash) August 4, 2025 09:24
@phorcys420 phorcys420 requested a review from bpmct August 4, 2025 09:24
@matifali
Copy link
Member

Thoughts on adding MCP server support?
We can add a generic input named mcp_config and mcp_path, which we can use from browser modules.

Here are a few examples

  1. Windsurf: /Users/matifali/.codeium/windsurf/mcp_config.json
  2. Cursor: ~/.cursor/mcp.json
  3. VS Code: Didn't find a user specfic setting path

@phorcys420
Copy link
Member Author

@matifali I want to add a config (and maybe extensions) entry in a next PR like we have for the code-server module, I think it should solve that.

@matifali
Copy link
Member

Nice. But I think exposing MCPs separately would make more sense given how popular they are.

@Copilot Copilot AI review requested due to automatic review settings August 11, 2025 16:02
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR introduces a new vscode-desktop-core module to centralize VSCode desktop IDE logic across multiple modules, acting as a building block similar to how AgentAPI functions for other modules. This effort aims to reduce code duplication and maintenance burden.

  • Creates a core Terraform module for VSCode desktop IDE functionality
  • Provides a reusable foundation for VSCode-based IDE modules
  • Includes comprehensive test coverage and documentation

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
registry/coder/modules/vscode-desktop-core/main.tf Core Terraform module implementation with variables, data sources, and coder_app resource
registry/coder/modules/vscode-desktop-core/main.test.ts Comprehensive test suite covering various configuration scenarios
registry/coder/modules/vscode-desktop-core/README.md Documentation with usage examples and caution about direct usage

@matifali matifali disabled auto-merge August 11, 2025 16:03
@matifali matifali enabled auto-merge (squash) August 11, 2025 16:20
@matifali matifali merged commit 63d56ea into main Aug 11, 2025
4 checks passed
@matifali matifali deleted the phorcys420/centralize-vscode-desktop branch August 11, 2025 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants