Name: Kyro
Author: Eshan Roy

Question 1

What is Kyro?

Accepted Answer

Kyro is an open-source, local-first autonomous desktop AI agent built with a multi-threaded Rust native core (Tauri v2) and React 19. It runs directly on your personal computer, combining screen understanding, browser automation, terminal execution, and Model Context Protocol (MCP) integrations with strict, centralized governance.

Question 2

Who owns and develops Kyro?

Accepted Answer

Kyro is a product from Tonmoy Infrastructure (https://tonmoyinfrastructure.org/) and is owned and architected by Eshan Roy (m.eshanized@gmail.com, https://github.com/eshanized). The project is developed openly with community contributors under the MIT License.

Question 3

What is Tonmoy Infrastructure?

Accepted Answer

Tonmoy Infrastructure (https://tonmoyinfrastructure.org/) is an infrastructure research and product organization focused on building sovereign, privacy-preserving systems, distributed tools, and local-first computing platforms that return digital ownership to developers and individuals.

Question 4

Who is Kyro designed for?

Accepted Answer

Kyro is engineered with two dedicated experience modes: Everyday Mode for knowledge workers and non-developers (providing safe reversible file organization, local PDF/document parsing, and multimodal screen explanations), and Developer Workbench for software engineers (offering project discovery, managed dev servers, git-aware code checkpoints, automated compiler build triage, visual regression auditing, and multi-agent git worktrees).

Question 5

Is Kyro open source?

Accepted Answer

Yes. Kyro is 100% open source under the permissive MIT License. You can inspect the entire Rust backend, React frontend, and build workflows in the official GitHub repository at https://github.com/eshanized/Kyro.

Question 6

What does 'local-first' mean in Kyro?

Accepted Answer

In Kyro, 'local-first' means that your data, execution engine, task histories, conversation logs, memories, artifacts, and configuration never leave your computer unless you explicitly send a prompt to a configured model provider. All database storage uses local SQLite with Write-Ahead Logging (WAL mode), credentials reside in your OS Keyring, and file operations execute directly on your local filesystem without cloud telemetry or intermediaries.

Question 7

Does Kyro work completely offline?

Accepted Answer

Kyro's core application, database, file organizer, document parser, local diff engine, and desktop input engine operate entirely offline without network access. However, autonomous reasoning requires an LLM. If you configure a cloud model endpoint (like NVIDIA NIM or OpenAI), internet connectivity is required for inference calls. If you configure an OpenAI-compatible local model server (such as Ollama or vLLM), Kyro can operate fully offline.

Question 8

Does Kyro require an API key to function?

Accepted Answer

Yes, for autonomous agent reasoning tasks that call an LLM. Kyro comes pre-configured to use NVIDIA NIM endpoints (with default models nvidia/nemotron-3-ultra-550b-a55b and meta/llama-3.2-11b-vision-instruct) or any custom OpenAI-compatible endpoint. You supply your API key in Settings, where it is securely encrypted in your operating system keyring (Vault).

Question 9

Which models and providers are supported?

Accepted Answer

Kyro includes a built-in ModelRouter with a capability registry. Verified models include NVIDIA Nemotron (nemotron-3-ultra-550b), Llama 3.2 Vision (11B and 90B vision instruct), OpenAI GPT-4o / GPT-4o-mini, Anthropic Claude 3.5 Sonnet, Google Gemini 1.5 Pro / Flash, DeepSeek Coder 33B, and Mistral Large. Any OpenAI-compatible inference endpoint (including local self-hosted endpoints) can be specified via custom Base URL.

Question 10

How does desktop screen and browser interaction work?

Accepted Answer

For desktop computer use, Kyro captures screens via the native xcap library, overlays Set-of-Marks (SoM) visual coordinates, and synthesizes mouse/keyboard input via enigo. For browser automation, Kyro runs an isolated worker process supporting native WebDriver BiDi (Firefox) and Chrome DevTools Protocol / CDP (Chromium, Chrome, Brave, Edge, Opera) over WebSockets, strictly confined to origin-safe navigation rules.

Question 11

Does Kyro require human approval before taking actions?

Accepted Answer

Yes. Kyro enforces a Zero-Trust Centralized Authorization Engine in Rust. In SafeAutoApprove mode, only verified read-only shell commands (lexed into exact argv tokens) are executed automatically. File writes, system changes, ambiguous shell commands, and external MCP tools require interactive approval. Furthermore, when sensitive checkpoints (2FA, CAPTCHAs, password inputs, banking domains) are encountered, Kyro halts and requests a human takeover.

Question 12

Is Docker or Podman required to run Kyro?

Accepted Answer

No, container sandboxing is optional for standard usage. However, if you configure the shell execution policy to SandboxOnly, Kyro strictly enforces container isolation. If Docker or Podman is not running, Kyro fails closed—it will deny the action rather than silently falling back to the host system.

Question 13

Which operating systems and architectures are supported?

Accepted Answer

For now, Kyro is available for Linux-based distributions (x86_64 Debian/Ubuntu .deb and universal .AppImage). Official pre-built installers for macOS (Apple Silicon & Intel .dmg) and Windows 10/11 (.msi and .exe) are in active progress and coming soon. In the meantime, developers on macOS and Windows can compile and run Kyro directly from source using Cargo and Node.js.

Question 14

How can I report bugs or contribute to Kyro?

Accepted Answer

You can open bug reports, submit feature requests, or participate in discussions on the GitHub repository at https://github.com/eshanized/Kyro. For code contributions, clone the repo, run 'npm install', and use the unified Makefile ('make dev', 'make verify', 'make test'). Security vulnerabilities should be reported privately to m.eshanized@gmail.com.

Frequently Asked Questions

Still have questions?