> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Frequent questions about Axosun: provider keys, command launches, launch stops, failures, data hiding, and audits.

> [!WARNING]
>
> Axosun is currently unavailable, and its return to service is not planned in the near future.

Answers to frequent questions about the Axosun Assistant. If there is no answer here, start with the [section review of](https://docs.axottle.com/en/axosun/overview.md).

> [accordion] What happens if the provider’s API key is incorrect?
>
> Button **Check the connection** on the profile will execute a real request to the provider and return the error (for example, `401 unauthorized`The error is saved on the profile as a result of the last check, the interface appears red status indicator. Without at least one profile on with the working key, the launches will not start - the panel will warn about this. If the provider refused already in the middle of the streaming response, the launch will end with the status of "error", and the chat will record the move instead of freezing. [Connecting an LLM provider](https://docs.axottle.com/en/axosun/configuration.md).

> [accordion] How do you stop the launch?
>
> Press it. **Stop.** Incomplete launch (queuing, context gathering, analysis) goes to the status of "canceled." If the launch was waiting for a response to the permission card, the cancellation will be noticed in about 2 seconds. [Sessions and launches](https://docs.axottle.com/en/axosun/sessions-and-runs.md).

> [accordion] Why did the assistant refuse to do the job?
>
> The most common causes are:
>
> * the action is prohibited by the current [policy](https://docs.axottle.com/en/axosun/permissions.md) - for example, the Remnawave master switch or entries in Remnawave are turned off; the rights are rechecked at the time of execution, so even the already issued card will not bypass the switched-off setting;
> * The action refers to completely prohibited (`change_sysctl`, `install_packages`) - they can not be enabled in any mode;
> * destructive action for the same purpose has already failed twice - the loop protection worked, the incident escalated to the operator;
> * the confirmation card waiting timeout (15 minutes) has expired - the action is marked as missed, request it again;
> * The request came under pre-security checks, such as disclosure of secrets, and was rejected before reference to the model.
>
> See [Fuses ](https://docs.axottle.com/en/axosun/safety.md).

> [accordion] Can Axosun execute a command on a server?
>
> Yes, but only through action. `run_shell_command` The assistant shows the exact command and the reason in the card, and the operator confirms or rejects it separately. By default, Axosun uses this action to read-only diagnose when regular checks are not enough. `rm -rf /`, `mkfs`recording `dd` on the disk, reboot and turn off the host, are blocked before execution even after confirmation. [Opportunities](https://docs.axottle.com/en/axosun/capabilities.md) and [Safety locks](https://docs.axottle.com/en/axosun/safety.md).

> [accordion] Why are user data hidden in the responses?
>
> By default, the concealment of personal data is enabled (`redact_user_personal_data`): email, Telegram ID, names, descriptions, device identifiers, and short UUID are masked before the model is transferred. In addition, the user sample is limited: the assistant receives counters and a limited sample (up to 100 entries by default), rather than full lists. [Data and privacy](https://docs.axottle.com/en/axosun/privacy.md).

> [accordion] Does the assistant see passwords and subscription links?
>
> No, never. Secrets -- API keys, tokens, passwords, private keys, subscription links, URIs. `vless://` and `trojan://` - are cleared unconditionally, regardless of any settings, both at the input and in the responses of the model. `[REDACTED:…]`This protection can't be turned off. [Data and privacy](https://docs.axottle.com/en/axosun/privacy.md) and [Warehouse of secrets](https://docs.axottle.com/en/security/secrets.md).

> [accordion] How do I give my assistant access to Remnawave?
>
> Panel **Axosun** tab **Policy**: turn on the Remnawave master access switch (it is turned off by default), then individual sub-switches if necessary: sensitive reading, writing, destructive operations, access to users and subscriptions (all are turned off by default). [Models of rights](https://docs.axottle.com/en/axosun/permissions.md).

> [accordion] What's in the audit?
>
> Axosun policy changes, model profile creation/modification/deletion, session and launch lifecycle, every confirmed and rejected action, every call to Remnawave tool (with sanitized arguments) and pre-check failures. The `audit_log` channel cannot be turned off - the panel returns it to policy automatically. See [Operations and Audit Journal](https://docs.axottle.com/en/panel/journal-and-audit.md).

> [accordion] The model suggested an action that's not in the catalog.
>
> The assistant can only offer actions known to the product: any action name that does not match the directory, the panel silently discards before showing to the operator. The directory is available on the **Action Catalogue**, its composition is described on the [Opportunities page](https://docs.axottle.com/en/axosun/capabilities.md).

## Related pages

* [Axosun – Review of ](https://docs.axottle.com/en/axosun/overview.md)
* [Model of rights](https://docs.axottle.com/en/axosun/permissions.md)
* [Sessions and launches](https://docs.axottle.com/en/axosun/sessions-and-runs.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.