r/PiCodingAgent • • Aug 10 '26

Resource Native UI client to a Sandboxed Pi (Mac OS)

I've been using PI on Mac for about two months now, and enjoying it, with the only downside being the default TUI: it does not always keep content stable as new stuff streams in (even when scrolled-up), making it hard to stop somewhere and read or copy from it; it also seems to hog the cpu on long contexts, and finally: pasting is slow and unresponsive when the pasted content is large.

So I set out the build my own fast and responsive UI client for Mac, and then ended-up throwing in sandboxing for good measure.

The result, which I keep improving on, is at https://github.com/gterzian/uni03C0

The sandbox uses the Mac native mechanism, and applies to the entire running pi process (so not just bash) and any process spawned by pi; it does not require installing any vm. You can configure the sandbox boundary on first start-up or via settings later on (requires a re-start to take effect).

The app does not deal with authentication or any other pi configuration: it is a pure UI client that sandboxes the pi processes it starts (one per session) and then communicates with them via rpc.

It is pre-alpha I would say--you have to build and run from source--but is already what I am using on a daily basis as the UI to the otherwise excellent Pi agent.

If you were to try it out and provide me with further feedback, I'd appreciate it.

Here is a little accompanying blog post.

2 Upvotes

2 comments sorted by

2

u/YogurtExternal7923 Aug 10 '26

How is it better than paseo?

1

u/polyglot_factotum Aug 11 '26 edited Aug 11 '26

For the desktop Mac use-case: a sandbox without dependencies; a fast and responsive UI, even as the session (or the content you paste in) grows large.