Three states, one surface.
OpenMeow is always present, never in the way. It sits in the notch when you don't need it and expands into a workstation when you do.
Invisible until you need it.
Traces the MacBook Pro notch cutout exactly. 180×32pt of hardware silhouette — no dock bug, no menubar clutter, no window.
⌃⌘ to ask anything.
Grows vertically up to 7 lines. Pick an agent with a chip, or just type. Kitty answers; Fishy drives the web.
A full surface, summoned.
Drops into a 680×440pt conversation panel when you hit return. Threads persist across days. Hide it with esc.
Two agents. One shell.
Kitty handles conversation. Fishy handles the browser. They live in the same surface, talk to the same context, and hand off cleanly.
The agent you think with.
Answers questions, reads files, drafts replies, explains code. Streaming tokens to the notch under 200ms first-paint.
The agent you deploy at the web.
Drives a real browser. Books, buys, researches, fills forms. Touches the 90% of the web APIs can't reach.
Built for the OS. Not on top of one.
Native SwiftUI shell.
Not a web wrapper. Not an Electron app. A real NotchWindow with spring physics, hardware-aware positioning, and sub-frame latency.
Private by default.
Transcripts live on your device. No cloud sync, no training on your conversations, no surprise telemetry.
Fast under pressure.
First-paint under 200ms from ⌃⌘. Streaming tokens render as they arrive. Nothing blocks the UI thread.
Three minutes. Real running code.
End-to-end in the notch — Kitty answers, Fishy drives a real browser, results land back inline. No mocks.
Questions? val@opensorcery.ai