Unfortunately at my company leads have no insight into employees claude code caps, and no one has ever complained until now. Apparently some people were basically running with insane caps on CC (25k+), if you asked for it you were approved. Which lead to some people doing insane things on CC for no purpose.
Just setting up better SOPs around using AI for coding is going to help them a ton. They can chalk off the sunk cost to a "learning phase", with now being the time to use the lesson learnt to formulate some future-looking standard operating procedures. No need to suddenly go cold-turkey on AI. My 2 cents.
Yeah i was looking there earlier, its just we thankfully mostly have macbooks, but i recently found out new devs are getting the smaller 8gb ram macbooks as well. Which is going to be even more frusturating.
Since my team is mostly remote running LLM on a cluster in the office is not really viable short term.
This is totally going to suck, but here's one option I was just suggested a few mins ago: https://www.reddit.com/r/LocalLLaMA/comments/1th1mqx/comment... For context, I was asking about running anything OpenClaw-friendly on my RTX4060 8GB VRAM. I know yours is a more involved use-case, but there's still some optionality here.
Given our field we cannot really use anything not approved by management. Pretty much if it doesn't leave our machine we can use its just i don't find anything good. We even have some new devs on the macbook neos, and i can't even find anything for them.
I was considering having something run locally within out building but the time when something like that would be avaliable is not near term so i am trying to make the best of what i can do.
Fundamentally one of my biggest gripes with tools like this is that often you are not working with a single repo in anything beyond simple apps.
When I am working with Claude I am often doing it from the root directory of a workspace of dozens of repos. I work with Claude to come up with a plan for implementing a feature and it investigates and plans.That plan often encompasses multiple repositories. Claude then turns large scale plans into smaller issues, or tickets as artifacts.
We’ve felt the same thing and tried to make ctx work well in multi-repo setups.
There are basically two ways to approach it:
- If one repo is primary and the others are mostly reference material, use workspace attachments. That lets the agent work in one repo while still being able to read the others. I do this a lot with dependency/source repos.
- If the work genuinely spans multiple repos, just initialize the workspace at the parent directory that contains all of them. The harness still sees the same filesystem layout it normally would, so Claude/Codex/etc. can plan and work across repos the same way.
The main caveat is that some features are naturally more repo-specific. Merge queue is the obvious example, since landing and replay are much cleaner when there is one target repo/branch model.
Imo I found opus 4.6 to be a pretty big step back. Our usage has skyrocketed since 4.6 has come out and the workload has not really changed.
However I can honestly say anthropic is pretty terrible about support, to even billing. My org has a large enterprise contract with anthropic and we have been hitting endless rate limits across the entire org. They have never once responded to our issues, or we get the same generic AI response.
So odds of them addressing issues or responding to people feels low.
The company I work for has a pretty bad bounty system (basically a security@corp email). We have a demo system and a public API with docs. We get around 100 or more emails a day now. Most of it is slop, scams, or my new favourite AI security companies sending us an AI generated pentest un prompted filled with false positives, untrue things, etc. It has become completely useless so no one looks at it.
I had a sales rep even call me up basically trying to book a 3 hour session to review the AI findings unprompted. When I looked at the nearly 250 page report, and saw a critical IIS bug for Windows server (doesn't exist) existing at a scanned IP address of 5xx.x.x.x (yes an impossible IP) publically available in AWS (we exclusively use gcp) I said some very choice words.
I have a coworker who is basically doing this right now he leads our team and is second place overall. Regularly runs opus in parallel he alone is burning through 1k worth of credits a day.
Frankly Claude code is painfully slow. To the point I get frustrated.
On large codebases I often find it taking 20+ minutes to do basic things like writing tests.
Way too often people are like it takes 2 minutes for it to do a full pr. Yeah how big is the code base actually.
I also have a coworker who is about 10x more then everyone else. Burning through credits yet he is one of the lowest performers.{closing in on around 1k worth of credits a day now).
$1,000.00 of credits per-day?? $200,000 per year? Those are bonkers numbers for someone not performing at a high level (on-top of their salary). Do you know what they are doing?
Yup. The way he works is all tasks he is issued in a sprint he just fires them through opus in parallel hoping to get a hit on Claude magically solving the ticket having them constantly be iterated on them. He doesnt even try using proper having plans be created.
Often time tickets get fleshed out or requirements change. He just throws everything out and reshoves it into Claude.
