Skip to content

docs(mcp): fix stale 'NOT WIRED YET' comment in telemetry.ts (#6617) #6700

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JSONbored merged 1 commit into from
Jul 17, 2026
Merged

docs(mcp): fix stale 'NOT WIRED YET' comment in telemetry.ts (#6617) #6700

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions src/mcp/telemetry.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,10 @@ import { PostHog } from "posthog-node";
// The wrapper also never throws: a PostHog init/capture failure degrades to recording nothing, exactly like
// the unconfigured path, so it can never surface an error into the MCP tool caller.
//
// NOT WIRED YET: per #6235 this module is deliberately NOT called from the tool-dispatch path — that (and the
// client lifecycle/flush strategy a live Worker needs) is the separate instrumentation issue's job.
// WIRED into the remote tool-dispatch path (#6237, merged PR #6358): {@link recordMcpToolCall} is invoked from
// `recordMcpToolTelemetry` in src/mcp/server.ts — the single chokepoint every `tools/call` request that reaches
// handleMcpRequest routes through exactly once, whether it succeeds or throws. (The local/CLI-side counterpart,
// packages/loopover-mcp/lib/telemetry.js, has its own separate wiring status per #6236/#6238.)

/** PostHog US-cloud ingestion host — the default when POSTHOG_HOST isn't set. */
const DEFAULT_POSTHOG_HOST = "https://us.i.posthog.com";
Expand Down