add-telemetry
Add telemetry events to track user behavior or system events in the Warp codebase. Use when instrumenting new features, debugging issues, or measuring product metrics.
Install
With your agent
Install OMGSkills skill "warpdotdev/warp:add-telemetry" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/warpdotdev/warp /tmp/warp && ln -s /tmp/warp/.agents/skills/add-telemetry ~/.claude/skills/add-telemetryFrom README
add-telemetry Overview Warp uses a trait-based telemetry system where feature-specific enums implement the TelemetryEvent trait. This approach keeps telemetry events organized by domain rather than in one giant enum. Important: Before implementing telemetry, collaborate with the user to: Define what events should be tracked and when Determine what data should be included in each event Clarify the purpose and expected of the telemetry Adding telemetry code is straightforward, but designing meaningful instrumentation requires careful thought. Steps Identify or create a telemetry module Find an existing feature-specific telemetry file (e.g., app/src/antivirus/telemetry.rs) or create a new one for your feature area.
More from this repo
add-feature-flag
Used to add a new feature flag to gate code changes in the Warp codebase.
factory-files
Used to create and edit file-based Warp software factory definitions, in a repository tree rooted at a factory.yaml.
factory-mcp
Use the Warp Factory MCP to hand work to a software factory and collaborate with it — bundle local work and send it to...