Rewriting Prime Agent in Rust
primeintellect.ai
[hidden]
Naturally then there isn't source material for "we rewrote yet another slow scripting project into Go/Rust/Zig/C/C++/..." blog posts.
[2 comments hidden]
I don’t see many people talk about Prime Agent, I always wondered if it could just be a Pi extension cause it seems to be a subagent orchestration agent.
[hidden]
Very happy user. Loved it with deepseek-v4-flash, although I've moved on because newer models are so compelling.
I just get good results from it; I think it's the python requirement.
It has been very good with sub-agents, and also finding old context, for a long time. And had backgrounded agents that you can run from one instance without herdr. Herdr is kinda redundant (better UI than PA though).
I see nobody else talk about it. It's so little talk that when I mention it on X, the devs comment on my posts sometimes.
[2 comments hidden]
Curious how this could be applied to greenfield coding rather than just making a copy in a new language or performance optimizing.
[2 comments hidden]
[2 comments hidden]
[hidden]
For Anthropic's reported benchmark numbers for Sonnet 5.5, when running terminal-bench 4.0, they had a comparison between $0.10 and $0.20 cache read for total task cost. That 50% cost reduction resulted in a 20.9-26.2% total cost reduction. Pretty specific though... single benchmark, model, harness, and provider. Cache reads make up ~42-52% of the total cost at the standard $0.20 price.
[3 comments hidden]
Now there is no excuses to not use Rust and it just shows in raw performance alone.
[2 comments hidden]
Eventually AIs will generate Assembly code directly anyway, no need for intermediate 3 GL languages.
[hidden]
Combine that with the fact that, unlike other code generators, LLM output can't as a rule be reliably reproduced from the original input in the future, sounds like a recipe for unpredictable long-term costs and regular regressions.
AbuAssar[hidden]
very nice outcome of this port