Skip to content

feat: add shared loopback HTTP transport - #53

Open
TheVillageGuy wants to merge 1 commit into
pardeike:mainfrom
TheVillageGuy:codex/shared-http-transport
Open

feat: add shared loopback HTTP transport#53
TheVillageGuy wants to merge 1 commit into
pardeike:mainfrom
TheVillageGuy:codex/shared-http-transport

Conversation

@TheVillageGuy

Copy link
Copy Markdown

Add an opt-in Streamable HTTP host so multiple MCP clients can use one DecompilerServer process and singleton workspace instead of retaining one stdio child per client.

Keep stdio as the compatibility default, restrict HTTP listeners to configurable loopback origins, and bound compatibility sessions to a ten-minute idle timeout and 64 sessions.

Upgrade the MCP SDK to 2.2.0 with ASP.NET Core transport support, document Codex URL configuration and the runtime model, and cover launch parsing plus loopback validation.

Validation: nine new launch tests pass; stdio initialize/tools-list smoke passes; two independent HTTP sessions share one PID; an idle HTTP server used 63.5 MiB and 0.125 CPU seconds over five seconds. The broader suite passes 195/201, with six unchanged Windows path-normalization assertions failing outside this change.

Add an opt-in Streamable HTTP host so multiple MCP clients can use one DecompilerServer process and singleton workspace instead of retaining one stdio child per client.

Keep stdio as the compatibility default, restrict HTTP listeners to configurable loopback origins, and bound compatibility sessions to a ten-minute idle timeout and 64 sessions.

Upgrade the MCP SDK to 2.2.0 with ASP.NET Core transport support, document Codex URL configuration and the runtime model, and cover launch parsing plus loopback validation.

Validation: nine new launch tests pass; stdio initialize/tools-list smoke passes; two independent HTTP sessions share one PID; an idle HTTP server used 63.5 MiB and 0.125 CPU seconds over five seconds. The broader suite passes 195/201, with six unchanged Windows path-normalization assertions failing outside this change.
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