AxiOwl Mobile
AxiOwl Mobile keeps your agent sessions within reach when you leave the desk. Pair your phone with a computer, open a conversation, follow its progress, and send the next instruction while the computer continues running the provider tools.
The phone is a working interface to that real environment. It can show messages, tool activity, permissions, and the file or terminal controls supported by the connected host.
The Computer Keeps The Workspace
Your repositories, provider applications, account credentials, and tool processes remain on the host. Mobile receives the information needed to display and control the selected session.
You can keep a long-running conversation open on its original computer instead of creating a separate phone conversation with a copied prompt. The provider session identity remains attached to the work.
What You Can Do
- Open an existing host-owned agent or create one through an available provider.
- Follow streamed assistant output and tool activity.
- Send another instruction with the relevant context.
- Answer permission requests exposed by the provider.
- Inspect project files and changes when the host supports those views.
- Use a host terminal when that capability is available.
- Return to the same host and session after reconnecting.
The host catalog determines the controls available for each provider. Provider brands alone do not imply identical tools or permissions.
Pair Deliberately
The host creates a fresh pairing offer. Import it on the phone and approve the intended device on the host. The resulting relationship identifies the phone and computer separately.
A pairing link is sensitive setup material. Use it for the intended device rather than posting it in a public message or repository.
Connect Across Networks
The encrypted relay route joins the paired phone and host across networks. A direct route uses an address under your control, such as a private network or VPN. Both are described in Hosts and connections.
The host must remain running and able to reach its provider tools. Leaving the desk is different from shutting down the computer that is doing the work.
Native Phone Agents
The native Goose Android and iPhone applications also run an agent loop inside the phone app. This is a separate mode from controlling a computer. Its configured provider, account storage, local tools, and conversation history belong to the phone application.
The model can still run at a remote provider. "On-device" describes where the agent loop runs, not an automatic promise of offline inference or desktop-equivalent tooling.
Read On-device agents and desktop sessions before deciding where a task should run.
Android And iPhone
Connected implementations use the shared host, agent, and timeline contract, while native Android and iPhone apps have their own interfaces and local runtime integration. Obtain the exact distribution for your device from Downloads. Common source contracts do not make every installed version interchangeable.
Android packages and Apple distribution channels have different installation requirements. An Apple registered-device package is not an App Store installation; follow the delivery method listed for that release.
Start Here
- Install, pair, and connect.
- Choose hosts and connection routes.
- Work with agents, files, and terminals.
- Understand mobile privacy.
Looking only for subscription and cloud-cost readings? Use the separate Usage Meter companion.