Local-first · notch-native · macOS
The assistant that
stays on your machine.
Pixel Pane lives in the notch. It sees what you point it at, reasons locally by default, and never touches a file or runs a command without your word.
How it works
Three steps. No surprises.
Every run is a deliberate loop: you grant context, the model proposes, and the app executes only what you confirm. State is durable, so nothing happens twice and nothing happens silently.
-
01
Capture
Point at a region of the screen, an image, or a folder you've granted. OCR and pixels stay transient — they're context, not a recording.
-
02
Reason
A local model answers by default. Switch to cloud explicitly when you want it — either way, the Mac app owns grants, evidence, and policy.
-
03
Confirm
File writes, commands, and installs surface as drafts you approve. Approved work runs exactly once, from an immutable record.
What it refuses to do
Built so trust is the
default, not a setting.
Most assistants ask for the world up front. Pixel Pane is the opposite — the boundaries are wired into the app, not into a prompt you have to hope holds.
Request alpha access-
continuous recording
It looks only when you ask it to. There is no always-on screen capture.
-
silent file access
Your explicit grants are the only doorway to local files and folders.
-
hidden memory
New chats start blank. Nothing carries across sessions behind your back.
-
unconfirmed side effects
Risky commands and writes are denied or held until you approve them.
Alpha
Want it in your notch?
Pixel Pane is in private alpha. Tell me a little about how you'd use it and I'll get you a build.