Why AxiOwl Treats Each Provider Differently
Why AxiOwl Treats Each Provider Differently AxiOwl does not treat every AI provider as the same kind of endpoint because the providers are not the same kind of endpoint. A Codex CLI thread, a Cursor Agent Window, a VS Code Copilot chat, an Antigravity agent session, and a future CLI target all expose different session […]
Using AxiOwl With Antigravity
Using AxiOwl With Antigravity AxiOwl can work with Antigravity agent sessions as one of its supported local provider surfaces. In normal use, that means an operator or another agent can address a discovered Antigravity chat by name, send it a message through AxiOwl, and let Antigravity reply back through the AxiOwl MCP path with the […]
Using AxiOwl With OpenCode
Using AxiOwl With OpenCode AxiOwl's OpenCode work is about making OpenCode CLI sessions addressable from the same local routing layer used for other AI-provider sessions. Instead of treating OpenCode as a separate manual terminal workflow, AxiOwl can discover OpenCode sessions, add them to its local registry, and route messages to a selected session through the […]
Using AxiOwl With Claude Code
Using AxiOwl With Claude Code AxiOwl can treat Claude Code CLI sessions as named provider targets instead of forcing every handoff through one generic terminal. The idea is simple: AxiOwl discovers real Claude session state, records sendable sessions in its registry, and uses Claude's documented CLI resume flow to deliver a message into the right […]
Using AxiOwl With VS Code Copilot
Using AxiOwl With VS Code Copilot VS Code Copilot is one of the local provider surfaces AxiOwl is designed to coordinate. In the current Windows desktop implementation, AxiOwl does not treat VS Code as a generic chat box. It has a first-party VS Code Copilot-backed bridge extension, installer features for that bridge, local discovery for […]
Using AxiOwl With Cursor
Using AxiOwl With Cursor Cursor is one of the local agent surfaces AxiOwl can address from its Windows desktop product. The practical idea is simple: a Cursor chat can be registered as an AxiOwl agent, then another agent or operator can send work to it through the same AxiOwl command path used for other providers. […]
AxiOwl Command Telemetry Explained
AxiOwl Command Telemetry Explained Command telemetry in AxiOwl is the local evidence trail that explains what happened when a command, MCP tool call, or provider reply moved through the system. It is not just a success message. It is the difference between "AxiOwl accepted this request" and "the target provider received it, accepted it, and […]
AxiOwl Failure Stages Explained
AxiOwl Failure Stages Explained A failed AxiOwl message is not one vague event. It is a failure at a specific boundary: the request may be malformed, the sender may be unresolved, the target may be missing from the registry, the delivery worker may fail to start, the provider edge may reject the message, or the […]
AxiOwl Run IDs and Message IDs Explained
AxiOwl Run IDs and Message IDs Explained AxiOwl uses two different identifiers when a message moves through the system: a run ID and a message ID. They sound similar, but they answer different questions. The run ID ties related work together. The message ID identifies one specific send attempt and becomes the receipt handle for […]
AxiOwl Cross-Provider Messaging Explained
AxiOwl Cross-Provider Messaging Explained Cross-provider messaging in AxiOwl means that one AI session can address another by a registered agent name, while AxiOwl handles the provider-specific mechanics underneath. The sender does not need to know whether the target is a Codex agent, a Codex CLI thread, a Cursor composer, a VS Code chat surface, VS […]