Messaging questions and troubleshooting
Does AxiOwl include a model subscription?
No. Provider authentication, subscriptions, model availability and usage charges belong to the provider/account you select. AxiOwl account or licensing features have a separate purpose.
The tool says accepted. Did the message arrive?
Acceptance establishes admission, not visible target delivery. Inspect the intended native conversation when delivery confirmation is needed. An assistant saying it sent the message is not equivalent to seeing the body at the destination.
Where is the agent's answer?
Send addresses a conversation; it does not automatically start a message exchange or wait for a model. The destination's work can appear in its own conversation. A new message elsewhere requires separate explicit authorization.
The operation timed out. Should I send it again?
Do not repeat an accepted or uncertain operation. A timeout does not cancel it. Preserve its reference, inspect the exact native target and use the existing status observation if the host exposes it and the user requests it.
Two chats have the same name. Which one is selected?
Resolution uses the provider/computer scope and actual recent chat use when the destination is selected. After binding, that operation keeps the exact conversation. Use distinctive titles and preserve remote qualifiers.
The provider is installed but AxiOwl tools are missing
Confirm the actual integrated environment or managed copy, the selected desktop/CLI surface, the setup outcome and provider authentication. Load changed integration configuration through the provider's normal lifecycle.
Do not clear the entire profile or credentials to conceal an integration problem.
Installation completed with warnings. Is everything ready?
No. Read each incomplete component and its reason. Independent integrations can have completed successfully while another remains unusable.
A remote chat is listed but cannot be reached
A saved registry can outlive connectivity. Check the intended computer, route, provider environment and account. SSH, relay, mobile pairing and A2A each have separate requirements.
Do not shorten the target label to make it resolve to a different local chat.
Why is the Download button unavailable?
The installed package may already be current, no approved package may be published for that platform/channel, or the package may need review. Read the displayed availability instead of forcing another download.
Does a successful build mean every provider pair works?
No. Compilation, signing, publication and installation do not establish message delivery for every provider/OS/version combination. Historical checks describe their actual scope.
How do I report a problem?
Record the product and component versions, OS, provider surface, exact action and visible result. Preserve the operation reference for an existing Send. Share only narrow redacted evidence through Contact.
Never include passwords, private keys, pairing links or unnecessary project/history data.