r/PiGCodingAgent • u/WimbashBagel • 14d ago
Are you using a GUI with PiG, if so which? (ADE,IDE, etc)
Lots of options.
r/PiGCodingAgent • u/WimbashBagel • 14d ago
Lots of options.
r/PiGCodingAgent • u/Educational-Yak8793 • 21d ago
r/PiGCodingAgent • u/Agreeable-Market-692 • 22d ago
Subreddits are not enough to make a community. When do we get to talk turkey and grind away at node's undue dominance over AI tooling???
Taking up space in Pi-land feels counterproductive, so we diaspora need a forum...beyond the sub here.
r/PiGCodingAgent • u/GiovaSan • 24d ago
Hello,
I've been shopping around for Pi alternatives and PiG checks all of my boxes! I want to jump to it but am unsure regarding extensions.
PiG has Piglets, which should be extensions but in Go and better, while also supporting official Pi ones.
My main question is whether I should use official Node.js ones, likely loosing the benefits of using Go as base language, or convert all of them to Piglet. Also, how can someone check whether a Piglet provide functionalities like the official ones? By cross-checking the official repository?
After that I can probably fully migrate to PiG for good 😁
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 22 '26
Pi in Go now 0.5.2 follows Pi 1.4.0, which came out yesterday, and it's mostly a fix release driven by issues people filed.
The security part first. Node.js shipped security releases on 2026-10-21, including a Brotli decoder bug that allows remote code execution and two TLS hostname check bypasses. PiG doesn't embed Node, so the Node that runs your TypeScript extensions is the one you installed, and you should update it to 22.23.4, 24.22.1 or 26.12.1. PiG's own CI and tooling moved to those versions. Separately, the private keys of eight eMudhra intermediate CAs turned out to be recoverable from their public certificates (Mozilla bug 2083449), so PiG's own TLS connections now refuse any chain through them, including the Sectigo cross-signed paths.
The rest is Pi 1.4.0 parity and fixes. MCP registration and CodeMode sandbox construction were quadratic in the number of tools, and a 100,000 tool catalog now builds its sandbox in 40 ms instead of 22 seconds. Parallel edits to one file through a hard link or a case alias could lose a change, and they're now ordered. That goes beyond Pi on purpose, since Pi has the same lost edit for hard links. There are also fixes for /scoped-models with Ctrl+P, /reload with CodeMode enabled, pig --list-models showing models Pi drops, and Durable stores written by pi-durable 1.3.0.
As always shout out the herd 🐷 🐷 🐷
Release notes: https://github.com/MichaelKinsy/PiG/releases/tag/v0.5.2
Install: go install github.com/MichaelKinsy/PiG/cmd/pig@latest or npm i -g u/pi-in-go/pig
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 19 '26
**edit: forgive the "ligher" typo, was a little too excited to press post :)
A couple of weeks ago I posted that 0.5.0 was en route and that I thought you would like it. It is out now 🐷 Here is what landed from that list, plus a few things that grew along the way.
Piglets. Piglet build can strip features out of the base harness or out of a prior Piglet, and a stripped Piglet can be the base for the next one. Piglets keep getting core updates for the parts they kept. pig-tern shipped as planned. pig-core is a lean base: it keeps only read, bash, edit and write.
Parity and porting. The port-map ledger is maintained mechanically now, and every row is closed. PiG follows Pi 1.3.0 up to Pi commit 1402973a, and every one of Pi's semantic interfaces is covered and held by a zero-gap gate in CI.
Evals. The eval and benchmark tooling became buffon, an open benchmark arena for the whole Pi community. The numbers below come from it, and you can rerun them.
Quality of life. pig extension upgrade rewrites older Go extensions for the new SDK, plus a lot of great contributions from the herd.
Release notes: https://github.com/MichaelKinsy/PiG/releases/tag/v0.5.0
Blog post with the full tables: https://pi-in-go.dev/blog/pig-0-5-0/
Repo: https://github.com/MichaelKinsy/PiG
Piglets (Pigpen): https://github.com/MichaelKinsy/pigpen
Buffon: https://github.com/MichaelKinsy/buffon
Performance
All numbers are median CPU ms from buffon on one machine, on the 0.5.0 release candidate. Lower is better.
| Task | PiG 0.5.0 | PiG 0.4.1 | Pi-Bolt | Pi (Node) |
|---|---|---|---|---|
--version | 5 | 18 | 11 | 282 |
| One prompt | 16 | 64 | 44 | 424 |
| One prompt with tools | 29 | 119 | 56 | 518 |
| RPC session | 71 | 438 | 108 | 675 |
| Interactive start | 61 | 145 | 55 | 536 |
| Resume a long session | 69 | 137 | 50 | 443 |
| Streaming a long answer (TUI) | 403 | 2,451 | 925 | 2,850 |
| One prompt, 10 TypeScript extensions | 934 | 2,191 | 109 | 676 |
| RPC, 10 TypeScript extensions | 2,016 | 9,430 | 194 | 950 |
0.5.0 beats 0.4.1 on every row. Without extensions it beats Pi on every row. Pi-Bolt is a little ahead on interactive start and long-session resume.
The extension rows are a real loss. PiG starts a separate Node host for TypeScript extensions, and that adds a fixed cost. So I also ran the same extensions ported to Go and fused into a Piglet. This is my own run, not buffon, and it is labelled provisional. The Go and TypeScript extensions were checked to produce the same commands, tools, results and messages.
| Scenario | TS extensions | Go extensions in a Piglet | No extensions |
|---|---|---|---|
| Print, 10 extensions | 941 | 67 | 16 |
| RPC, 10 extensions | 2,004 | 521 | 70 |
In print mode the Go Piglet is ahead of Pi-Bolt (67 against 109). In RPC mode Pi-Bolt is still ahead (194 against 521). Scripts and raw data are attached to the release as go-ext-comparison.tar.gz.
Most of the speed came from removing a few patterns. A streamed file write used to re-highlight the whole file for every new piece, and tool-call arguments were reparsed from the start on every token, which made long streams quadratic. Now PiG keeps state and processes only the new part. Every speed-up has to keep output byte-identical to Pi.
Piglets and binary size
Every built-in part of PiG is now a slot. A Piglet keeps a part, replaces it with Go code, or strips it so it leaves the binary. Stock PiG is the normal pig binary with everything built in. pig-core is a Piglet that keeps only read, bash, edit and write.
| Binary | Size |
|---|---|
| Stock PiG 0.5.0 | 70.3 MB |
| Go extensions only (TypeScript, Python and Rust runtimes stripped) | 61.4 MB |
| pig-core | 39.4 MB |
Sizes are from linux/amd64 builds of the release commit. Slots can also replace a part: pig-tern fills the frontend slot so the same PiG draws natively in the Tern terminal.
Durable
Durable has come up a lot here, so here is how I think about it. Pi Durable is a stateful agent whose state lives on a server, separate from the client (TUI, web UI, mobile) and from the chat history. A session keeps going when a client disconnects, and any client can attach to it. PiG runs Durable natively in Go. In 0.5.0 its cost no longer grows with your history, and a session finds its next wake without walking every live task. The Cloudflare Durable host follows Pi 1.3.0 and runs its suite in CI. https://pi-in-go.dev/blog/pig-0-5-0/
buffon
buffon is a benchmark arena I made for the Pi community. Every harness gets the same tasks and the same Pi extensions on the same machine. You can rerun it, point it at your own tools, or add to it. It builds on the open work of Pi, Pi-Bolt, durable-bench and everyone who publishes their evals.
Try it
go install github.com/MichaelKinsy/PiG/cmd/pig@latest
Custom models in models.json now need an api on the model or its provider, as in Pi. Go SDK users can run pig extension upgrade to rewrite older extensions.
Not done yet
TypeScript extensions are slower than in Pi and Pi-Bolt, as above. The TinyGo Durable build used for Cloudflare starts cold slower than Pi's, and the normal pig binary does not use it. The first code-mode use in a process costs a few ms more, and the OAuth credential store is not available to Node extensions yet.
PiG is MIT licensed and free, with no hosted or paid tier holding anything back. Big thanks to the Pi team, to Pi-Bolt for its open benchmark suite, to durable-bench, to everyone who posts their evals in the open, and to the herd for the contributions and issues.🐷
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 19 '26
r/PiGCodingAgent • u/opensecai • Oct 12 '26
r/PiGCodingAgent • u/async-monkey • Oct 11 '26
What are some of the subagent patterns being used for development and Pig?
I've used https://github.com/nicobailon/pi-subagents in my pi workflow and it's been great - relatively issue free. I understand that I can use this extension with Pig, but I've noticed that background agents error out - and I'm wondering if people are still using the same subagent extensions, some are using the refactored pigpen subagents piglet (github.com/MichaelKinsy/pigpen/tree/main/components/subagents#readme)?
Just curious.
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 09 '26
Quick update since 0.5.0 has been taking a bit: it's close, and it's the biggest release since launch 🐷
Piglets: piglet build can now strip features out of the base harness or a prior piglet. A stripped piglet becomes its own base that can still take extensions, and piglets built on top of it can strip what they want, without touching the upstream piglet's core design or forking the whole project. This is the derivative-harness idea I've been going on about since piglets started. Piglets also get piglet update, so the components that make one up keep getting core updates for the features they kept. The first piglets planned on this are pi-pig, pi-pig-pre-1.0 and pig-tern. Think pig with built-in mcp/code-mode removed from the binary like pre-1.0, still getting every core update, and you can add mcp back as an extension if you want it. Same for dropping the extension SDK languages you don't use (the original pi-pig idea: pig that only runs pi extensions).
Parity and porting: this is the biggest maintenance lift since release. The port-map ledger is now maintained mechanically, so gap analysis and future Pi updates are much easier to keep up with, and it's down to its last few rows for 0.5.0. Behaviour gets checked mechanically too now: cross-SDK wiring checks plus tests run against Pi itself, which already caught dozens of corner cases, including a few bugs we'd ported from upstream.
Evals: the eval/benchmark tooling is ported, plus new evals comparing pig-durable and pig performance, so there's reproducible data behind the port's health.
QoL: an opt-in auto-upgrade (and a prompt) for extension SDKs that don't match your pig version instead of erroring out, and lots of great contributions from the herd 🐷🐷
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 07 '26
Starting this thread as I've spent the last few days working in parallel on our evals and other suites for the repository and realized I should open a thread up for people to request or post their evals.
Just want this to be a place we can start to collect data on what is and what isn't working with the green pig.
It can be literally anything you think of and want to suggest don't feel you have to have a full research report done to post here. Suggestions are extremely valuable as I'm wanting to collect a list of items for me to plow through as well for the community.
Thanks all :) 🐷
r/PiGCodingAgent • u/Conflict-Mother • Oct 07 '26
It is a tutorial on how to write extensions for PiG. It focuses on building the right concepts and an overview of how it works — the necessary foundation for driving a code agent to turn your idea into a good PiG extension.
For a concrete running example, the tutorial builds a small feature: a /prefer command that lets you pin which real service provider serves your session. OpenRouter is a router in front of many real service providers — the same model can be hosted by several of them. An OpenRouter spec can end with a provider suffix:
openrouter/deepseek-v4.1-flash:deepseek
^model ^only this real provider
The trailing :deepseek tells OpenRouter: serve this request from DeepSeek's infrastructure only, never hand it to another host. The extension's job is to let you set that preference from inside the terminal, in one command.
The tutorial walks the full loop, from editor to the little program can spot running on machine:
author → install (local or npm) → first session → the process you can see → (optionally) fuse it into a binary.
If you would like to build a high level concept on PiG's extension, read it here: https://www.liyu1981.xyz/article/write-extension-for-pig
r/PiGCodingAgent • u/Conflict-Mother • Oct 06 '26

