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 Repair AxiOwl Provider Integrations
How to Repair AxiOwl Provider Integrations Provider integration repair in AxiOwl is not a matter of blindly retrying the same send until something appears in a chat. AxiOwl has a stricter model: it discovers real provider sessions, records them in a durable local registry, resolves sender and target identity, runs a targeted discovery repair when […]
AxiOwl Node Registry Explained
AxiOwl Node Registry Explained AxiOwl needs a practical answer to a simple routing question: when an operator says to reach a remote node, what machine is that, how should AxiOwl connect to it, and is the node still usable? The node registry is the small durable table that answers those questions. In the current AxiOwl […]
AxiOwl Named Agents Explained
AxiOwl Named Agents Explained A named agent in AxiOwl is a human-friendly handle for a real provider session that AxiOwl can route to. It lets an operator send to a recognizable target such as a chat, coding session, CLI agent, VS Code bridge session, Cursor session, or remote provider session without memorizing the provider's raw […]
AxiOwl Agent Registry Explained
AxiOwl Agent Registry Explained The AxiOwl agent registry is the local source of truth that tells AxiOwl which AI sessions exist, what they are called, which provider owns them, and whether AxiOwl has enough proof to send to them. It is not just a display list. In the current C++ implementation, the registry is durable […]