4 ms·
How you burn 300 requests in a day? From my Copilot usage Opus consumes surprisingly few requests to do a lot of stuff. It isn’t paying by token but instead by
by nextlevelwizard 5mo ago
How you burn 300 requests in a day? From my Copilot usage Opus consumes surprisingly few requests to do a lot of stuff. It isn’t paying by token but instead by prompt or something.
- coredog64 5mo agoOpus 4.7 has a 7.5x multiplier when it's used from Copilot. Falling back to 4.6 it's only 3.5x
- antod 5mo agoIt recently went up to 15x in our org.
- theblazehen 5mo ago300 prompts in a day isn't that unreasonable to achieve on a heavy day? And Opus has a significant multiplier as well
- antod 5mo agoYeah, thats 20 Opus 4.7 prompts.
- nextlevelwizard 5mo agoThat is a lot of prompts. What kind of prompts do you usually give? Mine are usually giving specification and telling Claude to implement some part of it, referring to existing code base, writing unittests and running e2e until it passes. This can easily take 4-5 hours. Then again, I have seen colleagues prompt “are you sure?” And other nonsense like that
- theblazehen 5mo agoI think we use it differently then, I tend to go heavy on the back and forth. For speccing things out, I have a back-and-forth with the grill-me skill, break things down into tickets, as well as kicking off subagents. That said, I significantly overestimated the number of human messages I send. My daily 90th percentile wrt number of prompts sent is sitting at 160 queries / day and average at 97 queries / day. Ran an analysis of my last 2000 messages, with the following breakdown Task delegation / execution: 23% Investigation / diagnosis / “what’s going on?”: 21% Planning / architecture / brainstorming: 15% Testing / verification / release ops: 10% Review / cleanup / quality control: 9% Course-correction / constraints / preferences: 8% Agent / ticket / workflow orchestration: 6% Providing context / evidence / pasted material: 4% Social reactions / acknowledgements / vibes: 2% Other: 2%
- nextlevelwizard 5mo agoYeah that’s not good for current Copilot usage since you are paying per request not by token
- theblazehen 5mo agoYeah, copilot is only my backup - Codex and Claude are my primary, where it's per-token. Just looked up my user prompt count from my opencode db
- devmor 5mo agoIf you are using subagents for asynchronous work, you can burn through 300 requests in a workday easily.
- saratogacx 5mo agoCopilot didn't charge for subagents. You could do an insane amount of work with dozens of subagents with a single request and a deep enough prompt to kick it off. I setup entire virtual teams (Dev, QA, product, reviewers etc with the initiating model just acting as the agent manager to keep it's context minimal) to one-shot some stuff and it kept churning and making progress. Those days are just about over with the change to token pricing but for a time....
- hrpulsar 5mo ago[flagged]
- oytis 5mo agoI guess you need automation for that. Run claude with cron to find fulnerabilities, suggest and implement improvements, automatically dig through backlog
- nextlevelwizard 5mo agoHope people doing those kinds of automations are paid to waste prompts and tokens. Any cron based LLM run is just stupid waste
- ddtaylor 5mo agoCopilot charges a 27X multiplier on Opus 4.7 prompts.
- humanfromearth9 5mo agoReview-fix rounds after generation of text or code, until convergence to a solution that doesn't need more improvements.
- nextlevelwizard 5mo agoYou are prompting the same model to review what it just did?