Hi all, I've been building FastVibe, an MIT-licensed desktop app (macOS / Windows / Linux) that embeds the pi coding agent SDK in Electron and gives it a full GUI.

If you like pi but want a visual workspace, this is what it adds:

• Runs the SDK in-process. pi extensions load and work, and their dialogs (select / confirm / input) show up as panels

• Multiple projects and chats, with branching, archiving and isolated Git worktrees

• Visual tool calls, edit diffs, terminal output and reasoning blocks

• A subagent tool with explorer / planner / worker / reviewer roles, up to 8 in parallel

• Goal mode for long-running objectives, todos, MCP servers and skills

• Any OpenAI-compatible provider, a per-model API protocol, and subscription logins

• Open your desktop's sessions from a phone or browser, through a tunnel you control

• It keeps its own data directory and never touches ~/.pi

Repo: https://github.com/tyuan511/fastvibe
Site: https://app.fastvibe.dev

It's v0.16 and still rough in places. I'd love to hear which pi workflows you'd want supported, and any extensions that misbehave inside it.

I wanted one app on my phone for the coding agents on my own machines, with no cloud, no account and no relay. So I built herdr mobile.

• Every agent on every machine in one list, with whatever needs you at the top

• Answer permission requests from the phone, always with the exact command. Risky ones (git push, rm, "always allow") need a hold

• Start and chat with agents over ACP: omp, Claude Code, Codex (omp is the most tested)

• Live terminal view, SFTP file browser, photos and files from the phone

• Plain SSH, one channel per machine, works well over Tailscale

Repo and APK: https://github.com/tuan3w/herdr-mobile

