I built Open Portal because I kept doing the same stupid dance: screenshot something, switch to a chatbot, upload it, retype the context I was already staring at, switch back. Five steps to ask one question about something already on my screen. Open Portal is one keystroke. Your screen freezes, you drag a box around anything — a chart, an error, a clause in a PDF, someone else's slide in a video call — type a question, and the answer streams back anchored to the box you drew. Follow up in a thread without re-explaining anything. The part I care most about: it works over every app, because it reads pixels instead of APIs. No integration to build, no vendor to ask permission from, nothing to support per app. If it rendered on your display, you can ask about it — including the things nothing else can reach. Legacy desktop software. A PDF that blocks copying. A remote desktop. A game. Three decisions I'd defend: • Screenshots never touch disk. Crops live in memory and die with the process. The conversation lives in the app, not on my server — a server-side store is exactly the asterisk that "never stored" can't have. • No API key to paste. Sign in with an email link. No password, no config. • The free tier is 5 answers a day, forever, no card. Nobody recommends a tool their friend has to pay to evaluate. I built all of it solo — the Mac and Windows app, the service, the billing, the site. It's early, and I'd rather hear what's broken than what's nice. What would you point it at, and where did it fall over? — Kamran

Open Portal

Box anything on your screen. Ask it, or make something.

Box anything on your screen. Ask it, or make something.