AxiOwl Evidence Logs Explained
AxiOwl Evidence Logs Explained AxiOwl evidence logs are the product's operating memory for message routing. They record what AxiOwl accepted, what it rejected, what it tried to discover, which provider path it handed work to, and where the boundary sits between a local receipt and real provider proof. That distinction matters. AxiOwl is not a […]
AxiOwl Delivery Receipts Explained
AxiOwl Delivery Receipts Explained A delivery receipt in AxiOwl is not a vague success message. It is a boundary marker. It tells the operator which part of the AxiOwl send pipeline has accepted the work, which provider route was selected, and where to look for evidence. Just as importantly, it avoids promising facts that AxiOwl […]
AxiOwl Session Discovery Explained
AxiOwl Session Discovery Explained AxiOwl session discovery is the step that turns provider-owned chat state into routing facts AxiOwl can use. It answers a practical question: which real agent sessions exist, what provider owns them, what stable session id identifies them, and whether AxiOwl has enough proof to send to them? That sounds simple, but […]
AxiOwl Provider Bridges Explained
AxiOwl Provider Bridges Explained AxiOwl provider bridges are the parts of AxiOwl that make different agent chat surfaces usable through one local message contract. They do not make every provider behave the same way internally. They give AxiOwl one controlled place to translate a resolved message into the specific delivery method that a target provider […]
AxiOwl Remote Nodes Explained
AxiOwl Remote Nodes Explained AxiOwl remote nodes are Linux machines that a local Windows AxiOwl installation can reach over SSH and use as remote Codex endpoints. They are not a generic cloud fallback layer, and they are not a second desktop UI. In the current implementation, the Windows build owns the local registry and coordinates […]
AxiOwl Message Routing Explained
AxiOwl Message Routing Explained AxiOwl message routing is the part of AxiOwl that turns a human target name, such as a known Codex thread or VS Code chat, into a provider-specific delivery attempt. It is not just a text forwarder. The current AxiOwl C++ implementation keeps a local registry of sessions, resolves sender identity, checks […]
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 […]
Using AxiOwl When One Agent Is Not Enough
Using AxiOwl When One Agent Is Not Enough One AI agent is often enough for a small question. It is not always enough for real engineering work. A coding thread may be good at editing a repository, another session may be better positioned inside an editor, another provider may have the right local context, and […]
Using AxiOwl for QA and Browser Testing
Using AxiOwl for QA and Browser Testing QA for agent software is difficult because a successful command is not the same thing as a successful user-visible result. A tool can accept a request, a provider can return exit code 0, and the actual target chat can still fail to receive, display, or act on the […]
Using AxiOwl for Infrastructure Maintenance
Using AxiOwl for Infrastructure Maintenance Infrastructure maintenance is mostly coordination: check the current state, assign the right operator or agent, send the exact instruction, keep a receipt, and preserve enough evidence to debug what happened later. AxiOwl is useful in that work because it treats AI provider sessions as named operational endpoints instead of anonymous […]