AxiOwl Notes
Short product notes about agent messaging, remote nodes, safe automation, and the workflows AxiOwl is built to coordinate.
-
About AxiOwl
A concise introduction to AxiOwl and the role it plays in coordinating AI-assisted software work.
-
How AxiOwl Relays Messages Over SSH Without Opening Inbound Ports
AxiOwl remote relay can use SSH so remote nodes participate without opening new inbound service ports.
-
How AxiOwl Verifies Remote Nodes Before Routing Work
Remote node verification checks whether AxiOwl can reach a configured node before relying on it.
-
How AxiOwl Tracks Remote Nodes in a Node Registry
Remote nodes need their own registry because a remote target is more than an agent name.
-
How AxiOwl Adds and Removes Registry Agents Manually
Manual registry commands exist for advanced setup and troubleshooting.
-
How AxiOwl Lists Registered Agents for Operators
Listing registered agents gives the operator a current view of addressable targets.
-
How AxiOwl Renames Provider Sessions After Creation
Renaming provider sessions makes AxiOwl workflows easier to understand.
-
How AxiOwl Creates New Provider Sessions
AxiOwl create support lets the user start a new provider session through a provider-specific path.
-
How AxiOwl Rate Limits Sends to Avoid Provider Flooding
AxiOwl rate limits sends because provider sessions should not be flooded accidentally.
-
How the AxiOwl Delivery Worker Keeps Provider Dispatch Isolated
The delivery worker separates request acceptance from provider dispatch.
-
How AxiOwl Delivery Stages Show Where a Message Failed
Delivery stages turn one vague send operation into a sequence of observable events.
-
How AxiOwl Evidence Logs Make Provider Failures Debuggable
Evidence logs make provider failures explainable.
-
How AxiOwl Doctor Inventory Explains What Is Installed
`axiowl doctor inventory` should explain the local installation in one place.