OwlkaDownload
← Back to Owlka

How it works

Last updated 2026-05-29. Owlka runs Claude on your computer, talks to your iPhone through an encrypted middleman, and keeps the work on your own machine. Here is the whole thing, start to finish.

Getting started in three steps

  1. Setup

    Install Owlka

    Download Owlka from owlka.com/download. Mac: open the .dmg and drag Owlka into Applications. Windows: run the installer. Owlka then launches the official Claude tools under your own Anthropic login and keeps your code, terminal, and project memory on your computer.

  2. Setup

    Pair your phone with a QR code

    The desktop app shows a one-time QR code. Scan it from the Owlka iPhone app. Pairing is one tap, and the code expires straight after. That scan is what hands the encryption keys over, face to face, so nothing secret ever crosses our servers in the clear.

  3. Setup

    Use Claude anywhere

    Your phone is now a thin client for your computer. Talk by voice or type, watch what Claude is doing live, approve a change, kick off a build, or pause it, all from the sofa. Pick up the same conversation on every paired phone.

Twenty seconds of step 3: watch, steer, and pause from wherever you are.

Three pieces, one conversation

Owlka is a desktop app and an iPhone app. The desktop does the real work; the phone is the front seat. The two talk through an encrypted middleman we run but cannot read.

Your Claude, on your computer
Owlka runs on your computer and launches the official Claude tools under your own Anthropic login. Your code, your memory, and your work stay on your own machine. Nothing about your project lives on our servers.
Your iPhone, your conversation
The Owlka iPhone app is the front seat. Talk by voice or type, watch what Claude is doing live, and step in whenever you want. The same conversation shows up on every paired phone.
An encrypted middleman
Your phone and your computer talk through a relay we host. It queues sealed packets and forwards them on, so a phone that drops off Wi-Fi can pick up where it left off. It cannot open the packets.

End-to-end encrypted, in plain English

The conversation stays between your phone and your computer. Here is what that actually means.

Sealed on the device
Every message is encrypted on your phone or your computer before it leaves the device. Only your paired devices hold the keys, so only they can open the messages.
The relay sees scrambled bytes
The relay carries sealed packets back and forth. It can see that your phone and computer talked, when, and roughly how much data they exchanged. It cannot see what they said. There is no Owlka-side key that would let it.
Keys are handed over at pairing
The one-time QR code you scan when you pair is what exchanges the keys. That happens face to face between your two devices. The keys never travel across our servers in the clear.
We hold no master key
If you lose your computer and all your paired phones, we cannot recover your conversation history. By design, there is no Owlka-side way to decrypt it.

Talk instead of typing

Dictate, don't type
Tap the microphone and speak. Owlka does not transcribe on the device: the recording goes to ElevenLabs, using an ElevenLabs key you add yourself on your computer, and comes back as text. With no key added, the button is greyed out and nothing is recorded. The security page explains exactly where the audio travels.

Good to know before you start

Owlka is powerful because Claude can do real work on your real computer. Two things are worth understanding before you rely on it.

AI replies can be wrong
Claude runs on your own computer and writes the replies you see. Like every AI model, it can hallucinate, invent facts, and write code that looks right but is not. Treat replies as drafts and verify anything important. Owlka is not for medical, legal, or financial advice.
Claude has deep control of your computer
Claude can run real commands on your computer: it can create, edit, and delete files and run programs. A misunderstood instruction can damage your work, including deleting files. You use Owlka at your own risk, so keep backups and read changes before you approve them.
What an approval card looks like when Owlka pauses to ask first.

The full version of both points is on the AI Use page.