[rushd][WS6] Web UX & MCP bridge

Open
#5,901 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
nodejs, typescript
Domain
api, backend, security, testing, web-dev

Research direction

Start by reviewing dependencies #5896 and #5897, then inspect the rush daemon protocol, the rush-serve-plugin infrastructure, and apps/rush-mcp-server. Define the work around the listed acceptance criteria: loopback WS/HTTP bridging with authentication and origin checks, multi-tab fan-out, an MCP build call with structured streaming, and integration tests running in CI.

Written by the indexing model from the issue text.

Description

area:rushd

Optional additional clients over the same protocol — a web dashboard bridge and an MCP client — validating the client-agnostic thesis with non-terminal consumers.

Depends on: #5896; #5897

Scope

  • @rushstack/rush-daemon-web bridge. A rush daemon serve bridge translating socket⇄WS/HTTP (reusing rush-serve-plugin infra), loopback-only with token auth + an Origin allow-list, and N-tab fan-out from one daemon.
  • MCP client. Speak the same daemon protocol (may refit apps/rush-mcp-server), validating the client-agnostic thesis with a non-terminal consumer.

Acceptance criteria

  • rush daemon serve bridges the daemon socket to WS/HTTP and fans out to N tabs from one daemon; it binds loopback-only and enforces token auth + an Origin allow-list (non-loopback/bad-origin refused).
  • A representative MCP tool call drives a build via the daemon and streams structured results back, consuming only the presentation-free protocol (no terminal assumptions).
  • Auth/origin, fan-out, and the MCP path are covered by integration tests; tests green in CI.

Part of #5894.

Dominant language
TypeScript
Stars
6.5k
Forks
708
Avg merge
5d 7h
Merged PRs (30d)
44

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/rushstack

All issues in microsoft/rushstack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.