I'm using it for large scale security work so it needs to do things precisely. For example, I monitor about 3500 libraries across npm/crates/pypi through an automated (non-LLM) framework.

Assess this 2 MB diff for a low level dependency version bump line by line, then trace its usage end-to-end through a spaghetti architecture of 800 other 3rd party dependencies into the bespoke code of this repo, and while you're at it, cluster in functional chunks, explain what the change does, scan for injection of malware, decode every base64/hex/eval() and so on and report what it does. Prepare scopes with exact source, file, line ranges to hand off to hunters.

Then step 2, which is what I'd normally give to a framework of mixed kimi/glm agents/subagents: take this code stub, with this and that integration path, identify all areas susceptible to bugs according to <list> throughout the whole path, fire subagents to build harnesses, fuzz the fuck out of it, for each candidate hand it off to a critic. If the critic agrees, write a bug report for the candidate, submit to <private bug server>, report to the issue with all drafted candidate reports, and list all candidates that were not confirmed by the critic.

Then step 3, I read everything, which is why I need it to not be retarded slop.

That's one use-case. Others are either more reactive (CVE got published, assess which code uses it), release reviews (for graphene or lnd or the android apps I run), explain every line in PR xyz... and so on. Everything runs in private tho, no github except to fetch package sources.