How AxiOwl Renames Provider Sessions After Creation
Renaming provider sessions makes AxiOwl workflows easier to understand.
How AxiOwl Uses a VS Code Bridge Extension for Chat Delivery
AxiOwl uses a VS Code bridge extension because useful VS Code chat behavior lives inside VS Code.
How AxiOwl Lists Registered Agents for Operators
Listing registered agents gives the operator a current view of addressable targets.
How AxiOwl Tracks VS Code Window Ownership Before Sending
VS Code window ownership matters because the wrong window can produce a false success.
How AxiOwl Adds and Removes Registry Agents Manually
Manual registry commands exist for advanced setup and troubleshooting.
How AxiOwl Supports VS Code Copilot Through the VS Code Host
VS Code Copilot support belongs inside the VS Code host because Copilot chat state belongs there.
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 Uses the Cursor Bridge Command Watcher
The Cursor bridge command watcher is the preferred path for Cursor delivery when it is installed and active.
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 Patches Cursor Without Using the URI Wake-Up as the Normal Path
AxiOwl should not use Cursor URI wake-up as the normal delivery path when the bridge watcher is installed and active.