How to Recover From a Broken Provider Bridge
How to Recover From a Broken Provider Bridge A broken provider bridge is not one single failure. In AxiOwl, it can mean the provider extension did not load, the MCP config is stale, a registry row points at the wrong session, a patch is missing, the provider app was not restarted, or the target accepted […]
How to Confirm Which Agents Are Active
How to Confirm Which Agents Are Active When an AxiOwl operator asks which agents are active, the practical question is not just "what names are saved somewhere?" The real question is: which provider sessions does AxiOwl currently consider usable as message targets, and what evidence supports that decision? AxiOwl answers that through a durable local […]
How to Troubleshoot AxiOwl Message Delivery
How to Troubleshoot AxiOwl Message Delivery Troubleshooting AxiOwl message delivery starts with one discipline: separate the stages. An install can succeed while discovery is stale. A registry row can exist while the target is not sendable. A command can return accepted_by_axiowl while provider delivery, provider wake-up, and a recipient reply are still unproven. That distinction […]
How to Monitor AxiOwl Health
How to Monitor AxiOwl Health Monitoring AxiOwl health means checking whether the local coordinator can prove what it knows, what it can reach, and what happened to recent messages. The current C++ implementation is built around a CLI, an MCP server, provider-specific delivery edges, a durable registry, provider discovery, and JSONL evidence logs. A healthy […]
The AxiOwl Messaging Model
The AxiOwl Messaging Model AxiOwl's messaging model is deliberately small: one sender, one target, one body, one selected provider edge, and one honest receipt. That constraint matters because AxiOwl is not just moving text between two identical chat windows. It is coordinating messages across provider sessions, local and remote nodes, MCP tools, CLI commands, registry […]
How AxiOwl Turns Chat Sessions Into Addressable Work Surfaces
How AxiOwl Turns Chat Sessions Into Addressable Work Surfaces Most AI chat tools treat a conversation as something a human opens, reads, and types into. That is fine for one person working in one window. It is a poor fit when multiple provider sessions need to hand work to each other, reply with identity, and […]
How AxiOwl Keeps Provider Bugs Isolated
How AxiOwl Keeps Provider Bugs Isolated Provider integrations fail in different ways. A chat app can change a local database shape. A CLI can start returning a new error format. A bridge extension can register the wrong window. A patch-sensitive surface can become unsafe after an update. AxiOwl is built around the assumption that those […]
Why AxiOwl Uses SSH for Remote Routing
Why AxiOwl Uses SSH for Remote Routing Remote routing in AxiOwl is not built around a public network service. The current Windows desktop line treats the Windows build as the local coordinator and registry owner, then reaches Linux remote nodes through SSH. On the Linux side, AxiOwl exposes a small command surface: axiowl relay-session –stdio, […]
Why AxiOwl Separates Local Acceptance From Provider Acceptance
Why AxiOwl Separates Local Acceptance From Provider Acceptance When one AI agent sends a message to another, "sent" is not one event. A local router can accept a request, validate it, resolve the target, and create a receipt before the target provider has actually accepted the message. AxiOwl keeps those facts separate because collapsing them […]
Why AxiOwl Uses Named Agents
Why AxiOwl Uses Named Agents AxiOwl uses named agents because agent-to-agent messaging needs a human handle that can be resolved to a real provider session. A raw provider session ID may be useful to an adapter, but it is the wrong interface for an operator trying to send a message, read a receipt, or understand […]