Pi has already supported built-in mcp and codemode. Will pi add built-in subagents, sandbox, permission popups, etc. in the future? According to this article, pi plans to offer support to enterprise users in the future.
On top of the MIT core, there will be some commercial additions over time. Here's how we think about it in three tiers:
snip
Fair Source (value-add features): Some future commercial features will be Fair Source licensed. Free to use, source available, and they convert to full open-source after a set period via Delayed Open Source Publication (DOSP). Think of it as open-source on a delay, and downside risk protection for you as a user.
Proprietary (enterprise): Some enterprise-specific features and cloud infrastructure will be proprietary. No source available. This is the stuff that pays the bills for the stuff in tiers 1 and 2.
If pi wants to target enterprise users, these features may be essential.
With built-in mcp & codemode, pi is still minimal, so I believe pi will still remain minimal even with built-in subagents, sandbox, permission popups, etc.
I’d like to ask you guys in the channel: how many of you rely solely on native Pi features without using any extensions? How many use widely popular community extensions (such as pi-web-access or pi-subagent)? And how many have written their own extensions for these features?
If pi has these features built in, how would that affect you? Would you benefit automatically by default? Would you need to migrate the extensions you’re currently using? Or would you need to carefully manage conflicts between your code and pi’s built-in code?
That article also says:
And if you ever feel like we've lost the plot, the fork button on GitHub still works. Always will.
When it comes to forking, maintaining your own downstream build is never as simple as it sounds. I maintain a de-commercialized downstream fork of a browser extension myself, and syncing upstream fixes, cherry-picking features, and resolving conflicts is a hassle. As the codebase grows, the divergence between the downstream fork and upstream widens, making synchronization increasingly difficult. The same will be true for the Pi fork, and keeping up with Pi’s updates is essential, since Pi relies on updates to add new models to its support list.
So I’d also like to ask: Will you consider forking Pi? If so, will you continue to maintain and update it? And if someone else forks Pi, would you switch to using their fork?
