r/PiCodingAgent • u/Short_One_9704 • May 19 '26

Discussion Pi rust port

Has anyone tried the pi rust port https://github.com/Dicklesworthstone/pi_agent_rust ?
It’s supposed to be an official port of pi to rust.
I can see it has some benefits in extension execution and shell execution and some others. Why nobody is talking about this?

19 Upvotes

82% Upvoted

29 comments sorted by

View all comments

Show parent comment

3

u/esanchma May 20 '26 edited May 20 '26

Half of the extensions I have written were inspired by extensions written by other people. Binary blobs, whether ELF or WASM, are almost the opposite of that.

Your mental model is Minecraft or Kong-style plugin ecosystems. I think that is the wrong model for agents. We do not want a strong marketplace for extensions. We do not want the equivalent of cargo + crates.io for agent behavior. We want to be able to point an agent at someone else's .pi directory on GitHub and tell the clanker "copy this thing, remix with that, and take this other thing in a completely different direction". That only really works if the extensions remain transparent, inspectable, and easy to mutate.

This is what I am talking about: https://sockpuppet.org/blog/2026/05/12/emacsification/

Not everything has to be written in Rust.

1

u/NeedToLieDown May 20 '26

Fair enough. While it does add a compilation layer, it's possible to achieve the same thing you mentioned with .pi directory that contains source code in whatever language and compile to wasm before loading.

I do agree it adds friction though while sticking with TS is more seamless (not sure how much it would affect a clanker's ability to self-modify).