Use voice with your OpenCode coding agent

From typing a prompt to having a conversation

Install Mortic on an Apple Silicon Mac and connect it with Google or GitHub. In your OpenCode project, run /mortic and tap M to speak. Follow the installation guide if this is your first session.

Mortic uses a disposable voice fork of your active OpenCode session. Ask a question, listen to the response, and read the same answer on screen. Speak again to interrupt or steer the explanation.

The voice session is read-only: it can read, search, and use the web, but cannot edit your files or run write actions. When you leave, the voice fork closes and your source OpenCode session stays unchanged.

Questions worth asking aloud

Understand an unfamiliar codebase

“Find the request handler for sign-in and explain how it reaches the database.” Use follow-up questions to narrow the explanation without composing a new written prompt for every step.

Think through a change before making it

“If we add retries here, which operations could run twice?” Discuss the tradeoffs while Mortic reads the relevant code. Review the answer before taking an implementation step in your coding session.

Get a technical explanation at your pace

“Walk me through this module. Start with the public interface.” Interrupt with “slow down” or “show me the caller” when you need a different level of detail. Exact code and paths remain easier to inspect in the written response.

These are example prompts, not promises of a particular answer. The available context and model response determine what Mortic can explain.

Keep control of the conversation

• M controls the microphone. Check its live or muted status before speaking.
• Speak again to interrupt the current answer and redirect the conversation.
• T opens the transcript when you want to inspect the conversation.
• Esc ends the Mortic session.

Watch the Mortic demo to see the conversation and sidepod together.

Common questions about OpenCode voice

Is Mortic just dictation?

Mortic supports a spoken conversation with an agent that has your OpenCode project context. You can ask follow-up questions, hear replies, see the written answer, and interrupt. It goes beyond converting speech into text in an input box.

Does Mortic write code by voice?

The current voice session is read-only. Use it to investigate code, explore plans, and understand explanations. It does not edit files or execute write actions.

Which coding tool and computers does this preview support?

The public installer covered here is for OpenCode on Apple Silicon Macs. See the current requirements before installing.

Do I need to bring API keys?

No provider keys are required for the managed Developer Preview. Connect your Mac through Google or GitHub. Access and model usage are limited; your account shows the percentage remaining.

Where does the conversation go?

Model and voice traffic goes from your Mac to the approved external services. Mortic does not collect prompts, responses, transcripts, or audio as product telemetry. Read the privacy notice for the full boundaries and retention details.

Try it in your project

Install Mortic for OpenCode, connect this Mac, and begin with one codebase question.