feat: anonymous telemetry and in-app feedback (Spec 036)#345
Merged
Conversation
Deploying mcpproxy-docs with
|
| Latest commit: |
f44b3f4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6b8d89cd.mcpproxy-docs.pages.dev |
| Branch Preview URL: | https://feat-036-telemetry-and-feedb.mcpproxy-docs.pages.dev |
📦 Build ArtifactsWorkflow Run: View Run Available Artifacts
How to DownloadOption 1: GitHub Web UI (easiest)
Option 2: GitHub CLI gh run download 23449237372 --repo smart-mcp-proxy/mcpproxy-go
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Detail telemetry enable/disable CLI behavior and output - Add documentation deliverables: CLAUDE.md, docs/features/telemetry.md, configuration.md, swagger.yaml - Clarify CLI feedback uses local API via socket Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…eedback feature Add frontend components for Spec 036 (telemetry and feedback): - Feedback.vue: form with category, message, email fields posting to /api/v1/feedback - TelemetryBanner.vue: dismissible info banner on Dashboard (localStorage-persisted) - Route /feedback added to router - Feedback link added to SidebarNav and NavBar menus - submitFeedback method added to API service Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
… (036) Backend implementation for anonymous usage telemetry and feedback: - TelemetryConfig in config with IsTelemetryEnabled(), env var override - Telemetry service: daily heartbeat, 5min startup delay, fire-and-forget - Feedback: validation, rate limiting (5/hr), proxy to Cloudflare Worker - HTTP API: POST /api/v1/feedback endpoint - CLI: mcpproxy telemetry status/enable/disable, mcpproxy feedback - Runtime wiring: RuntimeStats interface, background goroutine launch - Tests: 19 new tests covering all paths Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Create docs/features/telemetry.md with full privacy policy, data collected/excluded, and three ways to disable - Add telemetry/feedback CLI commands to CLAUDE.md - Add MCPPROXY_TELEMETRY env var to CLAUDE.md - Add POST /api/v1/feedback to API endpoints table Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Pass context through to http.NewRequestWithContext so in-flight heartbeat requests are cancelled immediately on app shutdown instead of blocking up to 10s on the client timeout. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Dumbris
force-pushed
the
feat/036-telemetry-and-feedback
branch
from
ba9dd48 to
f44b3f4
Compare
Dumbris
pushed a commit
that referenced
this pull request
Apr 11, 2026
The telemetry enable/disable commands correctly loaded config via loadTelemetryConfig() (which honors the --config flag) but then hardcoded the save path to config.GetConfigPath(cfg.DataDir), so `mcpproxy --config /custom.json telemetry disable` always wrote to ~/.mcpproxy/mcp_config.json instead of the custom path. This is a pre-existing bug introduced in PR #345 (Spec 036), not Spec 042. Add a small telemetryConfigSavePath helper that mirrors the load logic: prefer the package-level configFile flag when set, else fall back to GetConfigPath(DataDir). Apply it to runTelemetryEnable, runTelemetryDisable, and runTelemetryShowPayload (the latter passes the path to telemetry.New which persists the anonymous ID). Adds regression tests covering both enable and disable, plus a direct helper unit test, with HOME sandboxed to t.TempDir() so accidental writes to the real home config are detected. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
5 tasks
Dumbris
pushed a commit
that referenced
this pull request
Apr 11, 2026
The telemetry enable/disable commands correctly loaded config via loadTelemetryConfig() (which honors the --config flag) but then hardcoded the save path to config.GetConfigPath(cfg.DataDir), so `mcpproxy --config /custom.json telemetry disable` always wrote to ~/.mcpproxy/mcp_config.json instead of the custom path. This is a pre-existing bug introduced in PR #345 (Spec 036), not Spec 042. Add a small telemetryConfigSavePath helper that mirrors the load logic: prefer the package-level configFile flag when set, else fall back to GetConfigPath(DataDir). Apply it to runTelemetryEnable, runTelemetryDisable, and runTelemetryShowPayload (the latter passes the path to telemetry.New which persists the anonymous ID). Adds regression tests covering both enable and disable, plus a direct helper unit test, with HOME sandboxed to t.TempDir() so accidental writes to the real home config are detected. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Dumbris
added a commit
that referenced
this pull request
Apr 11, 2026
The telemetry enable/disable commands correctly loaded config via loadTelemetryConfig() (which honors the --config flag) but then hardcoded the save path to config.GetConfigPath(cfg.DataDir), so `mcpproxy --config /custom.json telemetry disable` always wrote to ~/.mcpproxy/mcp_config.json instead of the custom path. This is a pre-existing bug introduced in PR #345 (Spec 036), not Spec 042. Add a small telemetryConfigSavePath helper that mirrors the load logic: prefer the package-level configFile flag when set, else fall back to GetConfigPath(DataDir). Apply it to runTelemetryEnable, runTelemetryDisable, and runTelemetryShowPayload (the latter passes the path to telemetry.New which persists the anonymous ID). Adds regression tests covering both enable and disable, plus a direct helper unit test, with HOME sandboxed to t.TempDir() so accidental writes to the real home config are detected. Co-authored-by: Claude Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mcpproxy telemetry status/enable/disable,mcpproxy feedbackdocs/features/telemetry.mdWhat's collected
Version, OS, arch, server/tool counts, uptime, routing mode. Never: server names, URLs, keys, tool content, user data.
How to disable
Test plan
-racenpm run build)make buildpasses (personal + tray editions)🤖 Generated with Claude Code