Telemetry

Hyprlayer ships anonymized telemetry on by default so we can see which commands matter, where they fail, and which Claude Code and Codex model versions need attention.

If you’d rather not contribute, opting out takes one command.

Opt out

hyprlayer telemetry off

Re-enable later with hyprlayer telemetry on. Hyprlayer keeps your installation_id across off/on cycles, so we don’t double-count the same machine when you flip back. Turning telemetry off also removes the Claude Code Stop hook.

Self-hosting

If you run your own PostHog instance:

hyprlayer telemetry config --api-key <your-public-key>

Hook installation

Hyprlayer installs a Stop hook in ~/.claude/settings.json automatically while telemetry is on, and removes it when you opt out. It leaves your other hooks in place. The hook runs hyprlayer telemetry record-from-hook, which reads the Stop payload, summarizes the active skill turn, and appends one skill_run event to the local spool. It never calls the network itself.

hyprlayer telemetry hook install|uninstall|status exist for repair.