Skip to content

docs(agents): add VS Code extension to project map - #2267

Open
superyoung9208 wants to merge 1 commit into
MoonshotAI:mainfrom
superyoung9208:docs/add-vscode-to-project-map
Open

docs(agents): add VS Code extension to project map#2267
superyoung9208 wants to merge 1 commit into
MoonshotAI:mainfrom
superyoung9208:docs/add-vscode-to-project-map

Conversation

@superyoung9208

Copy link
Copy Markdown

Related Issue

No linked issue.

Problem

The root AGENTS.md project map omits apps/vscode, even though the official VS Code extension is now part of the repository. This leaves the project map incomplete and makes the extension's runtime and shared-state boundaries harder for contributors and coding agents to discover.

PR #647 previously proposed adding a similar project-map entry, but it remains open as part of an earlier VS Code workspace implementation. The current extension implementation was merged through #1769 without the corresponding root project-map update.

What changed

Added apps/vscode to the project map, documenting:

  • its extension identifier and minimum VS Code version;
  • its Node SDK, Extension Host, and webview architecture;
  • its primary entry points;
  • the configuration, authentication, MCP, and session state shared through KIMI_CODE_HOME.

Validation

  • Verified the description against apps/vscode/package.json, its runtime entry points, and README.
  • Ran git diff --check.
  • No tests were run because this is a documentation-only change.

Checklist

  • I have read the CONTRIBUTING document.
  • I have linked a related issue, or explained the problem above.
  • Tests are not applicable because this is a documentation-only change.
  • Ran gen-changesets; this PR does not need a changeset.
  • gen-docs is not needed because this does not change user-facing behavior or documentation.

@changeset-bot

changeset-bot Bot commented Jul 27, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 3102470

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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.

1 participant