Claude Code activity breakdown

See detailed Claude Code activity patterns across teams and modes

Available at Insights / AI assistants /Claude Code

If you're looking for a productivity boost from Claude Code, it's not enough to enable the tool for your teams and then forget it. People need to pick up the new habit and invest the time to learn how to use it effectively. To support that, you need proper visibility into the current activity patterns.

With the Claude Code activity breakdown, you can:

• Understand where Claude Code is gaining traction and where extra support may be needed.

• Know if people are just trying it out or actively relying on it in their work.

• Notice patterns in action proposals

Read more in our full guide:

Measure the productivity impact of AI tools

To track Claude Code adoption and licenses, see:

AI adoption metrics

Setup

Enabling Claude Code metrics:

AI coding tool integrations

Definitions

• Active users = Users who have opened the Claude Code client, and have any logged activity.

• Lines added / removed = Total number of lines added / removed by the Claude Code across all files (not necessarily committed)

• Actions accepted / rejected = The number of Claude Code tool action proposals that the user accepted / rejected. Includes all file editing and creation actions.

• Action acceptance rate = Actions accepted / (Actions accepted + Actions rejected)

Not all accepted code ends up in the codebase. An engineer could accept 200 Claude Code-generated lines over the course of creating a 10-line pull request.

You can't use these metrics to get an accurate number of the share of your code that's AI-generated.