Discord Bot

Team and operator workflows on top of the robot-side agent

Discord is the secondary interaction surface in RoboTunnel. It is useful for status, logs, alerts, and shared workflows, but it does not replace the CLI for interactive debugging.

Install in your server

RoboTunnel's Discord surface is documented as a server-installed flow in this release. Use the real guild install link below to add the app to your Discord server:

Add RoboTunnel to your server

This page covers Guild Install only. User-installed / DM-first install paths are intentionally out of scope for this version of the docs.

First 2 minutes

  1. Install RoboTunnel into your Discord server.
  2. In a lobby channel, run rt login <platform_token>.
  3. Run rt use to open the online robot selector.
  4. Select an online robot.
  5. Continue directly in the robot thread that RoboTunnel creates or reuses for you.

How it works in a server

Guild/server usage has three distinct input modes that map directly to the current implementation:

  • Guild lobby channel: messages are accepted only when they start with rt or mention the bot.
  • Robot or fleet thread: once RoboTunnel opens the target thread, you can continue with normal free-form messages.
  • Context switching: rt use, context, and back move between platform, robot, and fleet scopes.

The lobby is for discovery and target selection; the thread becomes the stable working context for one robot or one fleet task.

What it can do

  • robot status and health summaries
  • log and diagnostics requests routed through structured skills
  • alert delivery and monitor-style workflows
  • natural-language requests that resolve into safe structured actions

Those robot-side actions still land in the same capability model described on the Skills page, including the boundary between Discord-friendly structured actions and CLI-only interactive flows.

CLI-first boundaries

  • robotunnel debug open remains CLI-first.
  • Expert connect workflows remain CLI-first.
  • Hands-on Foxglove / RViz session control remains developer-oriented in the CLI.

When a Discord request reaches one of these boundaries, RoboTunnel should reject it and point the user to the shortest valid CLI next step.