Real AI agent use cases, with sources and setup prompts

Measure how much of your usage limit resuming a long session costs

A developer tested resuming long sessions in Claude Code with Opus 5.5 and in Codex with GPT-6.1 Sol, both on medium effort, and watched the usage meters. Resuming a long Claude Code session took a big chunk of the 5-hour limit, while codex resume did not show the same jump.

$17/mo1 hourBeginnerSource linked

Source

@Im_IrushiK on X · 2026-10-15

Written in our own words. Credit to the original author. Link checked 2026-10-21.

What they did

A developer tested resuming long sessions in Claude Code with Opus 5.5 and in Codex with GPT-6.1 Sol, both on medium effort, and watched the usage meters. Resuming a long Claude Code session took a big chunk of the 5-hour limit, while codex resume did not show the same jump.

Result (as claimed)

In his test a single Claude Code resume used about 14% of the 5-hour usage window.

Tools they used

Claude CodeOpenAI CodexClaude Opus 5.5GPT-6.1 Sol

Cost: Claude Code: from $17/mo; OpenAI Codex: free plan, paid from $8/mo; Claude Opus 5.5: from $4 in / $20 out per 1M tokens; GPT-6.1 Sol: from $2 in / $10 out per 1M tokens.

Set it up

  1. Pick a contained repo or task

    Start on a branch or side project where mistakes are cheap.

  2. Install and configure

    Set up Claude Code, OpenAI Codex, Claude Opus 5.5, GPT-6.1 Sol. Read what it can run on your machine and limit permissions where possible.

  3. Run it on a real task

    Give it a well-scoped issue and let it work. Review the diff like any pull request.

  4. Add guardrails

    Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.

Copy the full setup prompt

Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.

You are helping me set up this AI use case end to end in Claude Code.

Goal: Measure how much of your usage limit resuming a long session costs
What the original author did: A developer tested resuming long sessions in Claude Code with Opus 5.5 and in Codex with GPT-6.1 Sol, both on medium effort, and watched the usage meters. Resuming a long Claude Code session took a big chunk of the 5-hour limit, while codex resume did not show the same jump.
Reported result (as claimed by the author): In his test a single Claude Code resume used about 14% of the 5-hour usage window.
Source: https://x.com/Im_IrushiK/status/2110733197462151650
Tools they used: Claude Code, OpenAI Codex, Claude Opus 5.5, GPT-6.1 Sol
Category: Dev & ops

Please:
1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like).
2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure.
3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data.
4. Finish with a checklist to run it again next time.

The Daily 5

Get five new use cases tomorrow morning

Free. Real sources. Unsubscribe any time.

Guides for this use case

How to save, share and resume coding agent sessions · How to vibe code an app with Claude Code · How to use Claude Code and Codex together · How to cut AI coding agent costs and token use

Related use cases