Claude Token Tracking Guide

Overview

Claude Flow now includes REAL token tracking capabilities that capture actual Claude API usage, not simulated data. This guide shows how to enable and use token tracking with the Claude Code CLI.

Quick Start

Step 1: Enable Telemetry

First, enable telemetry for token tracking:

./claude-flow analysis setup-telemetry

This will:

• Set CLAUDE_CODE_ENABLE_TELEMETRY=1 environment variable
• Create .env file with telemetry settings
• Initialize token tracking directory (.claude-flow/metrics/)

Step 2: Run Claude with Token Tracking

Use the --claude flag with telemetry enabled:

# Option 1: Set environment variable inline
CLAUDE_CODE_ENABLE_TELEMETRY=1 ./claude-flow swarm "your task" --claude

# Option 2: Export environment variable
export CLAUDE_CODE_ENABLE_TELEMETRY=1
./claude-flow swarm "your task" --claude

# Option 3: Use wrapper directly
./claude-flow analysis claude-monitor  # Start monitoring in one terminal
./claude-flow swarm "your task" --claude  # Run Claude in another terminal

Step 3: View Token Usage

After running Claude commands:

# View comprehensive token usage report
./claude-flow analysis token-usage --breakdown --cost-analysis

# Get current session cost
./claude-flow analysis claude-cost

# Monitor session in real-time
./claude-flow analysis claude-monitor [session-id]

Architecture

How It Works

1. Claude Telemetry Integration: The system integrates with Claude's native OpenTelemetry support
2. Process Wrapping: When telemetry is enabled, Claude commands are wrapped to capture output
3. Token Extraction: Token usage is extracted from:
   • Claude CLI output patterns
   • Session JSONL files (if accessible)
   • /cost command output
4. Persistent Storage: Token data is stored in .claude-flow/metrics/token-usage.json

Key Components

• claude-telemetry.js: Core telemetry wrapper module
• token-tracker.js: Token tracking and cost calculation
• analysis.js: Analysis commands and reporting

Features

Real-Time Monitoring

Monitor Claude sessions as they run:

# Monitor with default 5-second interval
./claude-flow analysis claude-monitor

# Monitor with custom interval (3 seconds)
./claude-flow analysis claude-monitor current --interval 3000

Cost Analysis

Track costs based on Claude 3 pricing:

Token Breakdown

View token usage by:

• Agent type
• Command
• Session
• Time period

# Detailed breakdown
./claude-flow analysis token-usage --breakdown

# Agent-specific analysis
./claude-flow analysis token-usage --agent coordinator --cost-analysis

Advanced Usage

Programmatic Token Tracking

You can also use the telemetry wrapper programmatically:

import { runClaudeWithTelemetry } from './claude-telemetry.js';

const result = await runClaudeWithTelemetry(
  ['chat', 'Hello, Claude!'],
  {
    sessionId: 'my-session-123',
    agentType: 'custom-agent'
  }
);

Session Monitoring

Monitor specific sessions:

import { monitorClaudeSession } from './claude-telemetry.js';

const stopMonitor = await monitorClaudeSession('session-id', 5000);

// Stop monitoring when done
stopMonitor();

Troubleshooting

No Token Data Showing

1. Verify telemetry is enabled:

   bashCopy

   echo $CLAUDE_CODE_ENABLE_TELEMETRY  # Should output: 1
   

2. Check token usage file exists:

   bashCopy

   cat .claude-flow/metrics/token-usage.json
   

3. Ensure Claude is installed:

   bashCopy

   which claude  # Should show Claude path
   

Token Tracking Not Working

1. Clear existing metrics:

   bashCopy

   rm -rf .claude-flow/metrics/token-usage.json
   

2. Re-enable telemetry:

   bashCopy

   ./claude-flow analysis setup-telemetry
   

3. Run with explicit telemetry:

   bashCopy

   CLAUDE_CODE_ENABLE_TELEMETRY=1 ./claude-flow swarm "test" --claude
   

Integration with CI/CD

For automated environments:

# GitHub Actions example
env:
  CLAUDE_CODE_ENABLE_TELEMETRY: '1'
  
steps:
  - name: Setup telemetry
    run: ./claude-flow analysis setup-telemetry
    
  - name: Run Claude task
    run: ./claude-flow swarm "${{ inputs.task }}" --claude
    
  - name: Report costs
    run: ./claude-flow analysis claude-cost

Privacy & Security

• No sensitive data: Only token counts and costs are tracked
• Local storage: All data is stored locally in .claude-flow/metrics/
• Opt-in: Telemetry must be explicitly enabled
• No external transmission: Data is never sent to external servers

Best Practices

1. Enable telemetry once: Set it in your .env file for persistence
2. Monitor long tasks: Use claude-monitor for tasks > 5 minutes
3. Regular cost checks: Run claude-cost after expensive operations
4. Batch operations: Group Claude calls to optimize token usage
5. Use appropriate models: Choose Haiku for simple tasks, Opus for complex

API Reference

Commands

Environment Variables

Files

Examples

Complete Workflow

# 1. Setup
./claude-flow analysis setup-telemetry

# 2. Run task with tracking
export CLAUDE_CODE_ENABLE_TELEMETRY=1
./claude-flow swarm "Create a REST API with authentication" --claude

# 3. Check usage
./claude-flow analysis token-usage --breakdown --cost-analysis

# 4. Monitor next session
./claude-flow analysis claude-monitor &  # Run in background
./claude-flow swarm "Add tests to the API" --claude

# 5. Final cost report
./claude-flow analysis claude-cost

Optimization Example

# Analyze token usage patterns
./claude-flow analysis token-usage --breakdown

# Identify high-consumption agents
./claude-flow analysis token-usage --agent coordinator

# Get optimization suggestions
./claude-flow analysis bottleneck-detect --scope agent

Support

For issues or questions:

• GitHub Issues: https://github.com/ruvnet/claude-flow/issues
• Documentation: https://github.com/ruvnet/claude-flow/docs

Conclusion

Real token tracking in Claude Flow provides transparency into API usage and costs. By following this guide, you can:

• Track actual Claude API token consumption
• Monitor costs in real-time
• Optimize token usage patterns
• Make informed decisions about model selection

Remember: This tracks REAL usage, not simulated data!