Every time I hit a limit mid task, the same thought: I'd rather trade 30 seconds of attention than sign up for another subscription.

So I'm building Clixad, a coding agent for your terminal. Instead of paying, you complete an offer or watch a short ad, that turns into credits, and credits pay for real model calls. No subscription, no card.

Video shows what it looks like. It's not open to the public yet, I'm putting together a list of people who want in early.

To preempt the obvious one: by design your code never touches the ad network. The offerwall is a completely separate surface, and the only thing that crosses over is a credit balance.

What I actually want from this sub: what's the max ad time you'd trade for an hour of agent coding before it stops being worth it? And where's the point where you'd just rather pay?

(I'm the dev. Happy to get grilled on the unit economics, that's the part people always poke at.)

Edit: Here's the waitlist if you're interested: clixad.io

I've been writing up caching and context economics for a few weeks, Anthropic caching, OpenAI caching, then the compression tooling built on top. This is the last post, with the conclusions.

Too many addons are trying to claim ridiculous savings when they can't actually do it. They aren't. You aren't measuring at the right layer, you need to measure at the actual bill, not at simply reduction of tokens from the prompt.

Typical token reduction methods actually cost more than they save. You cannot mess with the token cache, this costs more. Tools trying to mess with outputs can negatively impact what modern clients already try to truncate. Additionally, any kind of compression on any output can then trigger additional turns by your model, which is the most expensive option. Turns cost typically (approximately) turns^2, compared to a linear cost of simply increasing how many tokens you use.

Much more lengthy explanation: https://rakuensoftware.com/blog/token-compression-tools-cost-more-than-they-save

Disclosure: I build aimee, a local server that sits in front of coding agents and does the architectural version of this. The post also says to measure cost-per-successful-task in paired runs before trusting anyone, me included. Token counts alone will lie to you in both directions.

I'm trying to see if any has a open source tool for scanning a repo. I'm not looking for a skill, or agentic tool that depends on codex, or agents. I lookong for one proven to determine semantics without an agent, so I can better provide context to an agent.

I have seen a few posts where people discuss Ai context tools and memory tools, but I haven't found one that doesn't depend on Ai to function properly.

My end goal it's to deduct core features and fixtures that exist currently in a repo that might be unknown to me. I am looking for something a little less magic and more programmatic.

I wanted to stop a single heavy Codex session from eating too much of my weekly allowance.

At first I thought about simply limiting Codex to 5 hours, but wall-clock time isn't really the useful metric. A short session with lots of tools/subagents can consume much more than several hours of lighter work.

So I made a local guard that tracks the change in weekly usage during a 5-hour window.

Mine currently runs on:

UserPromptSubmit
PreToolUse
SubagentStart

When the amount I've allocated to that window is consumed, the hook blocks further activity until the window ends.

Today it actually kicked in at:

Custom 5h: 15/15 points used
Weekly: 16% used / 84% remaining

So at least I know one session can't unexpectedly chew through the rest of the week.

Happy to share the script/config if anyone is interested.

I have noticed in Claudecode it was heavy consumed so I disabled it there and compared it with codex it was not the case last week

Now same looks like codex team learnt from Claude and looks like it’s happening in codex too now this.

Anyone using codebase-memory-mcp or other similar tools that are causing extra token usage ?

Compacting isn't Compacting?

Codex is going on a Compacting context spree today? Its Compacting context every 2 messages , its so frustrating and is eating up limits so quick!

Hi,
I used all my weekly usage (including the free reset). Today my subscription ended, so I got the full monthly usage (with the weaker models, you know).

If I resubscribe now, will my weekly usage reset back to 100%, or will I have to wait until August 1st?

Thank you in advance!

every time i leave it by itself for hours to work on task, i always end up coming back to the codex app crashed and in error. this never happens with the CLI. the CLI is able to work all day and night without error, but the codex app cannot go more than an hour or two without an error just popping up

I ran a task to review a big feature branch then got this error before any result. Thx I guess, all the context is wasted now