Claude Code Usage | Token Consumption, Checking Remaining Balance, and Handling Limits

Usage Basics

Claude Code Pricing Plans

What Counts Toward Usage

1. Input tokens: Your questions and prompts
2. Output tokens: Claude's responses
3. File reading: Reading code files
4. Command execution results: Analyzing output

How to Check Usage

Check Within Claude Code

/usage

Or:

/status

Information Displayed

Current Session:
- Tokens used: 15,420
- API calls: 23

Today's usage:
- Total tokens: 45,000
- Remaining (approx): 155,000

Check on the Web Dashboard

1. Log in to claude.ai
2. Open Settings
3. Check the "Usage" tab

Usage Limits by Plan

Pro Plan

• 5-hour limit: A set amount of requests
• When limit is reached: Temporarily restricted
• Reset: Recovers after 5 hours

Max Plan

API Usage

• No limit: Unlimited within your budget
• Pay-as-you-go: Pay only for what you use
• Rate limit: Limited requests per minute

What to Do When You Hit the Limit

Symptoms

Rate limit reached. Please wait before making more requests.

Or:

You've reached your usage limit for this period.

Solution 1: Wait

Pro plan: Limit resets after 5 hours
Max plan: Resets faster

Solution 2: Upgrade Your Plan

Pro → Max 5x: 5x the usage
Max 5x → Max 20x: Even more capacity

Solution 3: Switch to API

# Configure API usage
export ANTHROPIC_API_KEY=your-api-key
claude --api

Tips to Save Usage

1. Give Clear Instructions

❌ Bad example (likely to generate follow-up questions):
"Improve this code"

✅ Good example (likely to complete in one go):
"Improve the formatDate function in src/utils/date.ts
with the following requirements:
- Support ISO 8601 format
- Handle timezones
- Handle null/undefined"

2. Specify Only the Necessary Files

❌ Bad example:
"Look at the entire project"

✅ Good example:
"Check src/components/Button.tsx"

3. Avoid Long Output

# No need to show all logs
npm install 2>&1 | tail -10

# Limit commit history too
git log -5

4. Request Multiple Tasks at Once

❌ Bad example (3 interactions):
1. "Create function A"
2. "Create function B"
3. "Create tests"

✅ Good example (1 interaction):
"Please create the following 3 items:
1. User retrieval function (getUser)
2. User update function (updateUser)
3. Unit tests for both"

5. Use CLAUDE.md

Document frequently repeated information in CLAUDE.md:

# CLAUDE.md

## Tech Stack
- Next.js 14
- TypeScript
- Tailwind CSS

## Coding Conventions
- Functional components
- Type definitions required

Monitoring Usage

Check Regularly

# Check at the start of the day
claude
/usage

Understand High-Usage Tasks

Set Alerts (For API Usage)

# Set budget limit
export ANTHROPIC_MAX_TOKENS=100000

Guide for Choosing a Plan

Pro Plan Is Best For

• Using a few times a week
• Personal projects
• Learning purposes

Max 5x Is Best For

• Using several hours daily
• Medium-sized projects
• Freelancers

Max 20x Is Best For

• All-day usage
• Large-scale projects
• Team development

API Is Best For

• Unpredictable usage patterns
• Automation needs
• CI/CD usage

Usage Optimization Examples

Example 1: Code Review

❌ Inefficient:
"Please review this PR"
→ Reads all files, consuming large amounts of tokens

✅ Efficient:
"Please review the following changes:
- src/auth/login.ts: Authentication logic added
- src/components/LoginForm.tsx: Form UI
Please focus on security aspects"

Example 2: Bug Fix

❌ Inefficient:
"I'm getting an error. Fix it."
→ Additional questions needed for information gathering

✅ Efficient:
"Please fix the following error:
Error: TypeError: Cannot read property 'id' of undefined
File: src/api/users.ts:42
Situation: Occurs when user does not exist"

Example 3: New Feature Development

❌ Inefficient:
"Create an authentication feature"
→ Vague, requiring multiple back-and-forth exchanges

✅ Efficient:
"Please implement an authentication feature with the following specs:

## Requirements
- Login with email/password
- Session management with JWT tokens
- Refresh token support

## Tech Stack
- Next.js API Routes
- Prisma
- bcrypt

## File Structure
- src/lib/auth.ts: Authentication logic
- src/pages/api/auth/login.ts: Login API
- src/pages/api/auth/refresh.ts: Refresh API"

FAQ

Q: Is usage reflected in real-time?

A: It's nearly real-time, but there may be a delay of a few minutes.

Q: Can unused quota be carried over to the next month?

A: No, there is no carryover. It resets each month.

Q: Can I estimate usage in advance?

A: Exact estimates are difficult, but you can roughly calculate that 1 token ≈ about 4 English characters.

Q: Is usage shared across multiple projects?

A: Yes, usage is shared across the entire account.

Q: Can teams separate their usage?

A: With the Team plan, you can view usage per team member.

Summary

Claude Code usage management:

Key points for saving:

1. Clear instructions: Be specific so tasks complete in one go
2. Specify files: Only load necessary files
3. Limit output: Avoid long logs
4. Batch requests: Handle related tasks at once
5. Use CLAUDE.md: Reduce repeated explanations

By being mindful of usage, you can use Claude Code more efficiently.

References

• Claude Code Official Documentation
• Claude Pricing Plans
• API Usage Dashboard