PiG is a direct port of the amazing Pi agent harness as one Go binary for macOS, Linux and Windows (Windows in preview). Node.js only comes in if you run TypeScript extensions. Pi's extensions run unchanged; write new ones in Go, Rust or Python and /reload them live. It is a direct port of Pi's its agent loop, terminal UI, sessions, providers, and extension system, shipped as one static Go binary with no libc dependency.

Some Go-specific bits that might interest this sub:

* Extensions in Go can be *fused* into a single binary and talk to the host over in-memory pipes instead of sockets; other languages run as supervised subprocesses over local sockets.
* The TUI renders differentially; width handling was ported from Pi's own algorithm and checked with a differential test against Pi's code over \~1.5M cases: [tui/widthx/pi\_width\_diff\_test.go](https://github.com/MichaelKinsy/PiG/blob/main/tui/widthx/pi_width_diff_test.go).
* Behavior is checked against Pi in real terminals (tmux-driven scenarios that compare screens).
* `go install` [`github.com/MichaelKinsy/PiG/cmd/pig@latest`](http://github.com/MichaelKinsy/PiG/cmd/pig@latest) works; so do a curl installer and `npm i -g` u/pi-in-go`/pig` (it installs the prebuilt native binary for your platform).

Measured startup is about 21 ms vs about 300 ms median, and about a quarter of the peak memory (method in the blog).

Disclosure: agents wrote much of the port. Tests, side-by-side comparisons against Pi, and a person reading the diff decide what ships.  
  
Repo: [https://github.com/MichaelKinsy/PiG](https://github.com/MichaelKinsy/PiG) 

Blog: [https://developer.hpe.com/blog/meet-pig-pi-in-go-a-port-that-plans-on-keeping-up/](https://developer.hpe.com/blog/meet-pig-pi-in-go-a-port-that-plans-on-keeping-up/) 

Upstream Pi: [https://github.com/earendil-works/pi](https://github.com/earendil-works/pi)

Happy to answer questions about the port, the extension host, or keeping up with upstream. Feedback on this is appreciated and contributions are welcome.

Thank you to r/HPE for covering writing the blog and contributing PiG to Open Source and special thank you to the Pi team of course at [https://earendil.com](https://earendil.com)



Meet PiG: The Pi coding harness that is yours but in Go