AxiOwl Technical Overview
AxiOwl AxiOwl is a native Rust and Slint desktop application for routing messages between named chats and agents across supported provider surfaces. It exists to provide one clear operator-facing message path instead of a pile of disconnected local chat tools. This Docs page is based on the main project README and serves as the public-facing […]
AxiOwl Is Infrastructure for AI Workflows
AxiOwl Is Infrastructure for AI Workflows AxiOwl is not another chat window. In the current C++ implementation, it is a local Windows coordinator for AI workflow plumbing: it keeps track of reachable provider sessions, exposes command-line and MCP entry points, resolves sender and target identity, dispatches delivery through provider-specific edges, and records receipts and evidence […]
AxiOwl Is Not a Chatbot
AxiOwl Is Not a Chatbot AxiOwl is easy to misunderstand if the only mental model is "another AI chat window." That is not what the current product is. A chatbot is where a person types a prompt and expects that same product to generate the answer. AxiOwl is a coordination layer for provider sessions that […]
AxiOwl Cross-Provider Messaging Explained
AxiOwl Cross-Provider Messaging Explained Cross-provider messaging in AxiOwl means that one AI session can address another by a registered agent name, while AxiOwl handles the provider-specific mechanics underneath. The sender does not need to know whether the target is a Codex agent, a Codex CLI thread, a Cursor composer, a VS Code chat surface, VS […]
How to Use AxiOwl Across Multiple Computers
How to Use AxiOwl Across Multiple Computers AxiOwl is designed first as a local Windows coordinator for AI provider sessions. It discovers provider chats on the machine, records them in a registry, sends messages to named sessions, and exposes MCP tools so providers can reply with their real session identity. That local-first model matters when […]
How to Add a Remote Node to AxiOwl
How to Add a Remote Node to AxiOwl A remote node in AxiOwl is a Linux machine that the Windows AxiOwl coordinator can reach over SSH and use as a remote Codex delivery endpoint. The important part is not just that the host exists. AxiOwl needs a registered node row, a verified SSH path, a […]
How to Connect AxiOwl to Your First Provider
How to Connect AxiOwl to Your First Provider Connecting AxiOwl to a provider means more than adding a shortcut or writing a config file. In the current AxiOwl implementation, the Windows runtime discovers provider sessions, records reachable chats in a local registry, sends messages through provider-specific edges, and expects replies to come back through AxiOwl […]
How to Create Your First Named Agent
How to Create Your First Named Agent A named agent in AxiOwl is a sendable target you can refer to by a human-readable name instead of by a raw provider session ID. That name is not just cosmetic. AxiOwl stores it in its local registry with the provider, session ID, node, aliases, timestamps, and sendability […]
How to Send Your First Message Through AxiOwl
How to Send Your First Message Through AxiOwl Sending a first AxiOwl message is not just a chat command. In the current C++ implementation, a send goes through a small delivery pipeline: AxiOwl reads the target name, loads the local agent registry, resolves the target to a provider session, builds the visible message body, sends […]
How to Install AxiOwl for the First Time
How to Install AxiOwl for the First Time AxiOwl is installed as a local coordinator for supported AI provider sessions. On Windows, the current first-time install path is the AxiOwl MSI. That installer places the AxiOwl runtime on the machine, adds the command-line tool, writes local state under the user's AxiOwl data directory, and installs […]