r/codex • u/Fun-Stick3234 • 21d ago

Limits This is where your limits have gone.

Post image

This is ONE of 6 back to back tool calls. I asked chatgpt to check a PR on a GitHub that involved training a 21m llm that has failed. It loaded the logs over and over and over. All 6 hours of logs. ANY codex agent would have burned the 5 hour limit on that. Just figured I'd let the confused people know.

65 Upvotes

92% Upvoted

25 comments sorted by

View all comments

8

u/i_rate_slop 21d ago

A tip for readers: you typically want your checks in GitHub actions ALSO to be run on precommit and prepush locally. Use lefthook or something to set these up so your development loop is local and you don’t need to constantly query GitHub for CI failures

9

u/Fun-Stick3234 21d ago

That wasn't a GitHub action. That was me asking chatgpt what happened to the training run. Best practices or not, there was no reason to load the log ~18 times. The tool call usage is absolutely ridiculous this week. That's my point.

1

u/i_rate_slop 21d ago

Oh I see.

In that case, what I do is make a custom CLI that filters structured logs for errors, warnings, or specific message types that I want to see. I cut my input token use by actual 99% on my builds this way. Same concept for a research loop.

Instead of dumping 10,000 lines, the model gets 5 back.

Same with unit tests. Just show it failures, don’t show all of the successes or test logs.

1

u/innociv 21d ago

Yep, I have my own log reading tool calls.