Gateway

The Gateway is Anyy's resident runtime. It owns live sessions, tools, channels, schedules, background jobs, and delivery while TUI, Dashboard, CLI, and messaging clients connect to it.

Check the Service

anyy gateway status

The result identifies the resolved Profile home, service host, socket, and process state. When both versions are available, it also reports a mismatch between the running Gateway and the current CLI.

For a broader product view, also run:

anyy status

Start and Stop

anyy gateway start
anyy gateway restart
anyy gateway stop

start installs the supported user service when it is missing and waits briefly for the runtime to become reachable. restart also recovers a missing service installation before starting it.

Anyy uses the supported service manager on the host, including a launchd user service on macOS, a systemd user service on common Linux systems, and the supported procd or s6 integration where installed.

Stop interrupts resident work

Stopping the Gateway disconnects channels and stops their live orchestration, schedules and connected runtime work. Check active jobs/processes before maintenance. The separate Dashboard process or browser tab may remain open while its Gateway is unavailable.

Select a Profile

Each resident Gateway serves one resolved Profile:

anyy --profile work gateway status

Profile selection resolves a Home; it does not create a separate native user-service asset for each Profile. macOS uses the fixed com.anyy.anyy launchd job and systemd uses anyy.service. If the existing asset belongs to another Home, the ownership check must be resolved rather than overwriting its service file. The s6 integration has its own per-Profile service handling. See Profiles.

A TUI can temporarily start an in-process Gateway when its default socket is absent; that temporary runtime is cleaned up when the TUI exits. Install/start the resident service when work must continue afterward. Do not point two unmanaged processes at the same Profile. Profile ownership also protects state-changing offline operations.

When to Restart

Most supported setup and Dashboard changes reconcile live state without a manual restart. channel_webhooks.enabled and channel_webhooks.listen are startup listener settings and require restart; account Reload alone does not apply them. See Webhook setup. Restart when:

• gateway status reports that the running Gateway version differs from the current CLI;
• a remediation message explicitly asks for restart;
• the service is installed but unreachable after normal reload; or
• you are completing an offline maintenance procedure.

Troubleshooting

1. Inspect the service:

   anyy gateway status

2. Run product diagnostics:

   anyy doctor

3. Restart the resolved Profile's service:

   anyy gateway restart

4. Re-run status and doctor before changing sockets or service-manager files manually.

Symptom	Likely next step
Service is not installed	anyy gateway start
Running Gateway version differs from the CLI	anyy gateway restart after updating Anyy
Dashboard/TUI cannot connect	Verify they resolve the same Profile and socket
Offline maintenance cannot acquire ownership	Stop the Gateway for that Profile, then retry

See Status & Doctor for the diagnostic fields.