* feat(network): add Network screen surfacing backend fetch log (#1355) Routes `FetchRequestLogState` to a new Network tab so users can inspect HTTP-layer request/response headers, status, duration, and category (auth vs transport) of every fetch the backend makes for an active session. Adds `NetworkControls` + `NetworkStreamPanel` + `NetworkEntry` groups, a `monoBreak` Text theme variant for long header values, and wires onClearNetwork / onExportNetwork (JSON download) from `App.tsx`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(network): include request / response bodies in search filter Headers were already covered but bodies were not, so searches for strings that live inside the JSON-RPC payload (e.g. "jsonrpc", "initialize", a tool name) silently returned no matches. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(network): always render Response Body section, note streaming Streaming responses (text/event-stream, application/x-ndjson, POST to /mcp) are intentionally not body-captured by the fetch tracker, so the section was silently omitted. Now whenever a response was received we render the section, with either the body, a "(empty)" note, or a "Streaming response — body not captured" note keyed off content-type. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(network): capture response bodies via async body-update events Two related fixes: 1. The fetch tracker was marking every streamable-HTTP POST /mcp call as "not captured" because the response content-type is text/event-stream. In practice those streams are bounded — the server sends the JSON-RPC reply (sometimes preceded by progress events) and closes — so we can clone the body and read it. Only GET + SSE / ndjson is the unbounded long-lived channel that has to stay uncaptured. 2. Reading the body inline blocked the transport from processing progress notifications until the entire stream finished, breaking the `resetTimeoutOnProgress` integration test. The body is now read in the background and dispatched via a new `fetchRequestBodyUpdate` event that the FetchRequestLogState patches into the matching entry by id. Plumbing wires through node/transport, the remote SSE channel (RemoteSession, RemoteClientTransport), and the remote event types. Also hides the Network tab when the active server is stdio (no HTTP traffic to surface) and bumps the inline body preview limit to 100 KB so typical tools/list responses render rather than tripping the "too large" notice. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(network): show orange SSE badge for long-lived stream entries Adds a small "SSE" badge to the right side of the NetworkEntry header (left of the HTTP status badge) when the response is a long-lived streaming channel (GET + text/event-stream or application/x-ndjson) — the only case where the body genuinely isn't captured. Makes the "not captured" placeholder less surprising at a glance. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(network): address PR review findings - Stop capturing OAuth response bodies (drop updateResponseBody from the effectiveAuthFetch tracker). Restores pre-PR behavior for auth-category entries so live access_token / refresh_token values can't leak into the Network tab body preview during a screen-share. Headers + status are still tracked. - Extract `isLongLivedStreamResponse(method, contentType)` to core/mcp/fetchTracking so the rule lives in one place; consumed by the tracker and the NetworkEntry UI placeholder. - Document the intent of NetworkEntry's `useEffect` (the list-level toggle is authoritative; per-entry overrides are intentionally discarded on each list toggle). - Rename MAX_INLINE_BODY_BYTES → MAX_INLINE_BODY_CHARS (`.length` is UTF-16 code units, not bytes) and update the user-facing notice. - Switch NetworkStreamPanel's search from joined-string `.includes` to per-field `.some(.includes)` so a term can't span field boundaries. Regression test added. - Add aria-label to ListToggle ("Expand all" / "Collapse all") — both an a11y improvement and a stable selector that lets the panel test stop fishing the button out by text-content negation. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test(network): use ListToggle aria-label in panel + modal tests Cleanup spotted in PR review follow-up: - HistoryListPanel + ServerSettingsModal previously fished the ListToggle out by empty text content because the toggle had no accessible name. Now that ListToggle exposes "Expand all" / "Collapse all", both tests can use getByRole + name and the stale comments go away. - ListToggle's own tests now assert the aria-label contract so a future refactor can't silently drop it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(network): expose category toggle state via aria-pressed The category UnstyledButtons in NetworkControls previously communicated their toggled state only via background color. Adds aria-pressed={active} so assistive tech can discover the on/off state without visuals, with a test that asserts the attribute tracks the visibleCategories prop. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
116 lines
3 KiB
TypeScript
116 lines
3 KiB
TypeScript
/**
|
|
* Remote session - holds a transport and event queue for a remote client.
|
|
*/
|
|
|
|
import type { Transport } from "@modelcontextprotocol/sdk/shared/transport.js";
|
|
import type { JSONRPCMessage } from "@modelcontextprotocol/sdk/types.js";
|
|
import type { FetchRequestEntryBase } from "../../types.js";
|
|
import type { RemoteEvent } from "../types.js";
|
|
|
|
export interface SessionEvent {
|
|
type: RemoteEvent["type"];
|
|
data: unknown;
|
|
}
|
|
|
|
export class RemoteSession {
|
|
public readonly sessionId: string;
|
|
public transport!: Transport;
|
|
private eventQueue: SessionEvent[] = [];
|
|
private eventConsumer: ((event: SessionEvent) => void) | null = null;
|
|
private transportDead: boolean = false;
|
|
private transportError: string | null = null;
|
|
|
|
constructor(sessionId: string) {
|
|
this.sessionId = sessionId;
|
|
}
|
|
|
|
setTransport(transport: Transport): void {
|
|
this.transport = transport;
|
|
}
|
|
|
|
setEventConsumer(consumer: (event: SessionEvent) => void): void {
|
|
this.eventConsumer = consumer;
|
|
// Flush queued events
|
|
while (this.eventQueue.length > 0) {
|
|
const ev = this.eventQueue.shift()!;
|
|
consumer(ev);
|
|
}
|
|
}
|
|
|
|
clearEventConsumer(): boolean {
|
|
this.eventConsumer = null;
|
|
// If transport is dead and no client connected, signal to cleanup
|
|
return this.transportDead;
|
|
}
|
|
|
|
markTransportDead(error: string): void {
|
|
this.transportDead = true;
|
|
this.transportError = error;
|
|
// Always push the transport_error event — pushEvent queues it if no
|
|
// consumer is attached yet, so a process that crashes during startup
|
|
// (between POST /api/mcp/connect returning 200 and the browser opening
|
|
// /api/mcp/events) still surfaces its error to the eventual consumer
|
|
// instead of vanishing.
|
|
this.pushEvent({
|
|
type: "transport_error",
|
|
data: {
|
|
error,
|
|
code: -32000, // MCP error code for connection closed
|
|
},
|
|
});
|
|
}
|
|
|
|
isTransportDead(): boolean {
|
|
return this.transportDead;
|
|
}
|
|
|
|
getTransportError(): string | null {
|
|
return this.transportError;
|
|
}
|
|
|
|
hasEventConsumer(): boolean {
|
|
return this.eventConsumer !== null;
|
|
}
|
|
|
|
pushEvent(event: SessionEvent): void {
|
|
if (this.eventConsumer) {
|
|
this.eventConsumer(event);
|
|
} else {
|
|
this.eventQueue.push(event);
|
|
}
|
|
}
|
|
|
|
onMessage(message: JSONRPCMessage): void {
|
|
this.pushEvent({ type: "message", data: message });
|
|
}
|
|
|
|
onFetchRequest(entry: FetchRequestEntryBase): void {
|
|
this.pushEvent({
|
|
type: "fetch_request",
|
|
data: {
|
|
...entry,
|
|
timestamp:
|
|
entry.timestamp instanceof Date
|
|
? entry.timestamp.toISOString()
|
|
: entry.timestamp,
|
|
},
|
|
});
|
|
}
|
|
|
|
onFetchResponseBody(id: string, responseBody: string): void {
|
|
this.pushEvent({
|
|
type: "fetch_request_body_update",
|
|
data: { id, responseBody },
|
|
});
|
|
}
|
|
|
|
onStderr(entry: { timestamp: Date; message: string }): void {
|
|
this.pushEvent({
|
|
type: "stdio_log",
|
|
data: {
|
|
timestamp: entry.timestamp.toISOString(),
|
|
message: entry.message,
|
|
},
|
|
});
|
|
}
|
|
}
|