Skip to content

feat: add independent named proxy listeners - #471

Draft
DivyamTalwar wants to merge 1 commit into
apify:mainfrom
DivyamTalwar:feat/proxy-listener-lifecycle-306-1509
Draft

DivyamTalwar wants to merge 1 commit into
apify:mainfrom
DivyamTalwar:feat/proxy-listener-lifecycle-306-1509

Conversation

@DivyamTalwar

@DivyamTalwar DivyamTalwar commented Oct 22, 2026 •

Copy link
Copy Markdown

Adds mcpc proxy @session to list, attach, and stop named listeners without replacing the upstream session. Listeners have independent credentials and restart persistence; connect --proxy remains supported with a deprecation hint.

  • Persist lifecycle state, fence bridge ownership, and retain retryable credential cleanup receipts.
  • Preserve legacy configuration/token pairing and show per-listener restoration failures.
  • Validate unit regressions, the Node legacy/modern and Bun E2E matrix, identical-package lifecycle checks, and official MCP conformance.
  • Named management requires trusted POSIX IPC; Windows is explicitly refused until named-pipe ownership is verified.

Draft for CLI/platform review. Initial runtime validation used Linux Node and Bun. Native macOS validation is recorded below; Windows named management remains deliberately unsupported.

Refs #306

Implemented and independently reviewed with OpenAI Codex in ChatGPT; no Claude Code session was used.

Native macOS validation follow-up — 23 October 2026

Revalidated exact head ee5ef1a44ac17c33e0d8a6314054d7c1eaf0519e on native macOS/Node25.2.1 with disposable test homes:

  • Frozen-lockfile install and production build passed.
  • Full unit suite: 1,394 passed, 2 existing skips across63 files.
  • Real local proxy E2E suites (proxy, proxy-lifecycle, proxy-control-trust): 3/3 passed in legacy mode and3/3 passed in modern mode, no skipped or failed suites.

This adds actual native macOS lifecycle/IPC evidence to the prior Linux Node/Bun runs. An initial build correctly failed because dependencies were absent; installing the unchanged lockfile resolved setup without source or assertion changes. No user authentication profiles were used.

Windows named management remains deliberately unsupported until its ownership/trust contract is implemented and validated; these Mac results do not claim Windows support. Maintainer CLI/API review and upstream CI authorization remain separate gates.

Signed-off-by: Divyam Talwar <divyamtalwar0@gmail.com>

This branch has not been deployed

No deployments
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