How AxiOwl Uses Enrolled Agent Names Instead of Window Hunting
Window hunting is a weak foundation for AI workflows.
How AxiOwl Discovers Existing Provider Chats and Sessions
Discovery answers a basic question: what provider sessions exist on this machine right now?
How the AxiOwl Registry Stores Provider Sessions
The AxiOwl registry is the local address book for provider sessions.
How AxiOwl Separates Provider Brands From Provider Surfaces
AxiOwl separates provider brands from provider surfaces because brand names are too vague for installation, routing, and support.
How AxiOwl Sends Multiline Messages Safely With Standard Input
Multiline messages are common in AI workflows.
How AxiOwl JSON Receipts Make Sends Scriptable
Human-readable output is useful for operators. JSON output is useful for scripts.
How AxiOwl Distinguishes Local Acceptance From Provider Acceptance
AxiOwl distinguishes local acceptance from provider acceptance because those events happen at different boundaries.
How AxiOwl Adds Visible Reply Instructions to Delivered Messages
AxiOwl-delivered messages include visible reply instructions because receiving agents need an explicit return path.
How AxiOwl Uses Run IDs and Message IDs to Correlate Replies
Run IDs and message IDs help AxiOwl connect requests to replies.
How AxiOwl Sends Messages Between Named Agents
AxiOwl starts with a simple user action: send this message to that agent.