Repository navigation
token impact #749
bashfulrobot
started this conversation in
General
Replies: 3 comments 1 reply
|
I think I may have answered my own question here. I just tried it out with Claude and blew through my daily allotment in a relatively short time. Granted, I'm only on the pro plan at the moment. Definitely drives better outputs, but just goes to town on the token and limits. |
0 replies
|
Maybe the thing to do here is transition the conversation to which models to use for what, to optimize token usage. |
0 replies
|
Yes, getting the agent to be more accurate tends to use more tokens, but I feel like sometimes these kinds of questions tend to miss a few other things:
My personal view is that not all token usage is the same. Burning tokens to ensure correctness alignment, etc, is well worth it compared to burning tokens to get inconsistent outputs. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi there, I've been testing OpenSpec with success on Codex using the 2x entitlements I currently have until April. I'm just curious what others have seen in terms of token consumption using OpenSpec over time. And given how OpenSpec is architected, do archive items ever come into play for token consumption? Or any of the OpenSpec files for that fact. My assumption is that the OpenSpec files don't come into any token consumption unless you call the prompt. And even then, I may assume that anything archived is no longer in scope.
Is this a fair understanding?
Cheers!
All reactions