Skip to content

fix(build): automatically run mcp setup after build#17

Open
PavelA85 wants to merge 2 commits into
onllm-dev:mainfrom
PavelA85:fix/auto-build-mcp-setup
Open

fix(build): automatically run mcp setup after build#17
PavelA85 wants to merge 2 commits into
onllm-dev:mainfrom
PavelA85:fix/auto-build-mcp-setup

Conversation

@PavelA85
Copy link
Copy Markdown
Contributor

@PavelA85 PavelA85 commented May 7, 2026

This PR fixes an issue where the Native Messaging host isn't registered by default when developers run \pnpm build. This resulted in a \Local bridge: unavailable\ error when loading the unpacked extension. By modifying the build script to run \�uild:all && setup:mcp, the native host configuration and MCP server compilation happen seamlessly, making the developer experience smoother.

Copilot AI review requested due to automatic review settings May 7, 2026 23:34
Copy link
Copy Markdown

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 updates the root build workflow so that running pnpm build also performs MCP setup, aiming to prevent “Local bridge: unavailable” when developers load the unpacked extension by ensuring the native messaging host is registered and the MCP server is ready.

Changes:

  • Change root build to run build:all followed by setup:mcp.
  • Add build:extension script as a dedicated extension-only build entrypoint.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread package.json Outdated
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