OctoAI

octo · privacy policy

Privacy policy

Octo is a desktop app, made by OctoAI (Lucas Marujo), that runs AI coding agents such as Claude Code, Codex and OpenCode across your projects. This policy covers the Octo app for Windows, macOS and Linux, including the version in the Microsoft Store, the Octo phone app for Android and iPhone, and the legacy orkai command line tool.

In short

What stays on your computer

Octo keeps its settings, your sessions, the agents you start and what they print in its data folder (%LOCALAPPDATA%\Octo on Windows, the local data folder of your user on macOS and Linux). To show the sessions, models and subagents of each agent, it reads the files those agents keep in your home folder, such as ~/.claude and ~/.codex. None of it leaves your computer, except to a phone you paired yourself, as described below.

What goes over the network, and to whom

Every request carries only what is described here, plus your IP address, which any server you connect to can see. Octo never sends your computer's name, your user name, your files or any identifier of its own.

Updates

The Octo downloaded from GitHub reads the version list of its newest release on GitHub (github.com/lucasmarujo/octo) each time it opens, and downloads the new version when there is one. The Octo from the Microsoft Store never does this: the Microsoft Store installs its updates.

Versions of your agents

When its window opens, Octo checks whether each agent you have installed has a newer version, by reading the public version number its maker publishes: downloads.claude.ai for Claude Code, registry.npmjs.org for Codex, Kilo, OpenCode and Qwen Code, x.ai for Grok, code.kimi.com for Kimi Code, pi.dev for Pi, cursor.com for Cursor and Google's update server for Antigravity, whose address names your operating system and processor type. When you click Install or Update, Octo opens a terminal that runs the maker's own installer, which downloads from the maker's servers.

Plan usage

To show how much of each plan you have used, Octo reads the login token an agent already saved on your computer (for example in ~/.claude/.credentials.json or ~/.codex/auth.json) and sends it only to the company that issued it: Anthropic (api.anthropic.com), OpenAI (chatgpt.com), Kilo (api.kilo.ai), OpenCode (opencode.ai), xAI (cli-chat-proxy.grok.com) and Moonshot AI (api.kimi.com), along with the account or user ID that service already gave you when it asks for one. This happens while Octo is open, at most every two minutes. Octo never stores, logs or forwards these tokens. An agent you signed in with an API key, or not at all, is never contacted. For Antigravity, Octo asks the agy program itself for the usage, and agy contacts Google on its own.

Phone access, only after you turn it on

Phone access is off by default. When you turn it on, Octo reaches your computer from your phone through a Cloudflare quick tunnel (api.trycloudflare.com, with cloudflared downloaded from Cloudflare's GitHub release if it is missing, and a lookup on cloudflare-dns.com) or, if you choose it, through your own Tailscale network. Everything between Octo and your phone after the first handshake is end-to-end encrypted with a key that never leaves your devices: Cloudflare carries the traffic and can see IP addresses, timing and your phone's browser details, but not your terminals, folders, agent names or usage. Octo keeps the model and system of each paired phone in its data folder so you can tell them apart.

Notifications on your phone, only if you allow them

If you allow notifications in the Octo phone app, the phone gives your computer, over the encrypted channel, a push token that Expo issues for the app. When an agent finishes or waits for you, Octo sends that token, the agent's name, whether it finished or is waiting, the agent's number and a random code your phone made up for that computer to Expo (exp.host), which passes the notification to Apple (APNs) or Google (Firebase Cloud Messaging) to show it on your phone. Your computer's name, your folders and what the agents print are never sent. Octo keeps the token in its data folder until you turn notifications off, pair your phones again or remove the app from the phone.

The agents themselves

The agents Octo runs are programs made by other companies. What you type into them, and the code they read and write, goes to their makers under their own terms and privacy policies, exactly as when you run them without Octo. Octo does not change, read for itself or forward that traffic.

The orkai command line tool

When the legacy orkai tool runs inside Windows Terminal, it adds a Windows Terminal profile whose icon Windows Terminal loads from octo.marujo.dev.

This website

octo.marujo.dev is a static site with no cookies, no analytics and no third-party resources. Like any web server, it may keep standard access logs (IP address, time, page and browser) for a short time to keep the site running.

Microsoft Store

If you install Octo from the Microsoft Store, Microsoft handles the download, the license and the updates under the Microsoft Privacy Statement. OctoAI only receives the reports Microsoft provides to every publisher, such as install counts and crash reports.

Children

Octo is a tool for software developers and is not directed at children under 13.

Changes and contact

When what Octo sends changes, this page changes with it, and the date at the top says when. Octo is open source, so every request above can be checked in its source code. For questions, open an issue at github.com/lucasmarujo/octo/issues.