After seen my Pi agent occupied about 1G memory of a 40% of 1M context session, I started to search about faithful implementation of Pi with less memory consumption. I found several, and finally come to few choices: PiG, pi_agent_rust and fx. PiG is very faithful, right out of the box it works; pi_agent_rust, unfortunately it just breaks my terminal and I do not even it works or not, and fx is actually not a Pi implementation, just because it is from vercel and it seems small (bin <6MB).
After a while of usage, I have discovered, PiG is better than what I have expected, especially in memory consumption. Previously Pi original is really good, but with recent updates, it seems consume more and more, such as mentioned 1G memory of a 40% of 1M context session, large consumption is one thing, the side effect of that is it starts to slow down after mem consumption climbed. PiG as a golang app, with a much easier deployment/upgrade experience, also is much steady in mem consumption. And actually I found in real usage, such as around 15% of 1M context session, the PiG actually consume on par memory to fx, which is written in Zig and manual memory management instead of GC in PiG.
So great work! and I believe I will use PiG as my daily agent harness from now on :)
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 05 '26
PiG 0.4.1 is out. It follows Pi 1.0.3 (1.0.4 coming) and fixes every bug reported since 0.4.0:
Sign in with ChatGPT works again, and cancelling a login is clean
Extension input handlers can open dialogs without freezing the terminal
Extension exec no longer hangs on background processes
Windows bash keeps every line of output
Tool renderers in every SDK, durable runtime file watching, Azure Chat Completions, all five llama.cpp thinking levels
Breaking (from Pi 1.0.3): the Azure provider is now azure; the release notes say what to rename
Update: pig update, npm i -g u/pi-in-go/pig, or curl -fsSL https://pi-in-go.dev/install.sh | sh
Release notes: https://github.com/MichaelKinsy/PiG/releases/tag/v0.4.1
Pigpen is public too: https://github.com/MichaelKinsy/pigpen
It has 11 Piglets with their Packages, all in Go: Zed and VS Code bridges, agent-to-agent, a guardrails warden, herdr status, games, and a porter that turns Pi extensions into Go. Tern is coming soon. Piglets can build on other Piglets, and "pig strip" and more Piglet features are on the way. PRs welcome.
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 03 '26
It's finally here, thanks for all the patience and support for this release and project so far :)
PiG is a separate Go implementation of Pi, the coding agent, shipped as one native binary. 🐷
0.4.0 follows Pi 1.0.0 (0.3.1 followed 0.87.1). New since 0.3.1:
Pi 1.0.0's durable runtime, in Go: checkpointed sessions and tasks that resume after a crash, tools that rerun only when replay-safe, exactly-once submissions, forks and subagents. Ported with Pi's own tests.
Code mode is built in and needs no Node (QuickJS on wazero, the same wasm Pi ships). Shorter prompt, recovery hints in errors, and scripts can generate images.
MCP: a native client in print, JSON, RPC and interactive mode, with OAuth hardening (authorization server metadata URL, RFC 9207 iss checks, per-server credentials, step-up that keeps scopes).
Termux on Android (arm64): curl -fsSL https://pi-in-go.dev/install.sh | sh and npm install -g u/pi-in-go/pig both work, using a cgo build against Android's libc.
pig piglet build without a checkout: a release binary fetches its own exact source through the Go module proxy (checked by GOSUMDB), or builds in Podman/Docker when Go isn't installed.
TUI: fullscreen by default; quietStartup: "header"; Radius in /login; a copy-code method for Anthropic.
PiG's own look: a pixel pig header, /sprite with 15 pigs, an API for extensions to add their own, and a first-run setup that includes a sprite pick.
The Pi 1.0.0 extension API in the Node, Go, Python and Rust SDKs. Some SDK signatures change; the release notes list them.
Windows remains in preview.
Also 0.4.1, which follows Pi 1.0.1, is already underway as well :)
Demo: first-run setup, then a classifier model plays two MCP games live through code mode.
Upgrade with pig update or npm install -g u/pi-in-go/[email protected].
Release notes: https://github.com/MichaelKinsy/PiG/releases/tag/v0.4.0
r/PiGCodingAgent • u/PebcakFubar • Oct 03 '26
Have ported over the Pi extension to a PiG Go extension to show agent state in a herdr pane.
https://github.com/ashLatham/pig-herdr-agent-state
p.s. nice work on PiG, didn't like how Pi started feeling bloated with opinionated features. As of today PiG will be my day-to-day harness.
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 03 '26
Super cool post done on PiG here by DIY Smart Code - https://youtu.be/Wzpz7rQawNo?si=MURL207l7AHCmqrI
r/PiGCodingAgent • u/Educational-Yak8793 • Oct 02 '26
Hey guys!
Thanks for the patience with all the pi features dropping recently! Just wanted to give an update we’re almost to full parity with 1.0 including durable pig, mcp/codemode, and more. I was planning to cut the release today but I had to go to a wedding before I could launch. Expect something late tonight early tomorrow also if anyone wants to run the release branch from source fee free :)
Thanks all! 🐷
r/PiGCodingAgent • u/Educational-Yak8793 • Sep 30 '26
Quick heads-up for anyone who installed PiG (Pi in Go) early.
- 0.3.0 and later: PiG checks for new releases when it starts and shows "Update Available … Run pig update", just like Pi. pig update downloads the new binary, verifies its checksum and signature, and replaces itself.
- 0.2.0: it can't update itself and won't tell you about new versions. Re-run the installer once: curl -fsSL https://pi-in-go.dev/install.sh | sh. After that, pig update works for every release.
0.4.0 is in progress: it tracks Pi 0.99.1, with built-in MCP and code mode that don't need Node. More soon. 🐷
r/PiGCodingAgent • u/Educational-Yak8793 • Sep 29 '26
As promised (and delayed 😰), here's the first follow-up release and it's a big one. 0.3.0 rolls up the unpublished 0.2.1 and everything I was holding for 0.3.1, so upgrade straight from 0.2.0.
Release notes: https://github.com/MichaelKinsy/PiG/releases/tag/v0.3.0
Try it: https://pi-in-go.dev
What you'll notice:
Extensions behave like Pi. Node extensions now import Pi 0.87.1's own pi-tui, pi-ai, pi-agent-core and pi-coding-agent code instead of PiG's stand-ins. pi-mcp-adapter (with /mcp), pi-bro and pi-warden work.
Node 22, 24 and 26. TypeScript extensions load with the same jiti release and options as Pi. That fixes the Node 24+ breakage several of you hit.
One pi.events bus across extension processes. Listeners get the original object, not a JSON copy, and crash isolation is kept.
Providers: DeepSeek, OpenCode Go and xAI in /login and --list-models, Z.ai thinking, Anthropic pasted-redirect login, Bedrock/Vertex/Cloudflare setup, and Pi's exact error text.
go install [email protected] works outside the checkout, and there are Session IDs in print/JSON mode.
Windows: Node's command quoting including Git Bash, and /login no longer goes through a shell.
Performance and corner case optimization, cause who doesn’t love optimization in a performance fork 😄
Go SDK heads-up: host-backed getters now return an error instead of guessing a default. There's a before/after in the release notes.
Thanks to everyone who filed issues and sent PRs, including the Reddit folks whose extension reports turned into fixes (rokrdev, WorriedAcanthisitta3, slypheed, zRafox). Keep the reports coming 🐷
r/PiGCodingAgent • u/CptFalcon7788 • Sep 28 '26
Hi all,
I'm very excited about the recent open sourcing of PiG. I'll be working on a series of pig extensions and piglets to help with financial analysis and invesmenting. I'm starting off with a pig extension for alpha vantage which is a popular financial data source. Anyone can get a free api key though it is limited.
https://github.com/Cpt-Falcon/pig-alphavantage
This quick, small extension provides pig agents with the ability to acquire important information about markets and companies. Its not completely comprehensive--instead, its optimized to provide agents with sensible information in an efficient manor. I'm hoping we can share investing tools to enable each of us to use pig as a personal investment facilitator, analyst, etc.
For example, instead of using the alpha vantage MCP server or the alpha vantage API directly where your agent has to call like several dozen tools/endpoints, you could just make a single av_overview call that obtains a good overview of key metrics at once. No need for the agent to have to know to make 20 different tool calls to cover all the required information.
In addition, every agent on your machine shares one cache and one rate budget. Run eight agents at once and they still spend one Alpha Vantage allowance between them, never pay twice for the same request, and never exceed the rate limit you set. This is critically important for multi agent environments tied to various data sources.
Pure Python standard library at runtime: nothing to pip install. PiG and python3 are enough. UV would of course work too.
Compact, typed tool output: every number carries a date and its source. Raw JSON never reaches the model.
Fails loudly. A missing key, an exhausted budget, or an Alpha Vantage error is reported to the model as what it is. Nothing is estimated or made up, and errors are never cached.
| Tool | What it returns |
|---|---|
av_quote | Latest price, open/high/low, previous close, change, volume |
av_daily | Up to 100 daily OHLCV bars, newest first, with a period summary |
av_intraday | Up to 100 intraday bars (1, 5, 15, 30 or 60 min) |
av_overview | Sector, industry, market cap, valuation ratios, margins, growth, 52-week range, analyst target |
av_financials | Key lines of the income statement, balance sheet, or cash flow (annual or quarterly) |
av_earnings | Quarterly reported vs estimated EPS and surprise % |
av_indicator | SMA, EMA, RSI, MACD (12/26/9), or Bollinger Bands |
av_news | Relevance- and freshness-weighted sentiment, label counts, top topics, latest headlines |
av_economic | Real GDP, CPI, inflation, fed funds rate, 10-year Treasury yield, or unemployment |
r/PiGCodingAgent • u/Educational-Yak8793 • Sep 27 '26
*edited -- Work slammed me today and so decided to wrap the 0.3.1 planned extra features and final fixes I'd noticed when I was preparing to cut 0.3.0. There may be a surprise release tonight if I'm able lock in, promise the updates will be worth it :)
Just a quick heads up as I know some people were waiting on 0.2.1 yesterday that we got some more contributions and fixes in that I decided to bump the release to today with better coverage for more diverse usage than what I had released under.
Will have a follow up post here, thanks all who have contributed and supported !🐷
r/PiGCodingAgent • u/Educational-Yak8793 • Sep 25 '26
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.
Behavior is checked against Pi in real terminals (tmux-driven scenarios that compare screens).
go install 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
Blog: 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
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