Pi,
in your notch.
Pi and Oh My Pi notifications, replies and cost on your Mac
Gnista shows every Pi and Oh My Pi session in your MacBook’s notch: working, done, or waiting for you. Reply from the notch when a turn is done, approve Oh My Pi’s plans there, and see what each session cost.
Gnista with Pi, at a glance.
- Where it runs
- Pi (
pi) and Oh My Pi (omp) in any terminal. - Setup
- One extension file each, in
~/.pi/agent/extensions/and~/.omp/agent/extensions/; nothing else changes. - Needs you
- Oh My Pi’s tool approvals and plan reviews; in Pi, another extension’s dialog.
- Answer from the notch
- Oh My Pi’s plans: Approve runs the plan, Keep planning sends it back with what to change. Tool approvals and Pi’s dialogs are answered in the agent.
- Reply from the notch
- Yes, wherever it runs: Gnista’s extension adds your words as the next prompt, and they show as yours.
- In the row
- The session’s title, your prompt, the reply, the tool in use, the model and context, read from the session file.
- Subagents
- Oh My Pi’s: how many are at work, on the session’s row.
- Cost and limits
- What each reply cost, as the agent records it, added up for the session; no plan limits.
One extension, two agents.
Pi and Oh My Pi take TypeScript extensions, not command hooks, so Gnista adds a small one that the agent runs itself. It sends each turn’s start, each tool, each wait and each turn’s end, and never blocks a tool.
Oh My Pi’s plans, answered in place.
When Oh My Pi has a plan ready, read it in the notch. Approve, and it runs. Keep planning, with what to change, and it plans again. Whichever answers first counts, the notch or its own window.
One more thing? Reply.
When a turn is done, write in the notch. Gnista’s extension adds it as the session’s next prompt, the same as typing it, in whichever terminal the agent runs.
Priced as it was billed.
The row reads the session file the agent writes: its title, your prompt, the reply, the model, the context, and what each reply cost. For a model Gnista doesn’t know, describe it in a model file.
What it can’t do with Pi, and why.
- Oh My Pi’s tool approvals show in the notch, but only its own window can approve them, so you answer there.
- Pi asks about nothing itself. When another extension opens a dialog, the row shows it needs you, and you answer in Pi.
- Keep planning needs words: Oh My Pi plans again only with what to change, so without them the plan stays for its own window.
- Print mode and subagents’ own sessions don’t report: the row is about the session you started.
Connected in a minute.
- Open Gnista and tick Pi, Oh My Pi, or both.
- Gnista writes one new file for each,
~/.pi/agent/extensions/gnista.tsor~/.omp/agent/extensions/gnista.ts, and leaves your settings alone. If another extension already has that name, Gnista stops and says so. - To answer Oh My Pi’s plans from the notch, turn on Settings ▸ General ▸ Answer prompts in Gnista.
- Start a new session. One already open picks up the extension when you restart it.
Pi, asked and answered.
Does it work with Oh My Pi?
Yes. Oh My Pi is Pi’s fork, with its extensions in a folder of its own. Gnista connects each one separately, and Oh My Pi gets plan reviews from the notch too.
Can I approve tools from the notch?
No. Pi asks about nothing itself, and only Oh My Pi’s own window can approve its tools. Oh My Pi’s plans you can answer from the notch, with Answer prompts in Gnista on.
Can I reply from the notch?
Yes, once a turn is done, in any terminal. Gnista’s extension adds your reply as the next prompt, and it shows as yours.
How do I remove it?
Settings ▸ Agents ▸ Pi (or Oh My Pi) ▸ Disconnect deletes Gnista’s extension file; your settings are never touched.
Gnista also keeps an eye on
Claude Code
Codex
Gemini CLI
Copilot
OpenCode
Devin
Qwen Code
Cursor
Mistral Vibe
CodeBuddy
Kimi Code
Codewhale
Droid
Antigravity
Qoder CLI
Kilo Code
MiMoCode
ZCode
WorkBuddy
Grok Build
Amp
Goose
Auggie
OpenHands
Trae
Aider
DeepSeek Harness
Wrote your own? It can report to Gnista with one line of JSON: custom agents.