feat(tracking): tag agent-connected requests with client=mcp#56
Conversation
Pairs with cloud-backend support for a `client` field on /tracking/v1/agent-connected so PostHog/Mixpanel can tell MCP connections apart from CLI. Without this, both sources POST identical bodies and the cloud cannot distinguish first-CLI-user from first-MCP-user adoption.
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 6 minutes and 31 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
UsageTracker.reportAgentConnected()now sendsclient: 'mcp'in the request body to/tracking/v1/agent-connected.usage-tracker.test.tsto lock in the new behavior.Why
Pairs with insforge-cloud-backend#472, which adds an optional
clientfield on the cloud endpoint so PostHog/Mixpanel can break down agent-connected events by source. Without this MCP-side change, every MCP session reports asclient: 'unknown'and is indistinguishable from CLI traffic.Test plan
/tracking/v1/agent-connectedrequest body — should include"client":"mcp"client=mcppropertynpm testpasses🤖 Generated with Claude Code