Voice input that fits real work
Speak through bugs, refactors, ideas, and follow-ups. Oplyr transcribes speech on-device on the Apple Neural Engine - your audio never leaves your Mac - and keeps the text visible so voice never becomes a black box.
Oplyr is a local-first macOS workspace for developers using AI coding tools.
Bring providers, project context, voice input, notes, reminders, and reviewable code changes into one controlled flow.
Invite-only beta. macOS 14+ first. Windows is not live yet, but it is the next platform direction if the Mac beta validates demand.
The problem
You start with one AI tool. It learns your project for the next thirty minutes. Then the context gets noisy, the session dies, the limit hits, or you switch to another provider.
Now you are explaining the same repo again. Same architecture. Same decisions. Same bugs. Same "please read these files first" prompt.
The problem is not that developers need one more chatbot. The problem is that AI work has no durable local operating layer. Context is scattered across terminals, browser tabs, chat logs, meetings, notes, and half-remembered decisions.
Oplyr exists to keep that loop together.
Product
Oplyr sits between you, your project, and the AI tools you already use. It gives you one macOS workspace for speaking, prompting, reviewing, switching providers, and keeping project context close.
Voice input, provider execution, transcript, workspace boundary, and diff approval in one control loop.
Speak through bugs, refactors, ideas, and follow-ups. Oplyr transcribes speech on-device on the Apple Neural Engine - your audio never leaves your Mac - and keeps the text visible so voice never becomes a black box.
Use Codex and Claude Code from one app today, with Gemini coming soon. Oplyr manages the workflow while your provider accounts remain yours.
AI can propose changes, but you approve what gets written. Inspect diffs, reject bad edits, and keep your repo under your control.
Oplyr runs on your Mac, scopes work to the project you choose, and is being built toward a local memory layer that survives restarts and provider switches.
Bring your own AI
Oplyr is not trying to replace Codex or Claude Code. It gives them a better local workspace: project boundaries, voice input, persistent context, review flows, and provider switching.
Provider tools run through your own local setup and accounts. Codex and Claude Code are current; Gemini is marked as coming soon. Oplyr does not take custody of your provider credentials.
How it works
Start with the desktop app. Oplyr runs the workspace locally and guides you through the setup needed for voice input and provider connections.
Use supported provider CLIs such as Codex and Claude Code through your own accounts. Oplyr becomes the control layer around them.
Open a project, speak or type, review the transcript, inspect proposed diffs, and approve only the changes you want.
Early access is macOS first and requires an Apple Silicon Mac (macOS 14 or later).
Some provider features require the matching provider CLI to be installed and authenticated.
Why Oplyr exists
Most AI coding workflows are scattered. One terminal for Codex. Another for Claude. A browser tab for reference. Meeting notes somewhere else. Project decisions buried in chat history.
Oplyr brings the workflow back into one place. It is a dedicated macOS surface for speaking to AI, keeping context, reviewing changes, and moving between providers without rebuilding the whole story every time.
The point is not to make AI more magical. The point is to make it more manageable.
Product roadmap
The beta starts with a trustworthy coding loop. The roadmap adds durable context, meeting memory, reminders, and session-aware focus tools without turning Oplyr into another noisy dashboard.
Provider connections, project-scoped sessions, local STT, transcripts, approval-gated edits, and diff review.
A provider-neutral memory layer for project decisions, architecture notes, approved changes, tasks, and context packs that survive restarts.
Capture engineering meetings, summarize decisions, extract action items, and connect notes back to the projects they affect.
Turn Gmail, calendar context, and meeting decisions into useful developer reminders without making another noisy task app.
Session-aware music recommendations for focus, debugging, deep work, and late-night shipping. Not a Spotify clone - a lightweight vibe layer for developers.
Roadmap items may change during beta. The priority is to make the core coding loop trustworthy before expanding the surface area.
Trust model
Oplyr runs the workspace on your Mac. Project access, transcripts, settings, and workflow state are designed around a local-first runtime.
Sessions are scoped to a project root you choose. The app is designed to keep AI work inside that boundary.
The assistant can propose changes, but meaningful file writes stay behind review. You decide what lands.
Code changes should be inspected like code review, not accepted from a chat bubble. Oplyr keeps the diff visible before approval.
Oplyr does not run your repo on our servers. Provider CLIs may communicate with their own services according to your provider setup and policies.
The product is being built with sensitive-file protection and workspace safety as core behavior, not optional enterprise polish.
Your voice is transcribed on-device on the Apple Neural Engine. Audio is processed on your Mac and is never uploaded to Oplyr or to a cloud speech service. The resulting text follows the same path as anything you type - what you send to a provider tool is governed by that provider.
Early access
We are inviting developers who use AI coding tools seriously and want a local workspace for providers, project context, voice input, notes, reminders, and reviewable code changes.
Request early access
Tell us what you build, which AI tools you use, and where your current workflow breaks.