Check your Claude and Codex plan limits before a long agent job

In Claude Code, /usage shows your plan limits; in Codex, /status shows the session’s token usage and context left. ACTVT reads your Claude and Codex plan usage from the provider: how much of the 5-hour session window and the weekly window you’ve used, and when each one resets. Agents can ask for it over MCP with the agent_usage_limits tool before they start a long job, and you can see the same limits in ACTVT’s Overview. Plan usage meters are part of the Premium tier.

0:484 chapters

Step by step

  1. 0:00Ask before you start

    I’ve got a two-hour job to run, and my plan has usage limits. So before I start, I ask Claude Code whether it’ll fit.

  2. 0:15Claude checks the plan

    Claude asks ACTVT how much of the plan is used, and it’s fine. 8% of the 5-hour window is used and 40% of the week. Each window has its reset time, which comes from the provider.

  3. 0:26The same numbers in ACTVT

    You can see the same windows in ACTVT’s Overview. There are Claude’s session and weekly limits with when they reset, Codex’s weekly window next to them, and which plan each one is on.

  4. 0:42Spend at API rates

    ACTVT works out spend at API rates. If you’re on a subscription, that isn’t what you actually pay, and ACTVT says so on the card.

Questions

Does it show the 5-hour and weekly windows?
Yes, with when each resets.
Can an agent check before it starts?
Yes, with the agent_usage_limits MCP tool.

Try it on your own agents

ACTVT is free to start, and reads the session files Claude Code, Codex CLI and Pi already write. Nothing to configure.