Skip to content

Move JudgmentKit install to loopback HTTP#1

Merged
mikeylong merged 3 commits intomainfrom
codex/loopback-http-frontend-skill
Apr 23, 2026
Merged

Move JudgmentKit install to loopback HTTP#1
mikeylong merged 3 commits intomainfrom
codex/loopback-http-frontend-skill

Conversation

@mikeylong
Copy link
Copy Markdown
Contributor

Summary

  • make local loopback Streamable HTTP the canonical install target at http://127.0.0.1:8765/mcp
  • add shared MCP HTTP handling plus the repo-local mcp:local runtime
  • fold the original FrontendSkill visual resources into the AI UI workflow guardrails/examples
  • add AI UI E2E evaluator tooling and ignore generated artifacts/ outputs

Validation

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
judgmentkit-ai Ready Ready Preview, Comment Apr 23, 2026 5:05am

Request Review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 17b89bfdd9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +61 to +62
const body = Buffer.from(await response.arrayBuffer());
res.end(body);
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Stream MCP HTTP responses instead of buffering entire body

sendResponse buffers every Response with await response.arrayBuffer() before writing to Node's socket, which breaks long-lived text/event-stream responses returned by handleMcpHttpRequest for Streamable HTTP/SSE clients. In that path the body is intentionally streaming, so waiting for full completion can stall the handshake indefinitely and make the local loopback server unusable for clients that negotiate SSE.

Useful? React with 👍 / 👎.

Comment thread lib/install-mcp.ts
Comment on lines +270 to +274
endpoint: createLocalMcpUrl(host, port),
startCommand: materializeLocalPath(
connection.loopback_runtime.start_command,
contract,
checkoutPath,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Include host/port overrides in emitted local start command

The installer now supports custom --host/--port and writes the MCP endpoint accordingly, but startCommand is still materialized from the static runtime command without embedding those overrides. If a user installs with a non-default port (for example --port 18765) and then runs the printed Start local MCP command, the server starts on defaults (127.0.0.1:8765), so the configured client endpoint and running server no longer match.

Useful? React with 👍 / 👎.

@mikeylong mikeylong merged commit 3af2ac8 into main Apr 23, 2026
4 checks passed
@mikeylong mikeylong deleted the codex/loopback-http-frontend-skill branch April 23, 2026 05:08
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