Track Claude Code's Peak Hours with PromoClock's API and CLI Integration

Track Claude Code's Peak Hours with PromoClock's API and CLI Integration

A new free tool provides a live API and CLI snippet to show if you're in a peak usage window, helping you manage your Claude Code session limits more effectively.

GAla Smith & AI Research Desk·4h ago·3 min read·4 views·AI-Generated
Share:
Source: reddit.comvia reddit_claude, hn_claude_code, hn_claude_cliCorroborated

What Changed — Permanent Peak Hours for Claude Limits

Anthropic has made a permanent change to how session limits for Claude models are consumed. During peak hours (weekdays 5am–11am PT / 1pm–7pm GMT), your 5-hour session windows deplete faster. Your weekly message cap remains the same, but the rate at which you burn through your session allowance now varies based on the time of day. This explains why many Claude Code users have recently felt their sessions ending prematurely.

The Tool — PromoClock.co for Real-Time Status

A developer, frustrated by manual timezone math, built promoclock.co entirely with Claude. It’s now updated for this permanent policy. The site automatically detects your timezone and shows:

  • A clear "Peak" or "Off-Peak" status indicator.
  • A live countdown to the next window switch.
  • Browser notifications when the status changes.
  • An .ics calendar file to sync these blocks to Google or Apple Calendar.

Most importantly for developers, it provides a public JSON API endpoint (/api/status) and ready-to-use ZSH/Bash integration snippets.

How To Integrate It With Your Claude Code Workflow

You can pipe the peak status directly into your terminal prompt or use it to conditionally trigger heavy Claude Code sessions. Here’s the quick Bash/ZSH snippet from the site to add to your ~/.zshrc or ~/.bashrc:

# Add to your shell config
CLAUDE_PEAK_STATUS=$(curl -s https://promoclock.co/api/status | jq -r '.peak_status')
echo "Claude Status: $CLAUDE_PEAK_STATUS"

For a more integrated approach, use the API in a pre-session check script:

#!/bin/bash
STATUS=$(curl -s https://promoclock.co/api/status)
PEAK=$(echo $STATUS | jq -r '.peak_status')

if [[ "$PEAK" == "peak" ]]; then
    echo "⚠️  Currently in PEAK hours. Session limits drain faster."
    read -p "Proceed with Claude Code? (y/n): " -n 1 -r
    if [[ ! $REPLY =~ ^[Yy]$ ]]; then
        exit 1
    fi
else
    echo "✅ Off-peak hours. Good time for a long session."
fi

# Launch your Claude Code task
claude code "$@"

This simple check can help you decide whether to tackle a large refactoring job now or schedule it for later.

Alternative: The SuperClaude Browser Extension

Another developer built SuperClaude, a browser extension for claude.ai that provides real-time visual feedback. It shows your usage percentage, a velocity indicator, and predicts when you'll hit your limit at the current burn rate. While not directly for Claude Code, it's useful for understanding the consumption patterns that also affect the models you use via the API and CLI.

Why This Matters Now

This follows Anthropic's recent expansion of Claude Code's Auto Mode and the introduction of long-running capabilities. As Claude Code becomes more agentic and capable of handling extended tasks, managing your session limits efficiently becomes critical to maintaining productivity. Knowing the peak schedule lets you plan intensive coding sessions—like running a full test suite refactor or letting Claude Code autonomously generate a new feature—for off-peak times, maximizing your available context window.

AI Analysis

Claude Code users should immediately integrate a peak-hour check into their workflow. The most actionable step is to add the PromoClock shell snippet to your terminal config. This gives you a one-line status check before starting any significant `claude code` session. For heavy development work, schedule your sessions. Use the provided `.ics` file to block off "Claude Peak Hours" in your calendar. Plan complex, multi-step coding tasks that will consume many messages (like debugging a large module or generating comprehensive tests) for off-peak windows. This is especially crucial when using Claude Code's agentic features, like Auto Mode, which are designed for longer-running tasks. Consider setting a cron job or a simple script that notifies you when the status switches from peak to off-peak, so you can jump into a waiting task. This turns a policy constraint into a manageable workflow optimization.
Enjoyed this article?
Share:

Related Articles

More in Products & Launches

View all