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. […]
Using AxiOwl With Codex
Using AxiOwl With Codex AxiOwl's Codex integration is built around a simple idea: Codex should be able to use AxiOwl as a native tool, not as a pasted shell recipe that asks the model to guess who it is. In the current AxiOwl implementation, the Codex plugin exposes an MCP server named axiowl, and that […]
AxiOwl Node Registry Explained
AxiOwl Node Registry Explained AxiOwl needs a practical answer to a simple routing question: when an operator says to reach a remote node, what machine is that, how should AxiOwl connect to it, and is the node still usable? The node registry is the small durable table that answers those questions. In the current AxiOwl […]
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 […]
AxiOwl Named Agents Explained
AxiOwl Named Agents Explained A named agent in AxiOwl is a human-friendly handle for a real provider session that AxiOwl can route to. It lets an operator send to a recognizable target such as a chat, coding session, CLI agent, VS Code bridge session, Cursor session, or remote provider session without memorizing the provider's raw […]
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 […]