File logs (structured): `/tmp/apus/apus-YYYY-MM-DD.log` for the default profile, or `/tmp/apus/apus-<profile>-YYYY-MM-DD.log` for a named profile. Set a stable path via `logging.file`; file log level via `logging.level`; console verbosity via `--verbose` and `logging.consoleLevel`.

Fastest tail:

```bash
apus logs --follow
```

Service/supervisor logs (when the gateway runs via launchd/systemd):

- macOS launchd stdout and stderr: `~/Library/Logs/apus/gateway.log` (profiles use `gateway-<profile>.log`; both streams share this file, so startup failures that happen before the logger starts are recorded here too).
- Linux: `journalctl --user -u apus-gateway[-<profile>].service -n 200 --no-pager`.
- Windows: `schtasks /Query /TN "Apus Gateway (<profile>)" /V /FO LIST`.

See [Troubleshooting](/gateway/troubleshooting) for more.

```bash
apus gateway status
apus gateway restart
```

If you run the gateway manually, `apus gateway --force` can reclaim the port. See [Gateway](/gateway).

Three Windows install modes:

**1) Windows Hub local setup**: the native app manages a local app-owned WSL Gateway. Open **Apus Companion** from the Start menu or tray, then use **Gateway Setup** or the Connections tab.

**2) Manual WSL2 Gateway**: the Gateway runs inside Linux.
```powershell
wsl
apus gateway status
apus gateway restart
```
If you never installed the service, start it in the foreground: `apus gateway run`.

**3) Native Windows CLI/Gateway**: runs directly in Windows.
```powershell
apus gateway status
apus gateway restart
```
If you run it manually (no service): `apus gateway run`.

Docs: [Windows](/platforms/windows), [Gateway service runbook](/gateway).

Quick health sweep:

```bash
apus status
apus models status
apus channels status
apus logs --follow
```

Common causes: model auth not loaded on the **gateway host** (check `models status`), channel pairing/allowlist blocking replies (check channel config and logs), or WebChat/Dashboard open without the right token. If remote, confirm the tunnel/Tailscale connection is up and the Gateway WebSocket is reachable.

Docs: [Channels](/channels), [Troubleshooting](/gateway/troubleshooting), [Remote access](/gateway/remote).

Usually means the UI lost the WebSocket connection. Check: is the Gateway running (`apus gateway status`)? Is it healthy (`apus status`)? Does the UI have the right token (`apus dashboard`)? If remote, is the tunnel/Tailscale link up?

Then tail logs:

```bash
apus logs --follow
```

Docs: [Dashboard](/web/dashboard), [Remote access](/gateway/remote), [Troubleshooting](/gateway/troubleshooting).

```bash
apus channels status
apus channels logs --channel telegram
```

Then match the error:

- `BOT_COMMANDS_TOO_MUCH`: the Telegram menu has too many entries. Apus already trims to the Telegram limit and retries with fewer commands, but some menu entries may still be dropped. Reduce plugin/skill/custom commands, or disable `channels.telegram.commands.native` if you do not need the menu.
- `TypeError: fetch failed`, `Network request for 'setMyCommands' failed!`, or similar network errors: on a VPS or behind a proxy, confirm outbound HTTPS is allowed and DNS works for `api.telegram.org`.

If the Gateway is remote, check logs on the Gateway host.

Docs: [Telegram](/channels/telegram), [Channel troubleshooting](/channels/troubleshooting).

```bash
apus status
apus models status
apus logs --follow
```

In the TUI, use `/status` to see the current state. If you expect replies in a chat channel, confirm delivery is enabled (`/deliver on`).

Docs: [TUI](/web/tui), [Slash commands](/tools/slash-commands).

If you installed the service (launchd on macOS, systemd on Linux):

```bash
apus gateway stop
apus gateway start
```

In the foreground, stop with Ctrl-C, then `apus gateway run`.

Docs: [Gateway service runbook](/gateway).

`apus gateway restart` restarts the **background service** (launchd/systemd). `apus gateway` runs the gateway **in the foreground** for this terminal session. Use the gateway subcommands if you installed the service; use the bare foreground run for a one-off.

Start the Gateway with `--verbose` for more console detail, then inspect the log file for channel auth, model routing, and RPC errors.