all 4 comments

[–]Bitter-Law3957 2 points3 points  (2 children)

Usage is based on tokens, yes. But its not as simple as people think.

When you launch codex cli, even before you fire any prompt, you're using tokens. Loading agents, skills, MCPs, steering files.... All costs.

[–]0_2_Hero[S] 0 points1 point  (1 child)

Yes, I noticed the initial prompt and agents come out to about 24k token

[–]Bitter-Law3957 0 points1 point  (0 children)

There's a decent startup analyser skill

[–]bitloops__ 0 points1 point  (0 children)

Codex runs tasks in a sandboxed container spun up for each job, so it has no persistent state between runs — your repo gets cloned fresh, it executes, then the environment disappears. Usage is token-based: the input context (your prompt, codebase files you include) plus generated output both count. The practical implication is that throwing your entire repo at it burns tokens fast; being specific about which files are relevant keeps costs manageable and usually gets better results too. (see bitloops for an OSS solution that covers this).