Back to Projects
Nov 2026

Otto

A Tauri 2 desktop notch that routes prompts to 19 local AI CLIs through compiled adapters, with learning modes, staged Smart Capture, local searchable history, and no automatic approval of CLI host permission requests.

Overview

Otto is a Windows desktop notch for studying, reading, and solving problems with AI. It sits at the top edge of the screen, expands on hover or with Ctrl+Alt+O, and sends prompts to AI CLI tools that are already installed and signed in on the machine, so it does not need a separate API key or subscription.

Engine adapters

Each engine is wired through a statically compiled adapter in the Rust agent layer, with no runtime plugin loader. Dedicated protocol adapters cover Codex, Claude Code, OpenCode, and Pi. A shared ACP runtime covers 15 more CLIs. Installed CLIs are discovered from PATH, and a Refresh PATH action in settings lets a newly installed CLI appear without restarting the app.

Capture stays explicit

Screen capture runs only when the user triggers it. Regions, windows, pasted or dropped images, and selected text appear in the composer as removable attachments, so the user decides what is sent. Selected text is read through Windows UI Automation instead of the clipboard. A finished answer can be inserted at the last focused external caret as Markdown-stripped text, without overwriting the clipboard.

Permissions fail closed

When a CLI asks for a host permission mid-turn, Otto shows an inline card with Decline & continue and Allow once. Nothing is approved automatically. If the request times out after 120 seconds, or the user presses Stop, closes the window, or the connection drops, Otto replies with Decline or Cancel. Otto has no file-edit executor and no shell executor of its own; each CLI keeps its own tool policy.

Release pipeline

Version 1.0.0 is dated 2026-11-21 and ships as a signed Windows installer with minisign-verified in-app updates, SHA-256 checksums, and a signed update manifest. Pull requests run only the affected checks, and release builds run the full frontend, Rust, and native E2E gates on frozen lockfiles before publishing.

Limits

The installer is not yet Authenticode-signed, so Windows SmartScreen may warn on first install. The native E2E suite uses a deterministic Codex subprocess fixture instead of live model calls, so each engine’s live behaviour is not covered by that suite. Rate-limit figures and model availability are reported as each CLI exposes them, and Otto cannot make them more precise.