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 […]
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 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 […]
AxiOwl Message Routing Explained
AxiOwl Message Routing Explained AxiOwl message routing is the part of AxiOwl that turns a human target name, such as a known Codex thread or VS Code chat, into a provider-specific delivery attempt. It is not just a text forwarder. The current AxiOwl C++ implementation keeps a local registry of sessions, resolves sender identity, checks […]
Using AxiOwl When One Agent Is Not Enough
Using AxiOwl When One Agent Is Not Enough One AI agent is often enough for a small question. It is not always enough for real engineering work. A coding thread may be good at editing a repository, another session may be better positioned inside an editor, another provider may have the right local context, and […]
Using AxiOwl to Coordinate a Small AI Development Team
Using AxiOwl to Coordinate a Small AI Development Team Small AI development teams do not always look like one person chatting with one model. A real workflow may involve a Codex thread handling code changes, a VS Code or Copilot-backed chat checking editor behavior, an Antigravity session working through a desktop surface, and another provider […]
How to Connect AxiOwl to Your First Provider
How to Connect AxiOwl to Your First Provider Connecting AxiOwl to a provider means more than adding a shortcut or writing a config file. In the current AxiOwl implementation, the Windows runtime discovers provider sessions, records reachable chats in a local registry, sends messages through provider-specific edges, and expects replies to come back through AxiOwl […]
How to Send Your First Message Through AxiOwl
How to Send Your First Message Through AxiOwl Sending a first AxiOwl message is not just a chat command. In the current C++ implementation, a send goes through a small delivery pipeline: AxiOwl reads the target name, loads the local agent registry, resolves the target to a provider session, builds the visible message body, sends […]