Pulse Report (demo data)

Generated 2026-03-15 20:26 · Data from 2026-03-10 to 2026-03-14

Pulse tracks what happens inside your Claude Code sessions — every tool call, every prompt, every error. This report summarizes your activity so you can see patterns, spot bottlenecks, and understand how you work with AI.

9,400
Total Events
Tool calls, prompts, session events
24
Sessions
One Claude Code conversation = one session
392
Prompts
Messages you sent to Claude

Key Insights

Tool Mix

Which Claude Code tools are used most. Tools include Read (file reading), Edit (file editing), Bash (shell commands), Write (file creation), Grep (search), and others.

Error Rate by Tool

A failure means a tool call returned an error, triggering a retry or debug cycle. Higher rates = more time spent fixing. Only tools with failures shown.

Events per Day

Total activity per day. More events generally means more active coding sessions. Useful for spotting trends over time.

Prompts per Hour

Distribution of your prompts across the day. Shows when you are most active. Gaps indicate hours with no Claude Code usage.

Session Sizes

Each bar is one Claude Code session, sorted by event count. Large sessions often involve complex multi-step tasks or long debugging chains.