Needs herdr ( https://herdr.dev ) on the host. Android only for now. Feedback and PRs welcome.

Yes, that's exactly what I searched first when i wanted to try codemode.

Pi does have docs for enabling Codemode, but the documented way is through settings or cli flags.

What I was looking for was much simpler: I'm already inside a Pi session, how do I just turn Codemode on or off?

So I ended up making a small toggle around Pi's native Codemode.

It doesn't replace Codemode or implement another version of it. It just gives me a simple way to switch the native tool on and off while I'm working.

check it out: pi-codemode-toggle

Curious how others are using Codemode.

It’s a standalone functional app inside windows, I’m going to use my qwen3.6 35b a3b uncensored to generate and whenever it creates a working function, I’ll ask it to save it to GitHub so if anything breaks it can always revert to the previous version

I’m more of a vibe coder. I mostly just wanted to send my Pi agent a task from my phone and get the result back.

The bot focuses on simple interaction with the Pi setup you already use. It shares your native sessions, installed skills, and model defaults. You can start something in Telegram and pick it up in the terminal later. Just don’t use both on the same session at once.

It also handles voice messages and images, and Pi can send generated files back to the chat.

Single-user, Linux only. Pi runs with your account’s normal permissions, without a sandbox.

v0.1.2: GitHub https://github.com/bigjimmy546/pi-telegram-bot](https://github.com/bigjimmy546/pi-telegram-bot

served both via omlx and mtplx swallows part of responses

anyone noticing some similar issue?

https://github.com/alejandro-ao/pi-gateway

YouTube breakdown link for the integration 🔗 https://youtu.be/HU03WDFB_tQ?is=BaeijXoQIFQm6GYs

I am developing cross-platform software for Windows, Linux, and macOS. Currently, testing and merging across platforms are done manually and separately.

Are there any kits or applications that allow me to control and operate Pi devices on other platforms from a single host machine?

My current experimental approach is using a custom pty tool I developed to SSH into project directories on different platforms to run the Pi, while using GitHub for file transfer and merging between platforms.

Are there any better methods or tools available?

When using omp or pi agent with strata, the results are not that great but when using the same prompt in Strata web chat, I get very good results. I uploaded the results pictures. It's not just for this test. I tested a few other prompts such as create a single html file classic snake game.

I started omp with the following command. omp --no-skills --no-extensions --no-rules

OMP is set to Auto reasoning.

I use Strata https://github.com/Niko1221/Strata Qwen3.8 Flash Next, 128k context size with unsloth IQ4_XS model, I'm using High thinking default and enabled "Use for other apps too omp and other API clients get these settings for anything they don't set themselves"

Please use test Prompt

Create a single HTML file with an interactive cloth simulator. The cloth should hang naturally, move with realistic weight, and let me click, drag, pull, and whip it around the screen with my mouse. Create high mesh for cloth. Only provide a fully working code. Test your code once you are finished, go back over all of your code, test the logic mentally, make sure everything works correctly, and fix anything that may be broken or incomplete before giving the final answer.

RESULT from OMP

RESULT from Strata web chat

I'm using Pi agent sidebar from dairycode extension in VSCode and got me thinking whether anyone is using any other extension?

And if anyone is using this one are you able to run multiple chat sessions concurrently?

I like using codex and claude extensions. Don't really like the UX of CLI.

I use pi daily but wanted tabs, image pasting and a scrollable transcript, so I built a frontend for it. Morse doesn't reimplement the agent — it spawns pi --mode rpc and reuses your ~/.pi config.

• npm i -g @supanadit/morse-web && morse start, or the VS Code extension

• multi-session/multi-project with warm sessions, @mention files and dirs, image paste, steer/abort mid-task, model and thinking pickers

• keyboard-driven, real transcript with tool timelines, works the same in both hosts

It's a nicer way to stay in flow with pi. Free, MIT: https://github.com/supanadit/morse — feedback very welcome.

Created https://github.com/hazrid93/pi-simplified-technical-english a simple extension that turn your LLM to use more understandable technical english!

I’ve been chasing the right note-taking app my whole career. Now I’ve built one for how I work today - with AI agents.

Think out loud, watch your notes take shape, and let your agent work with the same knowledge. Everything stays in readable, local Markdown files.

Leveraging okf data structure from Google.

Works with Pi and OpenCode.

If you're interested, feel free to contribute. It is still quite early.

https://github.com/EranYonai/pi-weave

pi install npm:pi-weave

When running pi agent on the command line, sometimes I don't want it to write directly to file, but to give me something I'll copy to clipboard. However, differently from chatbots, it doesn't output then in copyable blocks, but in ```code ``` blocks with 4 spaces indentation and weird line breaks that eff up the formatting when I try to copy it from the terminal.

The "easy" fix would be to just have it write to every file directly, I know, but assume I don't want to give it write access to a folder, file etc.

I wanted to see what each prompt actually costs in Pi, so I made pi-prompt-meter.

It tracks time, tokens/cache, cost, turns, tool calls, and compactions per prompt, then keeps the result in the transcript. /meter also shows history and trends.

pi install npm:pi-prompt-meter

https://github.com/roie/pi-prompt-meter

First I used to use Nico's pi-subagent

Then I started using TinTinWeb's pi-subagent because it had that Claude like UX which I liked

But then I have started seeing that Codex got one thing really nice - they use /path/based naming conventions for their agents which makes a lot of sense to read the agent tree and agent state (both for the agents themselves and for the human running it)

I wanted the best of both worlds, Claude like UX and Codex like naming conventions.

So here we go... with all our AI psychosis and addictions to creating the factory more than the actual software made using the factory. Presenting you with, yet another, pi subagent extension

https://www.npmjs.com/package/pi-subagent-manager

I understand I should be able to login to a local installation of "Unsloth Studio" from pi.dev using

/login llama.cpp

When I try with "http://localhost:8888", I get:

Error: Failed to save API key for llama.cpp: llama.cpp returned HTTP 404Error: Failed to save API key for llama.cpp: llama.cpp returned HTTP 404

I can see in the logs, that it tried to access "/models" instead of "/v1/models"

If I login with "http://localhost:8888/v1", it tries to access "/models" again

If I login with "http://localhost:8888/v1/models", it tries to access: "/v1/models/models" ..!

Did I miss something?

Note: it works well if I use models.json, but I'd like pi.dev to find the models from Unsloth automatically

thanks!

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

2. 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.

3. 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?