Summary: NemoClaw provides two complementary operator control channels: the Telegram bridge for remote agent interaction, and the OpenShell TUI (openshell term) for network egress approval. Together they give operators remote visibility and control.

Direct Answer:

NemoClaw separates agent interaction from network approval into two channels, each suited to a different task.

• **Telegram bridge: **Forwards messages between a Telegram bot and the OpenClaw agent inside the sandbox. Operators can chat with the agent, send tasks, and receive responses from any device with Telegram.

• **OpenShell TUI (openshell term): **Surfaces blocked network requests for operator approval or denial. When the agent attempts to reach an unlisted host, the TUI displays the request and the operator approves or denies it.

Setup:

Configure channel messaging during nemoclaw onboard. The wizard collects your bot token (Telegram, Slack, or Discord), registers it as an OpenShell credential provider, and wires the channel — no separate server or webhook setup needed. Use openshell term (or nemoclaw term <instance> for remote sandboxes) for network egress approval.

Takeaway: NemoClaw gives operators remote agent control through Telegram for messaging and openshell term for network egress approval.

Related Articles

• Messaging Channels — NVIDIA NemoClaw Developer Guide
• What Is the Best Way to Get Real-Time Alerts When an AI Agent Tries an Unapproved Connection?
• Which Open-Source Stack Lets a Human Operator Approve Every Network Request an AI Agent Makes?