monty-go: Pure-Go wrapper for Pydantic's Monty Python Interpreter

Is this Python in Rust in WASM in Go?

The Monty name was a perfect choice, Yakety Sax was playing in the distance as I read through the readme.

Jokes aside, I do love seeing WASM as a bridge to enable cool stuff like this.

Monty itself seems much more interesting than a Go wrapper for a WASM runtime running the Rust implementation that runs the Python code. There was a big discussion about it 6 months ago: https://news.ycombinator.com/item?id=46918254

I've implemented and shipped a version of this that uses full CPython with a custom filesystem implementation in userspace. I think this is a bit more interesting if a bit more low level.

Funny -- I just built a pure go wrapper myself because this one is super out of date!

https://github.com/CamdenClark/monty-go

It implements the new subprocess model for spawning Monty VMs that help keep your main thread isolated if one of the VMs crashes.

Because Monty is packaged as a binary now, you don't need to do the WASM embedding stuff, you just need to make sure you have the binary. (Similar to how you would run playwright in Go, for example)

1. Control and guardrails. I want agent-authored code to be able to express itself in code but I want to own the external tools that are available to the agent.

2. Suspension and resumption. Monty's VM state is fully serializable so I can run the VM until it gets to a tool call and persist the VM state. I could resume it days later with the results of the tool call with no issues. Doing that guaranteed with CPython is really tricky (tools like Pickle can get you close but if you have open sockets or other weird stuff you're in a world of hurt).