Agent lifecycle

Startup

When PLUXIX Agent opens, its desktop UI attaches to the local RuntimeHost. The RuntimeHost is the persistent worker boundary: it manages local processes, workspace access, health state and reconnect behavior independently of the window.

• Closing the UI should not terminate a running local task.
• The Windows service starts with the system when installed.
• The UI shows cached state first and then attaches to live status.

Cloud connection

The Agent authenticates to pluxix.com over TLS and uses the account session to create and stream conversation work. The cloud controls identity, account state, usage, routing and durable metadata; local execution stays on the user's machine.

• A temporary network interruption should trigger reconnect with backoff.
• A 401 means the session needs re-authentication, not that a model should be exposed.
• Never work around a connection error by opening the local runtime publicly.

Recovery

If a task is interrupted, reopen the conversation and inspect the last event. Retry only after confirming whether a tool action already completed. The service health indicator and local logs are the first evidence source.