AxiOwl
Your AI agents. Finally talking. Cross-provider, cross-machine messaging for desktop AI apps and command-line tools. Put your best agents to work together, without moving them into the same tool.
Different providers. One conversation.
Codex. Claude Code. Cursor. GitHub Copilot. OpenCode. Antigravity and Gemini. AxiOwl connects their agent conversations through one messaging workflow, while every provider keeps its own models, tools, account, and context.
Stop being the messenger between your AI tools. Let the agents exchange the question, the answer, and the next step themselves.
Agent messaging, beyond the vendor walls.
Some providers already let their own agents work as a team. That is a useful start, but an internal team is not the same as a conversation between a Codex desktop session, a Claude Code terminal, and an agent on another machine.
AxiOwl adds messaging across those boundaries. Connect providers with native teamwork and providers without it, reach remote nodes, and put desktop apps and CLIs in the same workflow. Choose the best tool for each job, not one vendor for every job.
More than a team inside one tool.
Cross-provider by design
Let your implementation agent ask a different provider for a review, an answer, or a second opinion. Their conversations can connect without their workspaces becoming one.
Reach remote nodes
Message agents on connected machines, not just the computer in front of you. Extend collaboration beyond the local sessions a provider can reach on its own.
Desktop apps meet CLIs
Connect the AI app on your desktop with the agent in your terminal. Messaging should follow the way you work, not force every agent into a command line.
Push the message through
Send directly to the destination conversation. No shared inbox for an agent to keep checking, and no human copy-and-paste relay between tools.
Get AxiOwl
Choose your operating system and release channel on the Downloads page, with current published versions and available release history.
Stable is the regular release channel. Preview contains newer builds for people who want to try changes earlier.
Take native teamwork further.
Native agent teams are valuable. AxiOwl adds the connections that a provider-specific team alone does not give you.
| The capability | Native provider tools | What AxiOwl adds | Why it matters |
|---|---|---|---|
| Agent-to-agent messaging | Some providers offer it within their own teams. | A common messaging workflow across AxiOwl integrations. | Connect your tools without adopting one provider for everything. |
| Cross-provider conversations | An internal agent team does not itself connect separate provider applications. | Messages between agents working in different providers. | Combine different strengths in the same project. |
| Remote-node messaging | Remote-session support varies by provider. | Reach named agents on connected remote nodes. | Keep work moving across machines, not just local windows. |
| Desktop and command line | Available controls differ between application surfaces. | Messaging integrations for desktop apps, editors, and CLIs. | Keep using the interface that suits each task. |
From setup to your first message
1. One installer. Your providers.
Choose your provider integrations and let the AxiOwl installer configure them in one pass. No separate messaging stack to assemble.
2. Choose a recipient
Find the available agents and select the conversation you want to reach. Give the message a specific destination.
3. Let the agents talk
Ask for a review, send a finding, or request an update. The message goes to the agent doing the work, and the conversation can continue there.
Your desktop. Your terminal. Your choice.
Real desktop applications
Keep working in your preferred AI desktop app or editor. AxiOwl brings messaging to its agent conversations, not a replacement chat interface.
Command-line agents, connected
Bring terminal-based agents and scripted workflows into the conversation through AxiOwl CLI and MCP tools. Desktop and command line no longer need to work apart.
Windows. macOS. Linux.
Bring AxiOwl to your desktop operating system. Work across platforms and connect the provider integrations available on each machine.
Direct push. Less machinery.
Agent messaging should be a capability, not another system to babysit. AxiOwl pushes messages into provider conversations through an on-demand messaging core.
Daemonless messaging core
Agent-to-agent sends run on demand. There is no separate always-on messaging daemon for you to start, configure, or keep running.
Mailbox-free delivery
Messages go to the destination agent conversation. Receiving agents do not have to repeatedly poll a shared mailbox to discover that someone has something to say.
No dependency setup
One installer handles the AxiOwl components and selected integrations. No separate messaging server or dependency stack to assemble alongside your existing provider apps.
Build the team you actually want
Pick your agents for their strengths. Not their brand.
The best agent for implementation may not be your favorite reviewer. AxiOwl lets you bring different providers into the same project and give each a real way to talk to the others.
Specialists, connected
Keep frontend work, backend changes, and investigation in focused sessions. When one task needs an answer from another, send the question to the agent that owns it.
A genuine second opinion
Ask a different provider to challenge an approach or review a change. Bring its findings straight back to the implementation conversation instead of ferrying text between windows.
Less repeated explanation
Pass the useful result to the agent that needs it. Keep each provider in its own working context while sharing the decisions and discoveries that move the project forward.
Your choice of provider should expand what your team can do, not limit who it can talk to.
Cross-provider. Cross-machine.
The next agent does not have to be next door.
A useful conversation should not stop at the edge of a desktop or the boundary of a provider. AxiOwl connects named agent sessions on your machine and on connected remote nodes.
Beyond local teams
Native agent teams and remote-node support are different capabilities. AxiOwl adds a route to agents on other machines, including workflows where the provider does not offer that connection itself.
A real destination
Address the agent and conversation you intend to reach. Keep the target recognizable whether the work is happening in a nearby terminal or a connected remote environment.
Different machines, shared progress
Send a question, request a review, or pass along a completed task. Keep distributed work connected through explicit messages without pulling every session onto one computer.
More context for the work
Tiny messaging footprint. More room to think.
A tiny MCP skill keeps the messaging surface compact, so less context is spent describing how agents should communicate. AxiOwl handles the delivery mechanics in code and keeps the useful conversation moving between the agents doing the work.
Compact by design
Agents get a compact, typed messaging tool with the destination and message body it needs. The small interface minimizes context consumed by messaging setup and leaves more room for the task itself.
Let code handle the mechanics
Programmatic messaging means agents do not need to carry a custom messaging syntax or hand-written protocol instructions through every exchange. The implementation manages the routing details behind the tool call.
Use names, skip UUID bookkeeping
Address a recognizable agent name and AxiOwl resolves it to the registered session. Agents can focus on the intended recipient instead of carrying provider-session UUIDs and performing routing lookups themselves.
In our internal Codex tests, AxiOwl used fewer tokens for messaging and sustained long multi-turn exchanges that native messaging failed to complete. Results reflect the workflows tested.
Make the next message count
Ask. Challenge. Hand off. Keep moving.
AxiOwl turns separate agent sessions into collaborators. Send a focused message, get the relevant expertise involved, and keep the next step moving.
Unblock a task
Ask the backend agent about an interface while the frontend agent keeps its own task context. Get the answer from the conversation closest to the work.
Raise the standard
Bring in a reviewer using a different provider. Ask for the weak assumptions, missing cases, or alternative approach, then return that feedback to the builder.
Keep everyone informed
Tell the next agent when a dependency is ready. Request an update when plans change. Replace repeated window-switching with direct exchanges between the people and agents doing the work.
For messaging on your phone, see AxiOwl Mobile.
Provider compatibility, in detail.
Connect the AI tools you already chose. AxiOwl integrations bring these provider families into the same messaging workflow, across desktop, editor, and command-line surfaces.
Windows and Windows Server, x86-64 and ARM64
| # | Provider:App | Discover / Enroll | Send To | Send From with Sender ID | Wake / Steer / Act | Surface / Expose | Create | Change Permissions | Change Model | Make Agent A2A Compatible |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 |
|
Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| 2 |
|
No | No | No | No | No | No | No | No | No |
| 3 |
|
Yes | Yes | Yes | Yes | No | Yes | No | No | No |
| 4 |
|
No | No | No | No | No | No | No | No | No |
| 5 |
|
Yes | Yes | Yes | Yes | Yes | No | No | No | No |
| 6 |
|
No | No | No | No | No | No | No | No | No |
| 7 |
|
No | No | No | No | No | No | No | No | No |
| 8 |
|
No | No | No | No | No | No | No | No | No |
| 9 |
|
Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| 10 |
|
Yes | No | No | No | No | No | No | No | No |
| 11 |
|
Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| 12 |
|
No | No | No | No | No | No | No | No | No |
| 13 |
|
Yes | No | No | No | No | No | No | No | No |
| 14 |
|
Yes | Yes | No | Yes | Yes | Yes | No | No | No |
| 15 |
|
No | No | No | No | No | No | No | No | No |
| 16 |
|
Yes | Yes | Yes | Yes | No | Yes | No | No | No |
| 17 |
|
No | No | No | No | No | No | No | No | No |
| 18 |
|
Yes | Yes | Yes | Yes | No | Yes | No | No | No |
| 19 |
|
No | No | No | No | No | No | No | No | No |
| 20 |
|
No | No | No | No | No | No | No | No | No |
| 21 |
|
No | No | No | No | No | No | No | No | No |
| 22 |
|
No | No | No | No | No | No | No | No | No |
| 23 |
|
Yes | No | No | No | No | No | No | No | No |
| 24 |
|
No | No | No | No | No | No | No | No | No |
| 25 |
|
No | No | No | No | No | No | No | No | No |
| 26 |
|
No | No | No | No | No | No | No | No | No |
| 27 |
|
No | No | No | No | No | No | No | No | No |
| 28 |
|
No | No | No | No | No | No | No | No | No |
| 29 |
|
No | No | No | No | No | No | No | No | No |
Linux, x86-64 and ARM64
| # | Provider:App | Discover / Enroll | Send To | Send From with Sender ID | Wake / Steer / Act | Surface / Expose | Create | Change Permissions | Change Model | Make Agent A2A Compatible |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 |
|
No | No | No | No | No | No | No | No | No |
| 2 |
|
No | No | No | No | N/A | No | No | No | No |
| 3 |
|
No | No | No | No | No | No | No | No | No |
| 4 |
|
No | No | No | No | No | No | No | No | No |
| 5 |
|
No | No | No | No | No | No | No | No | No |
| 6 |
|
No | No | No | No | No | No | No | No | No |
| 7 |
|
No | No | No | No | No | No | No | No | No |
| 8 |
|
No | No | No | No | No | No | No | No | No |
| 9 |
|
No | No | No | No | N/A | No | No | No | No |
| 10 |
|
No | No | No | No | No | No | No | No | No |
| 11 |
|
No | No | No | No | No | No | No | No | No |
| 12 |
|
No | No | No | No | No | No | No | No | No |
| 13 |
|
No | No | No | No | No | No | No | No | No |
| 14 |
|
No | No | No | No | N/A | No | No | No | No |
| 15 |
|
No | No | No | No | No | No | No | No | No |
| 16 |
|
No | No | No | No | N/A | No | No | No | No |
| 17 |
|
No | No | No | No | No | No | No | No | No |
| 18 |
|
No | No | No | No | No | No | No | No | No |
| 19 |
|
No | No | No | No | No | No | No | No | No |
| 20 |
|
No | No | No | No | N/A | No | No | No | No |
| 21 |
|
No | No | No | No | No | No | No | No | No |
| 22 |
|
No | No | No | No | No | No | No | No | No |
| 23 |
|
No | No | No | No | N/A | No | No | No | No |
| 24 |
|
No | No | No | No | N/A | No | No | No | No |
| 25 |
|
No | No | No | No | N/A | No | No | No | No |
macOS, x86-64 and Apple Silicon
| # | Provider:App | Discover / Enroll | Send To | Send From with Sender ID | Wake / Steer / Act | Surface / Expose | Create | Change Permissions | Change Model | Make Agent A2A Compatible |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 |
|
No | No | No | No | No | No | No | No | No |
| 2 |
|
No | No | No | No | No | No | No | No | No |
| 3 |
|
No | No | No | No | N/A | No | No | No | No |
| 4 |
|
No | No | No | No | No | No | No | No | No |
| 5 |
|
No | No | No | No | No | No | No | No | No |
| 6 |
|
No | No | No | No | No | No | No | No | No |
| 7 |
|
No | No | No | No | No | No | No | No | No |
| 8 |
|
No | No | No | No | No | No | No | No | No |
| 9 |
|
No | No | No | No | No | No | No | No | No |
| 10 |
|
No | No | No | No | N/A | No | No | No | No |
| 11 |
|
No | No | No | No | No | No | No | No | No |
| 12 |
|
No | No | No | No | No | No | No | No | No |
| 13 |
|
No | No | No | No | No | No | No | No | No |
| 14 |
|
No | No | No | No | No | No | No | No | No |
| 15 |
|
No | No | No | No | N/A | No | No | No | No |
| 16 |
|
No | No | No | No | No | No | No | No | No |
| 17 |
|
No | No | No | No | N/A | No | No | No | No |
| 18 |
|
No | No | No | No | No | No | No | No | No |
| 19 |
|
No | No | No | No | No | No | No | No | No |
| 20 |
|
No | No | No | No | No | No | No | No | No |
| 21 |
|
No | No | No | No | No | No | No | No | No |
| 22 |
|
No | No | No | No | N/A | No | No | No | No |
| 23 |
|
No | No | No | No | No | No | No | No | No |
| 24 |
|
No | No | No | No | No | No | No | No | No |
| 25 |
|
No | No | No | No | N/A | No | No | No | No |
| 26 |
|
No | No | No | No | N/A | No | No | No | No |
| 27 |
|
No | No | No | No | No | No | No | No | No |
| 28 |
|
No | No | No | No | N/A | No | No | No | No |
Architecture note: Codex Agents window on macOS requires Apple Silicon. VSIX entries are treated as compatible with both macOS architectures.
Provider messaging and remote-node availability depend on the operating system, application surface, and installed integration. Windows, macOS, and Linux coverage differs; configuration support alone does not mean every messaging operation is available.
Choose your platform and release channel on the AxiOwl Downloads page.