Feature Description

Add support for connecting to remote agents via WebSocket, enabling users to configure and chat with remote AI agents without local CLI installation. The architecture supports multiple protocols, with OpenClaw Gateway being the first implementation.

Problem Statement

Currently all agents in AionUi are local (fork-based CLI processes via ForkTask). Users who want to connect to a remote agent instance have no way to do so — there is no UI for configuring remote endpoints, no device identity management, and no pairing approval handling.

Proposed Solution

• New remote agent type with dedicated RemoteAgentCore and RemoteAgentManager (runs in-process, no worker fork)
• Protocol-agnostic architecture: RemoteAgentCore delegates to protocol-specific connections (OpenClaw first, others planned)
• Per-agent Ed25519 keypair generation stored in database (isolated from local ~/.openclaw/identity/)
• Full OpenClaw Gateway handshake with pairing approval flow (5s polling, 5min timeout)
• Encrypted storage for sensitive fields (auth_token, device keys) using existing credentialCrypto
• Settings UI for CRUD on remote agent configs with pairing state management
• Complete conversation lifecycle: create, send, receive, resume sessions

Feature Category

Multi-Agent Support

Additional Context

• Documentation: docs/feature/remote-agent/ (requirements, design, research, architecture analysis)
• Phase 1: OpenClaw protocol support
• Phase 2: Additional protocols (ZeroClaw, PicoClaw, etc.)
• i18n support across all 6 locales (en-US, zh-CN, zh-TW, ja-JP, ko-KR, tr-TR)